Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Setting deterministic lockstep changes the time step for the physics engine
See original GitHub issueCheck out the deterministic lockstep PG: https://www.babylonjs-playground.com/#DU4FPJ#3.
Changing the value for lockstepMaxSteps affects the speed of the physics simulation.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Deterministic Lockstep | Gaffer On Games
Determinism means that given the same initial condition and the same set of inputs your simulation gives exactly the same result. And I...
Read more >Physics Timestep Clarification - Questions - Babylon.js Forum
setTimeStep method determine the amount of time between each physics update, or the amount of simulation time processed each time the physics ......
Read more >Physics simulation fixed time step and enhanced determinism ...
I've implemented, the possibility to activate fixed delta time of Physics simulation directly in the project editor.
Read more >Deterministic Physics for Lockstep Networking, Any Progress?
Hi Unity Community, I'm working on an open source lockstep networking layer (atop socket.io) built for large scale RTS style games requiring ...
Read more >Fixing your Timestep and evaluating Godot - GameDev.net
One option for engine devs is to leave interpolation to the physics engine. This would seem to make a lot of sense (avoiding...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yep, those are two distinct issues (that’s why I didn’t close this issue). I already found an error in the calculation of the deterministic step (will probably commit tomorrow), I just wanted to be sure we can test it correctly.
I have pushed a fix. I am pasting my explanation from the PR here just for reference:
We should notice how deterministic step is working, and how we deal with max steps. If the scene is running at 20 FPS and we set the nax step to 3 and up, the scene will run in “simulated” 60 fps (as the max FPS target is 60 fps). if, however, we will set it to 1 or 2, the simulated fps will be lower (20 or 40 respectively).