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

POST A COMMENT

32 Comments

View All Comments

  • Michael Bay - Saturday, September 24, 2016 - link

    Gamebryo programmers back in 1999, most likely. Reply
  • Konndoor - Friday, October 28, 2016 - link

    It is Microsoft's fault for not fixing the exception handling. They knew that people were playing these games that are better than most of their new ones. Nvidia is just following the guidelines. A patch might me made for each game but that will take time for coding and testing.
    This whole thing is setup to sideline these heavily modded masterpieces like Fallout with TTW and Dagwood Super packed Oblivion.
    Meanwhile, Skyrim Remastered can save the day. It is a done-before game that is pretty but shallow. The gameplay is cheap if only thrilling. Not even as complex as Oblivion with no dual-wielding. The whole affair is just sad corporate maneuvering towards upping the bottom line.
    Reply
  • Konndoor - Friday, October 28, 2016 - link

    It's fixed. A modded fixed it. Use NVAC and it is at nexusmods. Reply
  • Konndoor - Friday, October 28, 2016 - link

    NVAC fixes the crashing without downgrading or rolling back the driver. The patch is at nexus mods. So, don't bother getting an entire team to work on something a random modded and programmer added in his spare time. Reply
  • Badgerboy1970 - Friday, September 23, 2016 - link

    I don't know if the crashing is supposed to be a universal problem because I was able to play Skyrim for about an hour last night with no crashes or any other issues at all. Currently using the Windows 10 64 bit with Anniversary update and GTX 1060 with the 372.90 drivers. Reply
  • SeanJ76 - Friday, September 30, 2016 - link

    It's the driver no doubt in my mind, I noticed much lower frame-times with 372.90 driver. Reply
  • Zak - Thursday, September 22, 2016 - link

    I can launch Skyrim and it runs but when I quit, Windows crashes to a black screen and I have to reset the PC. Maybe it's finally time to go back to Windows 7. I only use a PC for gaming and Windows 10 has been absolutely awful so far. In the few months I had more issues with games than in years of gaming on Windows 7. Reply
  • Morawka - Thursday, September 22, 2016 - link

    blame lazy game dev's for the bug. not ms.. read the post above yours my Mr Perfect Reply
  • kn00tcn - Friday, September 23, 2016 - link

    checking driver versions in a way that has been used for a decade then breaking many years after the game's release on a new OS (in fact a new update on a new OS) has nothing to do with lazy devs, what a lazy attack Reply
  • Michael Bay - Saturday, September 24, 2016 - link

    One look at KILOMETERS LONG list of fixes on any community patch is enough to see that coding standards are definitely not for Bethesda. Reply

Log in

Don't have an account? Sign up now