Darren Hodgson:

Not sure if this is a game or driver bug but... Game Settings: 2560x1440, Ultra preset (incl. TAA + FXAA), V-Sync = Disabled I've noticed what appears to be texture seaming issues on the walls, tables and even that nurse's skirt in The Evil Within 2. It looks like they're made up of those of squares separated by thin black lines. It's hard to describe but hopefully this image should explain it better: https://www.dropbox.com/s/ioe2y9bpgiwl5vb/TEW2_2017_10_14_13_54_44_253.jpg?dl=0 Anyone else seeing this issue?

Seen that bug for a lot of people while watching streams. Could be a Game Bug, seeing how poorly optimized it is as well.

-Tj-:

Also there is a utilisation issue, gpu doesnt go full 90-100%, usually 60-80%, with fps drops.. cpu usuage is waay bellow average, 20-30% max.

That's on all drivers on GF cards. Hard to say if it's a driver or a game issue.

Darren Hodgson:

I've noticed what appears to be texture seaming issues on the walls, tables and even that nurse's skirt in The Evil Within 2. It looks like they're made up of those of squares separated by thin black lines. It's hard to describe but hopefully this image should explain it better:

Don't force AF, let the game use it on it's own. TEW2 is built on id Tech 5 with its s/w implementation of PRTs and thus the rendering breaks if you force AF in this engine.

quote : Also there is a utilisation issue, gpu doesnt go full 90-100%, usually 60-80%, with fps drops.. cpu usuage is waay bellow average, 20-30% max. quote its happening to me as well. its game issue, highly the modified engine. besides, this game is awful i uninstalled it after a few hours.

Yeah there is definitely something wrong with game or driver or both.. When I lowered settings fps dropped instead of rising. I was in the living room - intro level, Ultra 53fps, high or Medium setting 44-47fps.. xD About AF, by TEW1 I forced AF in game cfg, did the same thing now (C:\Users\xxx\Saved Games\TangoGameworks\The Evil Within 2\base) I manually added these two lines image_anisotropy "8" (default is 2 if Im not mistaken) image_useCompression "0" and it looks clearer in the distance. Also driver forced vsync (adaptive) + 1 frame to render ahead + ingame 60fps vsync, RTSS made more stutters.

disq:

First time i'm seeing this when installing a driver from nVidia https://i.imgur.com/BzIylmj.png

That used to come up quite often in Windows 7 while installing nvidia beta drivers. I guess this is just the less colourful Windows 10 version

savannahmick:

This driver is causing weird issues with HDR and MPHC. Windows 10 and HDR have never worked for except with Mad VR and MPHC now it is broke! Geez! Also my screen is flashing twice when I exit MPHC but not with 385. Back to HDR I am surprised they haven't got it working since most newer decent TV's and a few monitors also have it now! 385 has no problems with MadVR HDR it works good so that's where I am at for now! Anyone else similar issues or ideas on issue or fix? Thanks!

yes it flashes twice, but you can stop it when enabling HDR before or after you see the colour is weird enter Windowed Full Screen. it's the drivers

alz-core397:

387.92 WHQL and GeForce Hot Fix Driver R387.98 breaks 3D VISION and stereoscopic 3d . im using 540M 2GB and when i installed them stereoscopic dissapears from nvidia control panel and causes restart sometimes. i rolledback to 385.28 and everything is OK. should i wait a new release? any suggestions?

Unless you have issues with games you currently play, I'd stay with the older driver and try the next set when Nvidia releases them. But make sure, when you upgrade, that you run DDU in safe mode and clean the old ones up first. If you haven't done this, try it and see if that helps. I'm using this set and no issues with 3D Vision. Mind you, my hardware is newer and support might be a bit better with the new drivers.

Interesting side effect with these drivers is when i use apple aerial screensaver with G-Sync enabled in fullscreen/windowed mode aerial runs smooth with previous drivers it stutters really badly and the minor flickering in world of tanks when going from garage to game seems reduced

dr_rus:

That's on all drivers on GF cards. Hard to say if it's a driver or a game issue. Don't force AF, let the game use it on it's own. TEW2 is built on id Tech 5 with its s/w implementation of PRTs and thus the rendering breaks if you force AF in this engine.

Actually, I wasn’t forcing anything originally (though I did try disabling MFAA in case it was that). Ironically, the issue is fixed if you DO force 16x AF in the game profile so clearly this *is* an engine bug, possibly one with this driver as well if it doesn’t happen on AMD graphics cards?

Xtreme512:

