Jump to content
  • Advertisement
Sign in to follow this  
giantjupiter

deterministic physics engine

This topic is 3883 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Advertisement
In isolation, all of them should be deterministic, as long as you use fixed time steps (e.g., physics always steps at 0.01 seconds rather than at the frame rate). And I think all of the popular engines support fixed time steps. Even in game, as long as you can guarantee deterministic inputs and used fixed time steps, the physics engine should produce deterministic results.

You can get into trouble if you have nondeterministic things going on that affect physics. For example, on a single player game, if there are kinematic objects being animated via a traditional keyframe animation system and the keyframe animation is updated with the frame rate, then all of a sudden your kinematic objects have nondeterministic motions, and so collisions with these objects become nondeterministic resulting in nondeterministic physics. Player inputs are by their very nature nondeterministic since humans aren't capable of deterministic motion. Networking stuff for multiplayer also tends to be heavily nondeterministic and dead-reckoning algorithms will predict different things each time, even if the player happens, somehow, to play the game in exactly the same way, precisely, each time.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!