Due for wide release tomorrow is the Star Wars Battlefront Beta, a technical test for the game being run ahead of the game's full launch in November. As is often the case for major game releases, NVIDIA is pushing out another Game Ready WHQL driver release for Battlefront, this time with version 358.50.

The big news in this release is of course improved support for the Battlefront beta. However as this is also the first driver release from the R358 branch, 358.50 also contains several other improvements. On the API side of matters, R358 adds support for the OpenGL ARB’s previously announced 2015 ARB extensions, as well as support for OpenGL ES 3.2. Furthermore NVIDIA has made some improvements to GameWorks VR, further knocking out bugs and improving VR SLI support.

Meanwhile on the Windows 10 front, this driver release finally resolves the issues utilizing SLI and the NVENC encoder at the same time, meaning ShadowPlay and GameStream now work with SLI setups. Support for stereo rendering under DirectX 12 with an SLI setup has also been added, making this the first time we’ve seen stereo rendering under DirectX 12 addressed. On the other hand Fermi owners hoping to find WDDM 2.0 support in this driver release will be disappointed, as a quick check finds that Fermi cards continue to use the WDDM 1.3 path under Windows 10.

Finally, NVIDIA’s release notes make an unusual mention of “Added controls for forcing the use of the integrated graphics processor or the NVIDIA GPU on Optimus notebooks.” Though at this point we’re a bit unsure why this note is in here since NVIDIA has offered Optimus GPU selection controls for some time now.

As usual, you can grab the drivers for all current desktop and mobile NVIDIA GPUs over at NVIDIA’s driver download page.

Source: NVIDIA

POST A COMMENT

20 Comments

View All Comments

  • D. Lister - Wednesday, October 07, 2015 - link

    Yet another WHQL certified driver update, so soon, and for a beta release? And that's WITH the daily profile and optimal settings updates plus the weekly Geforce Experience updates. This is getting a tad ridiculous, isn't it? Reply
  • HighTech4US - Wednesday, October 07, 2015 - link

    Well you could go the AMD route where almost every driver they release is a BETA driver Reply
  • D. Lister - Wednesday, October 07, 2015 - link

    @HighTech4US

    Since the good folks at AMD don't do much of beta testing anymore, the drivers are seemingly released to the public in a very alpha state, where paying customers find the bugs FOR AMD. A lot of AMD users prefer to look at this bug hunt as an ongoing free-to-play game that comes bundled with the drivers.
    Reply
  • eek2121 - Thursday, October 08, 2015 - link

    I kind of feel like most of you people don't actually own an AMD card. Find me one game that doesn't actually run under an r9 290 or a radeon 6970 or runs, but with graphical errors. You won't...because there aren't any. Reply
  • Cryio - Thursday, October 08, 2015 - link

    He doesn't own one. I'm running a 280X that I run under Windows 7, W8.1 and W10 and I've never had any kind of drivers issues. Reply
  • Michael Bay - Thursday, October 08, 2015 - link

    Oh, your anecdotal evidence is so much more convincing than his. Reply
  • shing3232 - Friday, October 09, 2015 - link

    I own two 290 run under 8.1 and Win10, so far so good as i own 290s for a year. The only major problem was when you encounter games that do not support CF. Reply
  • heffeque - Thursday, October 08, 2015 - link

    Well... other than the 15.9 problem that was quickly solved, I find nVidia's WHQL a lot more problematic and unstable than most AMD Beta drivers. I don't know where people find that nVidia still has stable drivers compared to AMD a decade ago, but it sure hasn't been the case for years now. Reply
  • shing3232 - Friday, October 09, 2015 - link

    970s do have terrible drivers these day and their WHQL are unstable because they release so quick one after one. Reply
  • Cryio - Thursday, October 08, 2015 - link

    Stop spreading FUD. You never even owned an AMD card probably. Reply

Log in

Don't have an account? Sign up now