Limited to 60FPS

[Philippine Mango]

Ok I've heard this time and time agian about how windows XP limits frame rates to 60FPS but didn't bother with it until it started to become a problem. I have V-sync disabled and I have omega drivers. Is there a way I can bypass this limitation? Also I'm wondering if the reason why my frame rates are limited to 60FPS is because I have temporal anti aliasing enabled..

 

[Scouzer]

yes, that is why

to have temporal you need vsync.

 

[Muscles]

People say winxp limits your FPS to 60 because winxp won't let you set higher refresh rates. For example, if your system is getting 120 fps in say Quake 3 and your refresh rate is set at 60 hz then all you're getting is 60 fps. Use a program called Reforce to fix this problem. Look it up on google and download it.

 

[Continuity27]

Originally posted by: Muscles
People say winxp limits your FPS to 60 because winxp won't let you set higher refresh rates. For example, if your system is getting 120 fps in say Quake 3 and your refresh rate is set at 60 hz then all you're getting is 60 fps. Use a program called Reforce to fix this problem. Look it up on google and download it.

Windows XP by default DOES let you set a higher refresh rate than 60, but not within full screen applications like games. Reforce is used to unlock higher refresh rates in full screen applications.

V-Sync will keep you at your monitors refresh rate as a maximum in order to minimize "tearing" which is a graphical anomaly noticed when turning and such. It's caused when the video card is sending video information faster than the monitor can handle, so when you turn, or something moves on your screen, the video card redraws a couple times before the monitor can redraw once completely, thereby interrupting it half drawn. If you have a high refresh rate, lets say 85+, I'd generally keep V-Sync on, what do you need more than 85+ FPS for? Your eyes can't see it, and all it will do is add graphical corruption. I think SLI still has issues when V-Sync is enabled though, so keep it off if using SLI.

 

[theMan]

does this happen it windows 2000 also? maybe games should be played non full screen but streched out all the way.

 

[Continuity27]

Originally posted by: theman
does this happen it windows 2000 also? maybe games should be played non full screen but streched out all the way.

It will run faster if it's full screen instead of windowed. Just run Reforce and set the Windows XP limit from 60 to whatever you want.

I don't think it happens in Windows 2000.

 

[Philippine Mango]

doesn't fix it...

 

[Philippine Mango]

bump

 

[FlyingPenguin]

Windows does NOT limit your video FRAMERATE in games.

Your framerate is capped by two factors:

- Any cap that exists in the game (most Quake engine games have a 72 FPS cap for instance, although it can be adjusted).

- The refresh rate of your monitor (if VSync is enabled).

With VSync enabled, your framerate can NEVER exceed your refresh rate, which is why those of us with LCDs should ALWAYS use the refresh override in our video driver settings to set 3D game refresh to 70 or 75 Hz (whatever your monitor supports). On an LCD you cannot distinguish between 60 and 70 Hz, but you want the refresh as high as possible for gaming.

 

[Muscles]

Originally posted by: Continuity27

Originally posted by: Muscles
People say winxp limits your FPS to 60 because winxp won't let you set higher refresh rates. For example, if your system is getting 120 fps in say Quake 3 and your refresh rate is set at 60 hz then all you're getting is 60 fps. Use a program called Reforce to fix this problem. Look it up on google and download it.

Windows XP by default DOES let you set a higher refresh rate than 60, but not within full screen applications like games. Reforce is used to unlock higher refresh rates in full screen applications.

V-Sync will keep you at your monitors refresh rate as a maximum in order to minimize "tearing" which is a graphical anomaly noticed when turning and such. It's caused when the video card is sending video information faster than the monitor can handle, so when you turn, or something moves on your screen, the video card redraws a couple times before the monitor can redraw once completely, thereby interrupting it half drawn. If you have a high refresh rate, lets say 85+, I'd generally keep V-Sync on, what do you need more than 85+ FPS for? Your eyes can't see it, and all it will do is add graphical corruption. I think SLI still has issues when V-Sync is enabled though, so keep it off if using SLI.

I'd leave vsync off... Tearing is not a problem assuming your hardware (monitor) is half descent. I get over 150 frames in some of the FPS games I play and my monitor runs at 130 hz at the resolution I play at. Therefore I'm actually seeing close to the FPS I'm getting while I play (130). Also in regards to Continuity27's comment about not noticing the difference between 85 and 120+ frames is crap. Some people can definitely tell a difference.

 

[Muscles]

Originally posted by: FlyingPenguin
Windows does NOT limit your video FRAMERATE in games.

Your framerate is capped by two factors:

