NVIDIA Releases 372.90 WHQL Game Ready Driver
by Daniel Williams on September 22, 2016 1:00 AM EST
Not to be outdone by AMD, NVIDIA also has their own driver release this evening, with the release of driver version 372.90.
Among the fixes in this latest drivers includes several game stability and G-Sync issues. In Mirrors Edge Catalyst NVIDIA has fixed an issue with the the Intensity slider, flickering has been fixed in Star Wars the Old Republic, and a crash with extended gameplay sessions on Rise of the Tomb Raider has been buffed out. Meanwhile G-Sync has received two fixes this time around, with with NVIDIA addressing lag in G-Sync windowed mode, and removing screen tearing in World of Warcraft that was occuring with in game V-Sync enabled.
A more impactful fix, since this issue made the news a couple of months ago, is a fix for the HTC Vive when running the video feed through DisplayPort. It turns out that the headset was not lighting up despite connecting, but those who wish to use DisplayPort instead of HDMI for their VR endeavors should now be able to do so. Lastly, NVIDIA Ansel will be enabled by default in the driver for white-listed games.
Bundled in with all of these fixes we are also given game ready support for Forza Horizon 3, the latest racing game to be published by Microsoft Studios. Forza is seeing release next week on Tuesday the 27th, though Ultimate Edition owners will get a head start this Friday.
Anyone interested can download the updated drivers through GeForce Experience or on the NVIDIA driver download page. More information on this update and further issues can be found in the 372.90 release notes.
Source: NVIDIA
Facebook
Twitter
RSS
32 Comments
View All Comments
damianrobertjones - Thursday, September 22, 2016 - link
Yay! Let's hope that it installs Vulkan without asking me, again. /sWithoutWeakness - Thursday, September 22, 2016 - link
Why would you not want Vulkan? I understand not wanting something installed if you specifically uncheck the box during setup (I don't need 3D Vision drivers for my 2D monitor) but I'm more curious why you are looking to avoid Vulkan?damianrobertjones - Tuesday, September 27, 2016 - link
It's not that I have anything against Vulkan... I just want the OPTION to not install it. I don't really care other than that but at no point was I asked to install it.These companies should stop doing this stuff!
m16 - Friday, September 30, 2016 - link
Your programs, all of them come with dozens of libraries, executables, services and files, and you're not privy about them. Even on Linux this is the case when you install software.Unless you run a secure box for something specific (In which you wouldn't be gaming to begin with), this is just pointless complaining.
You can just turn around and uninstall vulkan after it is installed. Be outraged when you can't, or don't be at all when it is a part of the driver permanently and it is not published anywhere.
FriendFive - Thursday, September 22, 2016 - link
I got this last night and it broke Fallout:New Vegas so I reverted to 368.81.Mr Perfect - Thursday, September 22, 2016 - link
Yeah, they broke New Vegas, Fallout 3 and Skyrim a couple versions back. The real kicker is the bug is now listed as a not-caused-by-our-drivers issue, so I guess they have no intention of fixing it.From the patch notes:
[Windows 10][Bethesda Softworks games (Fallout 3, Fallout New Vegas, Skyrim)] Games crash when launched. [1802925]
Mr Perfect - Thursday, September 22, 2016 - link
One of the nVidia staff commented on the bug on their forums. Guess it's MS's problem.ManuelGuzman: The new Windows 10 Anniversary Update had a specification change that required our display driver to output a different string from the previous drivers in the past. This has affected some games which were unfortunately developed with the assumption that the value would never change. We are working with Microsoft to find a solution. Drivers 368.81 and below are WDDM 2.0. R370 and higher drivers are WDDM 2.1.
wolrah - Thursday, September 22, 2016 - link
That sounds like it's Bethesda's problem to me. If the spec doesn't say that string remains static, but Bethesda's games assume it does and break when it changes, that's 100% Bethesda's fault. This is just like when Vista came out and app vendors who were doing things they weren't supposed to claimed that Vista "broke" their apps when in reality it was just XP didn't strongly enforce the rules.Mr Perfect - Friday, September 23, 2016 - link
This is true.I'm just hoping that MS can do something, because Beth sure doesn't care. You have to apply community fixes even to get Fallout 3 running on 7.
HollyDOL - Friday, September 23, 2016 - link
Bethesda is quite famous for their coding quality and they have some history. But at least they seem to improve over time... a bit. Arena couldn't be finished without patch at all and crashed alot. Daggerfall was a crash hell, but hey, at least it was possible to finish it (if you had holy patience with crashes).It shouldn't be that difficult for Bethesda to fix their junk (especially if it is just some string parsing thing as it seems).
I am not sure I'd want system infested with things like
if (executable == "skyrim.exe" || ...) magicString = "A" else magicString = "B"
I know it sucks because pple want to play older games on newer systems, but from developer perspective, if you can't follow specs you should be destined to fail big time - especially because it forces other developers to waste time duct taping your crap. It's just too bad general public will often blame something that is not to be blamed at all - in this case majority will blame Windows 10 no matter whether it is the actual 'bad boy' just because it's cool to blame it for everything including bad harvest in summer 1773.
So now it would be interesting to find out who exactly violated the specs - Microsoft, nVidia or Bethesda.