RLGaming.com

i tried out the tweak for RvS to improve frame rates by loading the game at high priority and noticed no difference in frame rates as displayed by Fraps. my fps stayed for the most part between 40-60.

My question though is this:

It appeared that my fps NEVER went above 60. is there something that limits fps in software or in hardware? Is there a way for me to change that? I can't imagine that i have a hardware option short of buying a new card, but maybe there is something in my OS (win xp) or my nvidia software that i could change. i have a geforce 4600 ti.

I know that in your display settings there is a frame-rate option, which lets you choose the frame-rate most appropriate for your system - one of which is "optimal", that's where I have mine and I don't have any problems with it.

Check your refreash rate setting Madrus. Just make sure that whatever setting you use, that your monitor supports it at whatever resolution you are using. If you run at a refresh rate your monitor doesn't support, bye bye monitor.

I have my refresh rate set at 85Hz, for 1024x768 desktop, and usually 1280x960 in games.

Also, try disabling Vsync in your video settings. Vsync ON limits games to whatever your refresh rate is set at, but you may experience graphic anomolies with it OFF.

It's mostly what softball is saying. Check to see what refresh rate your game is (many games select a video mode that includes a refresh rate of 60 Hz). This mode (rate/resolution) is not necessarily the same as your desktop rate/resolution. Check the in-game option for refresh rates (If it's not in your in-game menu, you'll need to activate it in one of the config files -- i forget which one, but I can tell you later if you need.) If your refresh rate is only 60 Hz, you will never get more than 60fps.

Also, and i believe this has been brought up before about refresh rates and WIN XP is that if you are not running with the SP1 XP update then WIN XP WILL NOT LET YOU RUN OVER 75MHZ even if you tell it to, it might report that it is but its not,and i have had this confirmed.

But if you are running SP1 and i presume you are then this is not a problem since this bug was fixed in SP1.