quote : Also there is a utilisation issue, gpu doesnt go full 90-100%, usually 60-80%, with fps drops.. cpu usuage is waay bellow average, 20-30% max. quote its happening to me as well. its game issue, highly the modified engine. besides, this game is awful i uninstalled it after a few hours.

Same issue with AMD cards so i am guessing a engine limitation, not optimised well.

Monchis:

It would be nice if the nvidia driver package deletes itself from c drive lol, gigas and gigas of wasted space from only two driver sets, folder even protects itself claiming it´s only using like 3mb of space but it´s not XD.

According to GE logs ability to clean up installation directory was added in 3.9.0. Don't know where, though.

Anyone using these drivers on shadow of war?

peppercute:

yes

Any difference from game ready drivers?

kilyan:

Anyone using these drivers on shadow of war?

Yes, they work perfectly fine with that game as do the v387.92 WHQL drivers (since the hotfix changes are not specific to that game anyway).

Divers are highly unstable in SLI configuration More so than any driver to date reverted back to 385.69 also drivers crash TitanFall2, Talos Principle (dx11), Shadwen, Dying Light, crash occurs within seconds. Crash occurs later in We happy few, when using the sli profile it came with. If I put in my own sli profile in we happy few using the 385.69, I get 93% utilization and rock steady performance/ When I use the 387 profile it only uses one card and crashes. (same with Echo) (385.69 no problem) Full crashes on game start (if SLI enabled) occurs in Halo CE, Doom, UT3, Soma, Andromeda, Resident Evil, Dishonored 2, Bioshock infinite (385.69 no problem) Additional observation: on games that don't crash - the load time before the screen refreshes and game starts - takes 3-12 seconds longer. Situation where crash occurs outside of above listed parameters (reproducible on two of my PCs): When Fast is selected in the v synch option When On (smooth) is selected in v synch When 10 bit (vs 8 bit) is enabled for monitor Driver seems ok if setting is left to "Application controlled" for v synch Driver seems ok if setting is left to 8 bit vs 10bit for monitor Driver seems ok if you don't plat any games at all On install, the 387 hard locks/blanks screen and doesn't come back after it finds the cards (other driver installs cause a few screen on off but within seconds come back to normal) The 387 cause a blank that does not return, reboot required, remoting in to see what's going on shows an error under application in event viewer and I have to do a remote restart. returning to 385.69 and custom profiles resolved issues and seems normal again. Also, even with ddu, this driver leaves a whole bunch of stuff everywhere in registry and some files in the program directory and program data that all had to be manually purged. returning to 385.69 and custom profiles resolved issues and seems normal again. my overall impression is that this driver has some much deeper included monkey work in it reverting (and cleaning the driver off the system manually) to 385.69 seems to solve the problem. 385.12, 385.41 and 385.69 did not manifest any of these issues. SLI profiles seem to work fine for all those and stability was not an issue. it could be that this driver (387) is fine with generic pc configurations, but in my situation its very unstable. I suspect they have made considerable changes, more than just some game profiles

@disq It's normal for non WHQL/Beta/Hotfix drivers...

venturi:

my overall impression is that this driver has some much deeper included monkey work in it

Haven't had a single issue with this driver yet.

dr_rus:

Haven't had a single issue with this driver yet.

I respect that and I'm glad for you I was just trying to provide feedback on the 387 driver but from your signature I don't see you're running SLI, ----in most of my issues is when SLI is enabled or available my build is somewhat more complicated but runs fine on 385.69: Supermicro X10DRG-Q (ver 1.10. bios 3.0) 2x (dual) E5-2699a v4 (44 cores/ 88HT) (2.4 to 3.7ghz turbo) 1TB ram DDR4 ecc reg (QUAD SLI) 4 Titan Xp (fully enabled) 2x NVMe 960Pro pcie 3.0 (os drives) amfeltec plx nvme 10x 850Pro SSD RAID (apps drives) 4k monitor (and *8k) Digital power supply 1600w Windows Server 2012 R2 Data Center

venturi:

but from your signature I don't see you're running SLI, ----in most of my issues is when SLI is enabled or available

Sure. But considering that SLI is a waste of money for some years now, with constant issues and about half of games not supporting it at all - I don't see how this driver is an issue really.

dr_rus:

Sure. But considering that SLI is a waste of money for some years now, with constant issues and about half of games not supporting it at all - I don't see how this driver is an issue really.

I respect your opinion , you're fortunate, because in my case I'm not able to run 4k, much less 8k with decent speed unless its SLI. maybe you have had a better experience at that resolution: What single card solution do you recommend for 4k and 8k?