Algodoo

Why you use "sim.running ?" in "update" instead just using "postStep"?

Thanks for asking. I had thought that the "update" event happened every frame while "postStep" happens at sim.frequency. I tested this and I can see that they both run at the same rate.

P.S.
My test was flawed. The "update" event does happen every frame (usually at 60fps) and "postStep" does happen at sim.frequency.

Hmmmm..... That was my assumption too. Do you know of an accurate method to test the rate difference between update and postStep?


BTW - Very imaginative scene. Well done!

Concerning update and postStep, I ran a simple test. I wrote exactly the same counter script in each, and I had them start exactly at the same time when I started Algodoo (they both had "sim.running ?" script). Here is what I found:

When the sim.frequency is set to 60Hz, both counters ran at the same rate. i.e., when I stopped both counters at the same time after running for about 15 seconds, the resulting counts were very close (+/- 2 counts) to each other. When I adjusted the sim.frequency and ran the test again, I found that it made a HUGE difference in the count rate of the "postStep" script and little or no difference in the count rate of the "update" script. So, apparently, there IS a difference in the rates that those two properties handle script, and only at 60Hz, they are very close or spot on with each other.

I didn't think to test at different frequencies. Thanks for checking that out.

post step runs at whatever sim frequency you set
update runs at screen fps

ex: sim frequency = 1000 hz. 1000 updates per second
update = fps. 60 fps(hz) 60 updates per second