My app runs to fast!

Mike · Post by **Mike** » Sat Mar 05, 2005 11:39 am

Hey there ya all

As the header implies my app runs too fast. It just does everything as fast as it can, which is to fast! I need to control it so it has a fixed speed, not speed related to the numbers of calculations it has to currently do...

What can you do to solve this? 30fps is kind of minimum right?

bal · Post by **bal** » Sat Mar 05, 2005 11:50 am

You could turn on VSync (boolean value in the createDevice() function). This will limit the FPS to your monitor's hz (60FPS that is).

Mike · Post by **Mike** » Sat Mar 05, 2005 11:54 am

But doeasnt that vsync also do other things? And what if my comp is not capable of running at 60fps, then speed will be nonfixed, right?

All calc in my app is done at a tick-basis. Thats why i wanna control it. Cant I do that? I realize i might have built my system stangely...

bal · Post by **bal** » Sat Mar 05, 2005 1:59 pm

Yeah, vsync just caps at 60FPS, you can still go below. This feature has been asked several times up to now but noone implemented it yet.

Acki · Post by **Acki** » Sat Mar 05, 2005 2:12 pm

I would do a pause loop after drawing the scene...
I prefer GeTickCount(), because it has a resolution of 1/1000 seconds...

afecelis · Post by **afecelis** » Sat Mar 05, 2005 2:52 pm

Code: Select all

smgr->addCameraSceneNodeFPS(0,100.0f,300.0f);

the last 2 values are for camera speed and camera rotation speed. Try weaking them and you'll speed will slow down.

Mike · Post by **Mike** » Sat Mar 05, 2005 3:38 pm

Couldn't you use the internal clock to limit it to a certain fps? That is after a entire frame has been done, it waits until 1/30s has been accumulated, then starts the next frame. But how to do this?

Guest · Post by **Guest** » Tue Mar 08, 2005 5:27 pm

does directX support any kind of framerate limit? I'd really hat to limit my game to just openGL because of the speed.

Kaeles · Post by **Kaeles** » Tue Mar 08, 2005 6:17 pm

instead of implementing all your movement and such according to the framerate you might want to try doing it independent of framerate....

such as...
moveforward()
{
timefactor = currenttime - starttime;
setposition = movevector* timefactor;
}
something like that, so that no matter what fps you get, the movement is still going to be the same.

William Finlayson · Post by **William Finlayson** » Tue Mar 08, 2005 7:08 pm

I always implement my time-based actions with an update(int ticks) method.

lastTime = timer.getTime()
main loop
currentTime = timer.getTime()
ticks = currentTime - lastTime
thing1.update(ticks)
thing2.update(ticks)
lastTime = currentTime
draw stuff etc
end loop

You mentioned that your calculation was done on a tick basis, so I hope this helps.