News for hackers. Stuff that matters.
Re:Planck.js – JavaScript rewrite of Box2D physics library by partycoder on Thursday April 06, 2017 @12:04PM (#14051799)
What I remember from Box2D is that the simulation wasn't deterministic but rather dependent on frame rate for example. Is it the same case for this?
Re:Planck.js – JavaScript rewrite of Box2D physics library by ewjordan on Thursday April 06, 2017 @01:56PM (#14052887)
If you tie the frame rate to the physics step, then yes - that will be true for pretty much any physics engine.

The classic advice here is http://gafferongames.com/game-physics/fix-your-timestep/

Re:Planck.js – JavaScript rewrite of Box2D physics library by shakiba on Thursday April 06, 2017 @03:46PM (#14053951)
In JS, if you pass same input it will give you same results. With box2d/planck frequency needs to be constant anyway, and I have not seen any nondeterministic component in the code. (I think in box2d docs it refers differences in execution platforms not the library itself.)
Re:Planck.js – JavaScript rewrite of Box2D physics library by DiThi on Thursday April 06, 2017 @12:23PM (#14052001)
Not even if you always pass the same frame step from your engine independently of your actual frame rate?
Re:Planck.js – JavaScript rewrite of Box2D physics library by maaaats on Thursday April 06, 2017 @02:13PM (#14053023)
Then you used it wrong, as you should never tie your simulation to the frame rate. Given same input, Box2d is deterministic.