Vista and that 60Hz gaming bug - again!

[VorLonUK]

I had this problem with XP, until a plethora of utilities appeared as it was affecting most gamers out there. I'm still using a CRT and usually have the Refresh rate at no lower than 85Hz.
Scouring the Web and trying my favourite and trusted utilities, it appear that they don't work with Vista and/or the current round (in my case) Nvidia drivers 169.44 for Vista 64.

I've researched and tried some of the following:-
Direct Refresh
Refresh Lock
Refresh Force
RivaTuner
PowerStrip

to no avail so far.
Before with XP I used NvTray which included NvTweak, which allowed the old style Nvidia Classic interface to be switched on and enable a host of extra features - but for some reason the later Nvidia drivers and or Vista or the combination of the two will not allow these options to be set. Or if they can be set they have absolutely no affect.
My normal Vista desktop Vertical Refresh setups as to what I want it to be 1280x1024@85hz, but so far the Crysis Demo has been stuck at 60Hz.

I wondered if this was just a one off with the Crysis Demo, as was the Demo of battlefield 1942 way back when it was released, but searching the interweb, it seems to be a whole new problem with Vista.
Most the utilities that appeared when it was a problem with XP are now quite dated and only a few have been updated.

Does anyone else here game with Vista 64 (or 32bit) and still use a CRT monitor? If so have you had to force your Refresh rate up from 60hz and if so, what utility are you using?

Thanks..

[zerotol]

I have a friend that had the same issue , he fixed it by doing something in directX.Ill post his solution when i speak him

[Naki]

DXDiag ---> More Help ---> Override...?? This allows you to set a custom HZ setting for DirectX games (not OpenGL though).

[VorLonUK]

DXDiag ---> More Help ---> Override...?? This allows you to set a custom HZ setting for DirectX games (not OpenGL though).

That doesn't appear to be available on the DXDiag Utility under Vista 64 or Vista 32 (Home Premium). I've checked both my PC and my laptop.

[Intuit]

Remember that all the GUI interface does is 'flip a few switches' in the registry. (and in some cases the file system) Ignoring the GUI and making edits directly to the registry may be the key.

The hangup may be that the V64 drivers may have well been rewritten as opposed to tweaked and recompiled; so this may not work.

But to find where the XP32 O/S stores the changes, close all unecessary programs. then undo the refresh rate lock.  Export a copy of the HKLM\System portion of the registry then reapply the refresh rate lock.  Export a second copy of the HKLM\System portion of the registry then use Microsoft's WinDiff.Exe utility to comare the two exported files to reveal where and how the OS drivers stores the changes.  Chances are (and this is driver dependant) the change is stored somewhere under the HKLM\System\CurrentControlSet\Control portion of the registry.

Anyway, use that new founded information to then look under V64's hood and see if you can find and then manipulate the necessary registry key value.