High setUpdateRate values?

Monkey Forums/Monkey Programming/High setUpdateRate values?

Foppy(Posted 2011) [#1]
Would it be sensible to use setUpdateRate values that are considerably higher than 30 or 60, for example 120?

I am experimenting with this in combination with HTML 5 builds. There can be a bit of stutter when setting the rate at 60. Then again, perhaps this is typical for HTML5 builds?

Sometimes the animation seems smoother with the high update rates, so I was wondering what other people do or think about this.


Sledge(Posted 2011) [#2]
It's going to be pointless if there's any sort of v-sync (either genuine or simulated) applied to the canvas by the browser or OS, surely?

EDIT: Oh, just looked at the behaviour Skid describes in the other thread and I guess not! I think my concern would be that, if you're doubling the update rate to try to keep things smooth, well that's a lot more actual work, isn't it, so surely you run the risk of increasing the chance of a hiccup?