In my tile engine, I am encountering something quite odd... I have been testing FPS by varing the amount of objects I put in a map. I notice that when I only have 1 layer, or NO tiles at all, the program will ALWAYS run at EXACTLY 150 FPS... if I add a lot of objects in 1 space then slowly (and i mean pixel by pixel) move over that space, the FPS won''t go down until 1 point and then it will go to EXACTLY 75 FPS (exactly 1/2 of the origional 150 FPS). If I then proceed pixel by pixel closer to the mass of objects, I notice it all of the sudden jump to (again) EXACTLY 50 FPS (exactly 2/3 of the 2nd 75 FPS)... Seeing a pattern? I am! Anyway, I am not able to produce anything other than these seemingly specific FPS rates and I am wondering if there is some kind of overload thing that does this... Has anyone run into this before? It''s no real problem just a weird occurence but since I am semi-new to directx programming I don''t know what to think about it.

This is probably because your refresh rate is 75hz.

Gotta love vsync

I am assuming your using DX, when you do the present() call, use no-vsync, then it will run at full speed and not be limited by your monitors refresh rate. Look it up in the dx sdk how to do it exactly.

Possibility