Too fast on modern hardware ?

[RobbeK]

No slowing down loops built in --  too fast ?  (only one pc in the house now)

Animation based on the Lorenz dif. equations


best Rob

.

[Mike Lobanovsky]

No, it isn't. It can't be because the scene is rendered only once every 20 milliseconds on any computer according to myTimer's timeOut setting. That's why what you're seeing and what I'm seeing actually runs at one and the same FPS rate.

[RobbeK]

Ah, thanks Mike -- it's somewhat confusing for me - is it then correct that problems start when the calculation cycle is (a lot) outside the rendering refresh rate ? (and giving less contineous movement )
For rotations/translations I normally use the FrameRate to calculate the incr decr step of the movement ...

best Rob

[Mike Lobanovsky]

is it then correct that problems start when the calculation cycle is (a lot) outside the rendering refresh rate ?

Yes, that's correct. But not only that. The Windows timer is a very crude instrument with precision granularity as low as 15~16 milliseconds. Which means that timeOut incrementation of 1 to 16 above ~16 milliseconds will immediately reset it to 32 milliseconds, 32 + 1 to 16 milliseconds, to 48 milliseconds, etc. etc. etc.

The Windows timer should be used only in simplest OpenGL applications with a fixed FPS rate that is a multiple of 16 milliseconds. On the other hand, the timer is a very easy means to minimize CPU load in immediate-mode OpenGL applications.