My program (which, for once, is working right) has a frame limiter built into it (leftover from Programming RPG''s with DirectX), which supposedly limits it to 30 frames per second in the following manner: BOOL cApp::Frame(){ static DWORD UpdateTimer = timeGetTime(); // Limit all frame updates to 30 fps if(timeGetTime() < UpdateTimer + 33) return TRUE; UpdateTimer = timeGetTime(); m_Frames++; // do work... } I find nothing strange about the code (wait until at least 33 milliseconds passed since last frame -> +/-30 fps), but when i added the FPS counter, it was leveling off around 20 fps. Even more strange is that when i change the minimum delay from 33 to 16 milliseconds (theoretically getting 60fps if your PC can handle it) it leveled off around 40 fps. Why is that? Also, when i removed the frame limiter completely it floated around 60fps, but i think that''s just because of vsync (... which is the monitor''s rate of updating, right?). By the way, to make sure my PC isn''t topping off at 60 fps (and out of curiousity as to how high it''ll go), how do i ''uncap'' the vsync (if that IS the problem) to allow it to go up to it''s max fps?

... freaky! I just tried it right now (without changing ANYTHING) and i got 30 fps with 33ms wait, and 60fps with 16ms wait. Despite probably being my fault in some way, i still blame my computer! :D

But how do i turn of vsync though? I searched all my files for the string "vsync" but couldn''t find anything. I looked it up on the DX docs, but the only reference was to the swap effect, which in my engine is:
d3dpp.SwapEffect = D3DSWAPEFFECT_DISCARD;

Does that mean vsync''s off? (... and if it is, that''s bad, isn''t it?)

!$%&*@# ... I ran it like 8 times now and over and over again i get 21.3something fps... If i put in a delay of 31ms though, i get 31.something fps (a quickfix, i suppose, but in no way ideal).

Anyone have a clue?

Slightly off-topic... but why are you limiting the frame rate? Maybe you could keep track of the time elapsed since the last frame and use that instead (time deltas)... ??

Regards,
Sharky

---
< Sharky''s Coding Corner >
< Coder @ Strangelite >
---

true... but this is already setup right now, and while not ideal it''s satisfactory. I could (and probably will later on) switch to full time-based simulations but that''ll get a bit complicated.

Even still, i''m just curious now as to the solutions... (and the problem as well)

great, thanks a bunch!

Anyone have a clue as to why sometimes it''s limited to 21.x frames and sometimes it''s limited to 30.x frames (using the same delay, just different runtimes)?