-"Freyja or Freya is a major goddess in Norse Paganism,
comparable to Roman goddess Venus and Greek goddess Aphrodite. The documented source of this religious tradition, the Norse Mythology, was transmitted and altered by Christian medieval historians, the actual role, heathen practices and worship of the goddess are uncertain.Freyja was also associated with war, battle, death, magic, prophecy and wealth. She is cited as receiving half of the dead lost in battle in her hall Folkvangr, whereas Odin would receive the other half at Valhalla.
The origin of 'Seid' (sorcery or witchcraft) was ascribed to Freyja."
Frame Rate Independence
(Open Source - BULLET PHYSICS LIBRARY, Physics Symulation
Forum)
Aug 26, 2008
>"a.)
Bullet features 2nd kind of "frame-rate
Independence", which gives you FREEDOM to sync your
timer and animation with Bullet's internal 60fps as you
see fit b.) it can do 1st - "FALLING-framerate"
Independence by using stepSimulation(dt, 0), but it is
not deterministic
c.)
stepSimulation(dt, 10or100or1000or5000..) should be doing
something 'visually similar' to what stepSimulation(dt,
0) in practice does or not?"
>>"Indeed, except that calling
"stepSimulation(dt, 0)," with a large dt is
unsupported and creates all kinds of artifacts. The big
difference with calling stepSimulation(dt,
10or100or1000or5000..) is that the latter doesn't degrade
the simulation quality."
- thank you, that makes it perfectly clear, how wonderful!
now,
the problem seem to be that stepSimulation(dt, 10or100..
) doesnt seem to be working as good as stepSimulation(dt,
0) and this thread uncovered that stepSimulation(dt, 0)
is somehow everyones 1st and "natural" way to
think about "what should be happening" - it
seem it would be everyones 1st choice to use it... if it
was only supported and if it was deterministic - perhaps
someone could make it so, but do we really need it?
1.) on game consoles:
NO, we will fix FPS anyhow and tie it up to Vsync so
animation get absolutely smooth and we can design our
world so the speed is rarely compromised, and even if
that happens little slowdown is not a big deal - eg.
GodOfWar2 on ps2
2.) on PC:
YES, probably - to try to accommodate as wider specs as
possible, little slow-down is not an option as it could
be BIG on some machines, while dropping FPS even down to
5-10 *IS* acceptable for low-end specs on some
screens/situations
...or so it would seem by looking at it from my chair
cheers
Aug 27, 2008
(Re)Designing an
API...
>>"Thus newbie code.. / ..more newbie-friendly / ..so that newbies have an easy time / ..also be newbie-friendly / easy for newbies.. / The newbie developer.. / what newbies pass.. / really help the most to the newbie end user"
- how in the world..
newbies?
there is no such thing really.. that logic is artificial
and when forced to existence can make you only do the
wrong things.. you SHOULD NOT design *anything* for
newbies, never, ever... the closest thing to that
misthink is a designing 'graphical user interface' for
children or handicapped... no TVs for newbies, no remote
controller for newbies, no Xbox for newbies, no C++ for
newbies..
because in practice it means - trying to accommodate for
someones ignorance, assumptions and every other way
people can be foolish... plenty of those, futile attempt
obviously, eh?
why just not make documentation clear and easily accessible, maybe answer some questions properly on the forum, more importantly even - do not attempt answering questions you do not know about ..and basically encourage and make it easy for newbies to LEARN not try to accommodate all the ways they can make mistake...
how else?
you dont really have to think about API and
"interface" at all, not as such - look, make
your code SMALLER, not necessarily in the number of
characters or even lines of code but smaller in the
number of *terms* you define in order to communicate
information and response throughout the code.. of course
it does almost always practically lead to less lines of
code, less variables, less function calls, less
arguments.. less of everything
and by doing so,
you would most certainly make it faster and more memory
efficient as well - but the best of all, simplicity and
bare logic is all you need to accommodate newbies - it
will be *easy to learn*
"All other things
being equal, the simplest solution is the best."
-Occam's razor
[edit:]
Bullet library is GREAT, its already very simple, *easy
to learn*, fast and still having all these great
features... it reminds me of OpenGL and they beautifully
go together, i LOVE THAT!
note,
everyone has source code -its yours-, go on, change
everything as you like... i will try your Bullet library
for newbies and maybe id stand corrected, dont let me
discourage you, its only an opinion..
Genesis, Saturday
----------------------------------------------------------------------------------------------
