Frame rate limiter

I assume you mean you don't want it to go over 30 fps? The best way is to keep looping, and check the time each loop. Once your frame time is greater than what you want, draw the frame and continue looping, something like this:

float Time = 0;while(true){    if((GetTime() - Time) > (1.0f / 30.0f))    {        Time = GetTime();        DrawStuff();    }}

This means it will wait until (1/30) seconds have passed until it does the next frame. The only proble here is if you can't maintain at least 30 frames per second, then things start to bog down (obviously).

Quote:

The only proble here is if you can't maintain at least 30 frames per second, then things start to bog down (obviously).

Thanks for that advice, i was thinking, i only have to maintain 30 game updates / second, i could skip rendering if it ever falls below 30.

This is a bad idea. It is much better to use a timer to find the delta time and then use that to advance any animation/physics. This is much more robust and makes full use of the CPU, where as in that method you waste clock cycles looping.

There's really no sane reason why you would want to limit the framerate at 30fps of all things. The refresh rate of the moniter is the only frequency that would make sense, and that is done through other means (VSync). Animation can be set up as a function of time, where as you normally have your dt be 1/30.0f, instead use the time interval that it took to draw the last frame.

hi there. thank google, ive found a site...
iam not a coder and didnt know anything how to code. i was looking for a tool to limit the fps in dx games. is there any tool to cap the fps?

would be nice if someone can give me a hint.

thank you

Quote:

Original post by Aressera This is a bad idea. It is much better to use a timer to find the delta time and then use that to advance any animation/physics (emphasis mine). This is much more robust and makes full use of the CPU, where as in that method you waste clock cycles looping.

I disagree with this. Using a fixed time-step for physics simulations is definitely the way to go to prevent all sorts of issues. However, you should be rendering (and updating animations) as fast as you possibly can.

Here's a stripped down version of what I'm currently doing.

You might find this site interesting http://www.gaffer.org/game-physics/fix-your-timestep/

I once had an idea for motion blurring which has most likely been used somewhere but it goes like this..

You render to your *screen* 30fps (video) or 24fps (film) or whatever you want.. But you render and update as many times as possible between the frames (though you might have it cap at five to keep memory usage for each intermediate

I once had an idea for motion blurring which has most likely been used somewhere but it goes like this..

You render to your *screen* 30fps (video) or 24fps (film) or whatever you want.. But you render and update as many times as possible to off-screen textures between the screen frames (though you might have it cap at five to keep memory usage for each intermediate framebuffer down) so then u accumulate the time between the capped framerate just like the eye does.

So say ur computer is capable of 90 fps at anyone time during the game, but the framerate is capped to a film rate (24fps) to make it seem more like a film, in the 41ms of frame time, you'll have rendered and updated 3.75 off-screen frames (which would end up as 4 full frames in real world application), thus giving you some basic motionblur. I'm sure this method of motionblur is terrible haha but hey

Anyone know what this kind of motion blur is called?

I some thing similar to motion blur in my engine. I blend the sleeps over time so the end user does not notice pause. By doing a bunch of small sleeps over time the cap keeps a smooth frame rate.
feel free to look at how I am doing it in the UpdateScreen and fpsDelay functions of my engine