- Any cap that exists in the game (most Quake engine games have a 72 FPS cap for instance, although it can be adjusted).
^^ Not quite accurate. It's possible that if you're playing online your FPS can be capped based on a server side setting. Quake 1's server side FPS cap I believe is 72 or 76 FPS but I know on the servers I play on for Quake 3 I get a solid 125 FPS all the time. Obviously if you're playing singleplayer and not online at all this information is completely irrelevant. Whatever FPS and refresh rate your hardware can output is what you'll be getting.

- The refresh rate of your monitor (if VSync is enabled).

With VSync enabled, your framerate can NEVER exceed your refresh rate, which is why those of us with LCDs should ALWAYS use the refresh override in our video driver settings to set 3D game refresh to 70 or 75 Hz (whatever your monitor supports). On an LCD you cannot distinguish between 60 and 70 Hz, but you want the refresh as high as possible for gaming.
This is exactly why most hardcore gamers will always prefer CRT over LCD. Most LCD's support only lower resolutions. Additionally, they only support lower refresh rates. CRT's don't suffer from these limitations as LCD's do.

 

[Spike]

Originally posted by: Muscles

Originally posted by: FlyingPenguin
Windows does NOT limit your video FRAMERATE in games.

Your framerate is capped by two factors:

- Any cap that exists in the game (most Quake engine games have a 72 FPS cap for instance, although it can be adjusted).
^^ Not quite accurate. It's possible that if you're playing online your FPS can be capped based on a server side setting. Quake 1's server side FPS cap I believe is 72 or 76 FPS but I know on the servers I play on for Quake 3 I get a solid 125 FPS all the time. Obviously if you're playing singleplayer and not online at all this information is completely irrelevant. Whatever FPS and refresh rate your hardware can output is what you'll be getting.

- The refresh rate of your monitor (if VSync is enabled).

With VSync enabled, your framerate can NEVER exceed your refresh rate, which is why those of us with LCDs should ALWAYS use the refresh override in our video driver settings to set 3D game refresh to 70 or 75 Hz (whatever your monitor supports). On an LCD you cannot distinguish between 60 and 70 Hz, but you want the refresh as high as possible for gaming.
This is exactly why most hardcore gamers will always prefer CRT over LCD. Most LCD's support only lower resolutions. Additionally, they only support lower refresh rates. CRT's don't suffer from these limitations as LCD's do.

For some of use those limitations are worth it for the other benefits. I run my Dell 2005fpw at 70hz and vsync all my games. Looks great to me and the screen is better for movies and general usage.

I used to use a program called "powerstrip" to lock my refresh rate at a certain number in each res. This was when my 21" CRT was my main monitor and I had issues with it defaulting to 60hz in any rez other than 1600x1200.

-spike

 

[Inigo Montoya]

Just use a tool like This (or any other one that does the same) (Just google radeon + refreshlock).

 

[EvilRage]

Okay, so...

I run two BFG 6800 GTs in SLI

I have my windows display properties refresh rate set to 85Hz (The max my monitor claims it can handle)

I have V-sync on

I generally get frames in the 60-100 range when playing CS: Source

I've noticed a huge improvement in visual quality after turning V-sync on. The tearing was distracting, and now it's gone. yay.

I haven't had any problems. Monitor is a Viewsonic G220fb.

 

[Philippine Mango]

Why do I get tearing depite having V-sync on?

 

[ryanv12]

Tearing? Whether V-sync is on or off, i've never had a problem with "tearing"

 

[Philippine Mango]

Originally posted by: ryanv12
Tearing? Whether V-sync is on or off, i've never had a problem with "tearing"

Well while the tearing isn't THAT bad, it's still tearing (it would tear only once) when I moved it very quickly (like turning the vehicle in vice city)

 

[Continuity27]

Originally posted by: FlyingPenguin
Windows does NOT limit your video FRAMERATE in games.

Your framerate is capped by two factors:

- Any cap that exists in the game (most Quake engine games have a 72 FPS cap for instance, although it can be adjusted).

- The refresh rate of your monitor (if VSync is enabled).

With VSync enabled, your framerate can NEVER exceed your refresh rate, which is why those of us with LCDs should ALWAYS use the refresh override in our video driver settings to set 3D game refresh to 70 or 75 Hz (whatever your monitor supports). On an LCD you cannot distinguish between 60 and 70 Hz, but you want the refresh as high as possible for gaming.

I was actually referring to refresh rate, not FPS, but anyways I was wrong in another way.

The problem has been rectified through service packs. No longer does Windows enforce 60 or 75hz in full screen applications despite what the user sets in his/her display properties. Now it stays the same between them. OpenGL on Windows might still be wrong though.