Nvidia GeForce 335.23 WHQL - Download & Discussion

Great, I can call off the party, the bug is not fixed in my opinion :bang:

Ok, if they mean that only one screen is used if I click on the maximize button, then it is fixed. But this was already working in my last driver version.
If I move the window to the Top Border, it still uses all three screens :bang:

Moving windows is not sluggish anymore, so at least some bugs are fixed.

I will stay with this driver for the next days and check if there are more bugs compared to my last version. If not I will keep it, Game performance looks ok atm...

 

OpenCL is still broken. :bang: Used in madVR video renderer NNEDI3 chroma upscaling and image doubling. Back to 327.23...

 

Shadow issues remain in Lockheed Martins Prepar3D. Dark region around the users aircraft (as shown in the previous driver thread), with shadow options Terrain Receives Shadows flag and Shadow Quality above Medium.

Forcing Supersampling via Inspector causes coloured blocks inside the aircraft Virtual Cockpit.

Filled in the report

Supersample issue... this app needs some support and profile please nV.

 

Hmm Branch: r334_89-21 - any performance advantage over the 334, 89 driver ?

 

No, it's not resolved.

 

Hey Painter, I have been using the Quattro 332.50 with great success with P3D V2.1. All the 334 drivers gave me these coloured dots as in your screenshot, and this includes the Quattro 334's. P3D V2 simply don't like this branch.

 

Yes, thanks ... same here 332.50 or 59[CUDA] are the last to work properly with P3Dv2. Which is fine if you only run P3D or FSX and can roll back, but I would like to take advantage of newer drivers for other games.

I hope LM and nV can link-up to give it some proper support, maybe gaining some performance and better AA while we're at it

 

Yes not fixed.

Manuel G any news on this please.

I really would like to use NNEDI3 in MadVR and have the latest NV drivers for gaming.

 

They claim the actual fixed vsync with framelimiter threw inspector?!@ is this true ?

 

Can't argue with that! lol!

 

thanks for the info, said to hear

 

Any SLI fix for Titanfall?.

I can't try it right now (at work).

 

jerks? Superiority complex much?


FYI its in 1st post.

 

Damn Tj. This new members are getting worse with each new sign-up. :bang:

 

If you use the latest drivers, and not 327.23, all the shadows in the game bug out in DX11 while using SLI (it is using those bits). To acess DX11 in the game you have to turn it on in the menu.

If you use those same bits in 327.23 and have DX11, you do not get the problem in SLI. So therefore, some driver regression after 327.23 is causing the error.

 

^
I see, maybe it will end in next driver branch. Well they got your reports so hopefully they're working on it.

Whats worse he seems to imitate someone with a very similar name - also uses same avatar


Anyway back ot, still no complains with this driver.. Played BF3 before 64tdm and it ran uber smooth all the time, just like 331.87.

 

Yes, confirmed. Still not fixed

 

Hmm Branch: r334_89-21 - any performance advantage over the 334,89 driver ?

 

Played a couple of rounds and so far no issues.

 

Any news, good or bad, for MW: O, or the underling Cryengine?