Currently, when I update the entities I calculate the time passed since the last update, and then pass that to their update function. They will in turn pass that duration to all their components.
currentTime = clock.getTime() timePassed = currentTime - lastUpdate
This means that the physics components also gets a variable time step, but it appears this is bad and can lead to inconsistent simulations. Here's some details on this:
The answers suggest that the physics simulation time step should be constant and higher than the rendering time step. But since I can't ensure how well the game will perform, this can be rather difficult to achieve.
One answer suggests this:
Use Gaffer's "fix your time step" approach. Update the game in fixed steps as in option 1, but do so multiple times per frame rendered - based on how much time has elapsed - so that the game logic keeps up with real time, while remaining in discrete steps.
This seems like a good approach to me, but I don't really understand how I should be doing it. Instead of doing:
I should be doing the following?
while timePassed > 0: physics.step(1) # millisecond timePassed -= 1