190.38 WHQL available

#

Yes, this does seem to be the case because I tried editing some of the names of the games in the Nvapps.xml profile as an experiment and they're are instantly reflected in the control panel profiles when you view them.

 

Grestorn explained the goings on with that.

the 2 nvapps files must be mirrored, otherwise the one with the latest edit date is merged into the registry. Nhancer and the CP edit only the data in the registry.

 

Overall is great but in GTAIV when SLI is enable I get flickering so I just disable SLI since it does not really use SLI any way.
The other problem is evga precision tool sometimes it does not detect the 2nd video cards temp or both cards. I have to reboot the machine. AA works fine in all games like COD4, L4D and HAWX.

 

OK, guys, 1 issue with these drivers (WHQL).
I can't chose 720p "quality" in nVidia control panel. I could do this in 186.24 BETA drivers. Now with these drivers I can't, and quality drop compared to 720p on movies in HD format is easily noticable. :bang:
I have 1 month old ASUS 192c connected with DVI to 8500GT.

Help, please.

EDIT: I did a clean install and deleted old PHYSX and DISPLAY drivers with DRIVER SWEEPER 2 beta 2.

 

i used 181.20 for this game i think with physx off,it worked great,try turning physx off as it messes up mirrors edge

 

cheers for the advice,i dont think i will bother installing these then if they mess up fallout 3

 

didnt know it was fault of driver, what driver works fine with fallout 3 though?

 

We are discussing this issue here:

http://forums.guru3d.com/showthread.php?t=301054

 

Ok im using dox modified 185.68 and they works just fine in Fallout 3

 

fallout 3 plays fine with 185 or 186 drivers,but with the 190's it gives crap performance

 

I tried these and it killed my performance.

I got rid of them and went back to my previous and all was good again

 

performance is fine on xp.... its probably like osomeone else mentioned... the power profile is causing it.

 

There is no such thing as a 60hz display.

they > ALL < work within a min and max range, which averages at 59.94.

59 is the correct mode, read directly from the EDID of the monitor, it was Vista and XP with the problem. Windows 7 has just corrected it.

oops, sorry for double post, i forgot i had posted a couple of hours ago.

 

I'm not sure you're accurate on your claim. While technically there is a slight variation, the EDID data should report correctly what the HDTV monitor refresh is. It's not going to vary with the tiny fluctuations. Many sets do not report EDID data correctly to the GPU

 

I'm very accurate on my claim.
XP ignored the EDID, Vista SP2 and Win 7 enforce it. If the displays EDID data is wrong then the only one who can fix the EDID is the manufacturer of the display, otherwise you must short the PIN responsible for DVI EDID/DCC detection and generate a customised inf.

The Detection is based on the Min and Max refresh ranges, and Windows 7 rounds up, while XP rounds down.

Because of this, Windows 7 is exposing a flaw in Displays which the range is from 58.94hz to 59.94hz, on XP the display would show as running at 60hz, where as it was running at 58.94.
On windows 7 the display rounds up to 59hz and displays that.

If you have any queries you can contact pSXAuthor and have him explain it to you at irc://irc.efnet.net/pcsx2

 

Settle down sonny, you just essentially agreed with what I said.
Chip meet shoulder.

Edit:

it effects HDTV's as well

i say its just crappy EDID problems again, requiring custom monitor infs to be made.

its all in the monitor...


Sound familiar? Later

 

well its not actually a problem, if your displays vendors are actually reputable and adhere to the EDID standard properly.

i know some games don't work with 59hz... but thats an issue in those games themselves, and not actually a 59hz bug.

 

Unreal 3 keeps crashing with these... :X

 

anybody know a well driver for left 4 dead

the games been freezing up too much lately as well as hardlocking too, even with these new drivers

+ the clocks stay stuck down-clocked when the driver crashes :bang:


i have a gtx 285, tried mat_queue_mode 0 and set affinity to cpu 0/1

still freezes/crashes

 

so what can we do to use 60hz??

i see 59hz and 60hz in the resolutions but if 60hz is selected it will always revert back to 59hz

if i lower my resolutions to where my monitor can do 75hz i can choose 75hz and it will stay 75hz