Download: GeForce 388.71 WHQL driver

#5503005

yosef019

2017-12-20 15:16

Should I buy the game now? I'm with i7 8700k @4.7 and Gtx 1080ti. 60 fps without drops?

#5503006

dr_rus

2017-12-20 15:17

r388_43-17 http://www.guru3d.com/files-details/geforce-388-71-whql-driver-download.html

What’s New in Version 388.71 WHQL Game Ready Provides the optimal gaming experience for PLAYERUNKNOWN’SBATTLEGROUNDS. CUDA Support Added support for CUDA 9.1 Application SLI Profiles Added or updated the following SLI profiles: •Warframe 3D Vision Profiles Added or updated the following 3D Vision profiles: • Black Desert - Fair • ELEX - Good • Forza Motorsport 7 - Not recommended • JX3 Online - Fair • PLAYERUNKNOWN’S BATTLEGROUND - Not recommended Software Module Versions • nView - 148.92 • HD Audio Driver - 1.3.35.1 • NVIDIA PhysX System Software - 9.17.0524 • GeForce Experience - 3.11.0.73 • CUDA - 9.1

Changes and Fixed Issues in Version 388.71 • /YouTube/: Flickering may occur when playing videos in full-screen mode. [2033196] • /YouTube/[Notebook]: Artifacts may appear when pausing video playback. [2033201] • Lines appear across the screen momentarily while booting into Windows. [200339233/1953061] • [NVIDIA TITAN V]: TDR error occurs and the display goes blank while playing a Blu-ray disc at high resolutions. [200364496] • [GeForce GTX 1080][Notebook]: The driver may not recognize or install the GPU.[2033168]

#5503011

squalles

2017-12-20 15:37

dr_rus:

r388_43-17 http://www.guru3d.com/files-details/geforce-388-71-whql-driver-download.html

dammit 388.59 are very bad drivers with this same branch and sub branch and these look same way waiting for main branch driver again btw vulkan updated?

#5503014

dr_rus

2017-12-20 15:44

squalles:

388.59 are very bad drivers with this same branch and sub branch and these look same way

Can't say that I had any issues with .59.

squalles:

btw vulkan updated?

No, same 1.0.56 as previously.

#5503017

-Tj-

2017-12-20 15:48

Hah was just thinking today, odd there is no new driver on the horizon, and here it is. 😀

#5503022

Blackfyre

2017-12-20 15:57

yosef019:

Should I buy the game now? I'm with i7 8700k @4.7 and Gtx 1080ti. 60 fps without drops?

Whoever told you that you couldn't achieve that before was lying to you. Unless you're talking about running the game at 4K, I am not 100% sure, but you should be able to by changing some settings around. I'm using a GTX 1070, and at 1080p & even 1440p my FPS doesn't dip below 60FPS with a few tweaks and changes to the settings, and that's prior to the optimisations in the current build (PUBG 1.0) being released tomorrow. Yes the game definitely needed optimisation for the majority of users. But if you have high end hardware and were willing to tweak down some of your settings, the game has been smooth for a while now (well over a month).

#5503027

dr_rus

2017-12-20 16:10

Doesn't mention this in the fixed issues but it seems that "Output color depth" doesn't reset to 8 bit on these on OS reboot anymore. ...Or maybe it's just because of me changing the display configuration after reboot.

#5503030

MIXXX

2017-12-20 16:14

I have been running 333.59 and they are performing well. I dont benchmark, it the games run smooth and no game or systems errors, they are keepers. I will update to these later today on 4 systems I have 1070 GTX , 1030 GT, 745 GTX and 520 GT so I prefer stability. PEACE

#5503038

khanmein

2017-12-20 16:43

@squalles By the way, 388.59 performed quite good & FYI, 388.71 is a lot smoother when I'm playing FIFA 18.

dr_rus:

Doesn't mention this in the fixed issues but it seems that "Output color depth" doesn't reset to 8 bit on these on OS reboot anymore. ...Or maybe it's just because of me changing the display configuration after reboot.

I think haven't fixed it. Since "Custom color settings are lost on reboot after upgrading to Windows 10 Fall Creators Update" still listed.

#5503059

Cryengine

2017-12-20 17:45

