Physics simulation becomes erratic with set_time_step set to more than 1

In my physics game the player is a dynamic collision object. After a level has been completed I wait until the object settles until I continue. I want to be able to fast forward this section to reduce the wait time.

This code produces erratic results:

msg.post("#collectionproxy", "set_time_step", {factor = 10, mode = 0})

I created a minimal project to see if it was something in my code causing the issue. This is the result with a time step factor of 2:

The test project: Archive.zip (10.2 KB)

This is the only code in the project (aside from loading the proxy):

msg.post("#collectionproxy", "set_time_step", {factor = 2, mode = 0})

Does this have to do with the physics being updated only once per frame?

Yes, I would think that is the reason. :-/

1 Like