3 ms·
There min/frame in the included paper chart range from 3.8m/frame to 25.8m/frame, which is pretty slow for 2013 at the simulation sizes they give. It is too ba
by bhouston 13y ago
There min/frame in the included paper chart range from 3.8m/frame to 25.8m/frame, which is pretty slow for 2013 at the simulation sizes they give.
It is too bad they didn't break out the individual steps to show where the time was spent. Could simply be unoptimized code. I notice there is a restriction on the time step to be less than 0.5 x 10^-3 s, not sure if that is the main difference.
- tinco 13y ago0.5 * 10^-3s is 2000hz, so 20 iterations per frame, assuming they render at 100hz, that seems a bit on the high side.. does that mean they don't have a good way of interpolating the physics effects, does that happen a lot in these kinds of simulations? I work on a real-time multi-player game, and our physics step is actually larger than our framerate, we interpolate the rest, I guess that's quite the opposite of this :)