Thanks

#5503061

-Tj-

2017-12-20 17:48

The Division DX12 startup DSR'd 1440p, is still crashing and doesnt run full screen.. Now with this driver its even more buggy then with 388.59, tried 3 times now to switch to FS in time, but always fail.. lol like a game within a game xD Edit: I restarted pc and then launched in steam and now it started fullscreen dsr normaly..

#5503065

goodsmac

2017-12-20 18:08

Is the green flickering bug in The Division fixed?

#5503070

Raider0001

2017-12-20 18:37

goodsmac:

Is the green flickering bug in The Division fixed?

My mouse doesn't control protagonist sometimes and You want such a small tiny bug fixed...

#5503090

GroinShooter

2017-12-20 19:25

goodsmac:

Is the green flickering bug in The Division fixed?

Probably not.

Raider0001:

My mouse doesn't control protagonist sometimes and You want such a small tiny bug fixed...

Oh it definitely isn't a small tiny bug, there's green flickering artifacts at the top of the screen and sometimes everywhere which results in the game being unplayable. This is only an issue under DX12. DX11 is fine, doesn't make it any less of a concern though.

#5503093

coth

2017-12-20 19:35

Oh, that's where hundred millions of raised money by PUBG gone - premium screenshot photoshopping.

#5503094

Raider0001

2017-12-20 19:36

GroinShooter:

Probably not. Oh it definitely isn't a small tiny bug, there's green flickering artifacts at the top of the screen and sometimes everywhere which results in the game being unplayable. This is only an issue under DX12. DX11 is fine, doesn't make it any less of a concern though.

to be honest I did not know about that bug, I thought it was like a 1 green pixel flashing somewhere :P

#5503102

thesebastian

2017-12-20 20:11

Provides the optimal gaming experience for PLAYERUNKNOWN'S BATTLEGROUNDS Is that statement true or just nvidia smoke? If some benchmark appears comparing a 2 month old nvidia driver with this one released today, (testing the PUBG version that will be released today/tomorrow) please let me know! For now I'll think it's just marketing.

#5503135

dr_rus

2017-12-20 21:51

One thing has been bothering me for some time now: why do NV drivers create compute shader cache in a "Temp" folder located in the root of drive C:? This isn't a default Windows "Temp" location and in fact nothing but NV drivers use it if Windows "Temp" locations are kept at their defaults. The drivers are in fact creating this "Temp" folder in C: root if it's not there. What's even more annoying is the fact that you can find other caches in other locations too: - NV_Cache in Windows\Temp - GLCache in AppData\Local - cep_cache in AppData\Local\Temp - Another NV_Cache in AppData\Local\Temp As far as I can tell, all of these are related to NV's shader caching and it's just very weird to see them being scattered all across the disk C: instead of being kept in one folder - preferably not the "C:\Temp" one as such folder doesn't exist in modern Windows.

#5503152

EdKiefer

2017-12-20 23:16

dr_rus:

One thing has been bothering me for some time now: why do NV drivers create compute shader cache in a "Temp" folder located in the root of drive C:? This isn't a default Windows "Temp" location and in fact nothing but NV drivers use it if Windows "Temp" locations are kept at their defaults. The drivers are in fact creating this "Temp" folder in C: root if it's not there. What's even more annoying is the fact that you can find other caches in other locations too: - NV_Cache in Windows\Temp - GLCache in AppData\Local - cep_cache in AppData\Local\Temp - Another NV_Cache in AppData\Local\Temp As far as I can tell, all of these are related to NV's shader caching and it's just very weird to see them being scattered all across the disk C: instead of being kept in one folder - preferably not the "C:\Temp" one as such folder doesn't exist in modern Windows.

Yeh, I noticed this to for a while now. I even added exception folder paths of it in CCleaner so it saves them. When you look at the timestamps they all seem relatively new so its not that one path is not used anymore, seems random with dates.

#5503155

dr_rus

2017-12-20 23:27

Well, another weird thing is that if you just delete C:\Temp with its contents then the driver would seemingly use C:\Users\...\AppData\Roaming\NVIDIA\ folder instead and will not re-create C:\Temp folder - which you'd think should be a default cache location from the start.