The matter is simple really. Ever since Windows 2000, it has been hard-coded
in the OS to default to 60 Hz when it runs a fullscreen Direct3D or OpenGL
application. This, to my knowledge, was originally done to prevent potential
harm to the monitor. The problems with this "feature" were two fold: 1) It
would not revert back to the original setting after the D3D or OpenGL
application ended, and 2) The fact that if the display works correctly at the
slected refresh rate on the desktop, it will work correctly at the same
refresh rate and same resolution in a 3D application. Windows was not
intelligent enough to know that because Windows doesn't think. Programmers
think, and the ones responsible for this "feature" didn't think enough.
The solutions to this problem range from the down and dirty to the hardware
manufacturer-supported. The original fixes were programs that you could run,
select the refresh rates you wanted for each resoltution, and the program
would edit the Windows Registry and delete every refresh rate entry below the
target value for each resolution you specify. That way when Windows would
default to the lowest avail setting, it would only see the refresh rate you
had specified. The newer approach, and the one I use in XP revolves around
the graphics card manufacturer's drivers. Most new drivers have a section in
them for setting the refresh rate overrides for your display. Unfortunately
the beta drivers from NVIDIA for Vista do not appear to have that setting
available.
I, myself, am about to try one fo the older workarounds and see if that
works. I'll post here with my results. My problem is actually a bit more
complicated. The setting in the control panel is set for 85Hz, but Windows
is only running at 75 Hz (confirmed through the monitor's On Screen Display).
Changing it back to 60 Hz, then back up to 85 Hz doesn't seem to do
anything. I'm hoping this will fix my issue as well
-Paul