260.93 developer driver

gave these another go after i stripped my card from shell and backplate and played big bad wolfie for while

temps reach 100/106C really fast in wow, even with window open to get some cooler air

260.63 was 1st driver i ever had emergency shutdown from temps, was playing with Vindictus beta gfx settings while it happend

so they finally made good performance drivers with crispy gfx and my card cant take it :bang:

think i go compare temps with 182.50 ->

edit: actually compared to 185.97 wddm1.1 and it peaked 82C, ave 78C
edit2: 257.15 is at 92/92C

 

It actually depends on the person montior and the person, just because you dont notice jaggies do not mean no one esle does. I get the same comment about me shouldnt use AA at my native but I do because i notice the jaggies.

 

Yeah completely subjective...

 

I confirm.
It was corrected on 258.xx and the bug appeared again in 259 and 260

 

MoH does not work with dx11(ctd after end of round). No one knows what the exact problem is or who's at fault. DX10 and 9 work with mulitplayer. Single player only is dx9 as it uses a different game engine.
According to ManuelG at nVidia's forums the 260.93 developer driver already have the gpu optimization for MoH. BFBC2's gpu optimization is coming in the next release.

 

I installed these and they gave me two very weird issues.

After I installed, if I right-clicked the desktop, I'd get an endless "waiting circle" animation (AKA The Rotating Hourglass). It just keeps going, and going, and going..... and going. Only way to end it is to re-boot.

If I go into the control panel and try to start the NVIDIA Control Panel, nothing happens. Literally nothing. The control panel doesn't even try to launch.

So, I re-installed 260.89. I'll take a pass on these developer drivers.

 

i had that with 260.63, the workaround was forced log off and log on; and only then i was able to start nvcpl.

 

?

Strange problems for you guys, i don't have any problems with this drivers! This drivers are better for me, than 260.89. Also ncpl works without problem. Finally fixes my 59Hz bug! :banana:
All in all - great work nVidia, but please don't (stop) turn around

 

I had this issue as well. Hopefully they fix it if they ever plan going public with these drivers.

 

Yep same issue with control panel. If you kill one of the nvvsvc.exe from the task manager the CPL will launch but with most of the settings missing. SO back to the WHQL.

 

I don't know how you guys have the control panel issue. For me this is a nice driver set, everything works great. Keep up the good work nvidia.

 

Yep, everything is fine here too.

 

those of you stating its fine what OS are you using?

 

I just installed these and I have absolutely no issues with the control panel. Performance seems to be very good so far, a mixture of the 260.78 Quadro and the latest 260.89 WHQL.

 

Can anyone test if this still happens in Mass Effect 1:

 

Yes , it will be fixed in the next driver

 

Are you sure? Did NVIDIA say that it will be fixed?

EDIT: Their tech support guy @ NVIDIA forums apparently said that.

 

No i'm really good at making things up :3eyes:

 

That's classic omg thanks for the morning laugh ,almost spilled my coffee on to my G19 tho:eyebrows:

 

that falout L V sturtering it will be fixed or we need game patch?uke2:?

Using 260.89 whql
msi after burner 2.0.0 (low detection)
fraps 3.2.2