Page 1 of 2

Manually limiting FPS

PostPosted: Feb 10, 2004 @ 6:03pm
by efortier

PostPosted: Feb 10, 2004 @ 6:21pm
by DillRye

PostPosted: Feb 10, 2004 @ 6:22pm
by simonjacobs

PostPosted: Feb 10, 2004 @ 6:59pm
by Dan East

PostPosted: Feb 10, 2004 @ 7:01pm
by wyrd

PostPosted: Feb 10, 2004 @ 7:21pm
by mlepage

PostPosted: Feb 10, 2004 @ 7:30pm
by efortier

PostPosted: Feb 10, 2004 @ 9:29pm
by xPeterx

PostPosted: Feb 10, 2004 @ 9:36pm
by efortier

PostPosted: Feb 10, 2004 @ 11:22pm
by Dan East

PostPosted: Feb 10, 2004 @ 11:30pm
by simonjacobs

PostPosted: Feb 11, 2004 @ 3:46am
by efortier

PostPosted: Feb 11, 2004 @ 5:27am
by Dan East
That may have to do with the thread granularity of the OS. The OS gives apps processing time in chunks, and that may happen to cause an extra long delay with a specific sleep amount.

Since your app is well behaved and Sleeping when it doesn't need CPU time, you could try increasing the priority of your application to see if that fixes your 32 MS problem.

You might want to verify that there isn't a bug in your code. Just call GetTickCount before and after Sleep to see how many milliseconds the call actually consumed.

Dan East

PostPosted: Feb 11, 2004 @ 6:27am
by mlepage

PostPosted: Feb 11, 2004 @ 7:29am
by sponge