Trolljerk,
I know the refresh problem of which you speak. The dreaded 60hz OpenGL lock-down (you can fix this in D3D with DXDiag, but not OpenGL) that causes your eyeballs to hurt after 10 min of game play.
Whoever thought up this stupid idea obviously has never sat in front of a 22" monitor running 1600X1200 @ 60hz for any length of time.
This was wonderfully easy to fix with nvRefFix, but alas it was busted with nVidia drivers beyond 23.11, and the author abandoned the program. Man, what a crying shame that was because nvRefFix was one of those little gems you wanted to pay for even though it was freeware :)
It's been dismal since then. Several so-called RefreshRate fixers have come and gone, and none of them worked as easily or reliably as nvRefFix. What is really strange is that one program will work for some people, and won't work for others. In my case, NONE of them would work with one exception. RefreshLock. However, RefreshLock is a TSR and has to stay running to work. nvRefFix did it's work, and went away. You only had to run it once.
So, things have been pretty lousy in the 60hz Refresh Fix department.... Until this week!
I went to Guru3D to pick up a fresh copy of NVHardPage, and by golly there was another new Refresh Rate fixer listed as the newest file called RefreshForce 1.0. The write-up insinuated that it would fix the problem in ALL circumstances.
I downloaded it and tried it. It works, by golly, and it's a run-once utility like nvHardPage was.
And, it's a one-button fixer too. This has been something that's been missing as well since nvRefFix went under. Most of the other utilities make you sit and adjust every single frequency/color depth possibility individually, which is very tedious.
ReForce has a one-button approach that I think works well.
ReForce also addresses an issue that I don't recall being mentioned by any of the other utilities, and now that I've read about this I think it may be responsible for many of the Refresh Fixer failures out there.
It appears that for whatever reason, Windows XP can maintain duplicates of the Monitor Hardware record. If you don't adjust the settings in the right one, it will be like you never even touched it. The ReForce readme states that you should alter ALL occurances of your monitor.
Indeed, the first time I tried it, it didn't work and I said "Oh, great. Yet another one that doesn't work". Then I read the readme (of course we always do that AFTER the install :)), and saw this note. I went back, and sure enough in the pull-down menu where you choose your Monitor, there were TWO copies of it registered by WinXP. I had adjusted the one that Windows XP was NOT using. I did the one-button fix to all of the instances of my 22" Mistubishi, and tested again.
It was fixed!
I have no idea why I went on such a rant about this, other than I'm jazzed that this damned annoying problem has finally been fixed by someone, and I whole-heartedly appreciate it. I might just send the guy a check or something :)
TL
|