Nvidia GeForce Driver 418.91 Lets Battlefield V RTX Owners Rejoice!
Nvidia has just released the Nvidia GeForce Driver 418.91. Nvidia GeForce Driver 418.91 comes after just a little over a week after the previous one. New drivers seem to be coming out quite frequently from Nvidia and AMD. As usual, Nvidia didn’t get all the bugs with the new driver. The Nvidia GeForce Driver 418.91 is to get gamers ready for Metro Exodus. Nvidia GeForce Driver 418.91 introduces DLSS support for Battlefield V.
Metro Exodus Could Be A Positive Sign Of Things To Come For RTX Features
Considering Metro Exodus is the next big title using RTX features, this shows that the technology is going to become more mainstream and not just a gimmick made up by Nvidia. Hopefully, Battlefield V will get that boost you’ve been looking for with the added DLSS in Nvidia GeForce Driver 418.91, along with Ray Tracing. You can see the advantages of having DLSS support in the YouTube video below.
Nvidia GeForce Driver 418.91 is going to give you up to 40% faster frames per second in Battlefield V thanks to DLSS support added in. A list of all the bugs and fixes in the Nvidia GeForce Driver 418.91 are below.
Existing Support
This release supports the following APIs:
Open Computing Language (OpenCLTM software) 1.2 for NVIDIA® KeplerTM and later
GPUs
OpenGL® 4.6
Vulkan® 1.1
DirectX 11
DirectX 12 (Windows 10)
What’s New in Version 418.91 WHQL
Game Ready Drivers provide the best possible gaming experience for all major new
releases, including Virtual Reality games. Prior to a new title launching, our driver team
is working up until the last minute to ensure every performance tweak and bug fix is
included for the best gameplay on day-one.
Game Ready
Provides the optimal gaming experience when using DLSS and Ray Tracing in Battlefield
V and Metro Exodus.
Software Module Versions
• nView – 149.34
• HD Audio Driver – 1.3.38.13
• NVIDIA PhysX System Software – 9.18.0907
• GeForce Experience – 3.17.0.126
• CUDA – 10.0
New Features
Added support for NVIDIA TITAN RTX.
Implemented performance improvements on multiple titles, such as Witcher 3. when
using G-SYNC and SLI on Pascal and Maxwell GPUs.
Application SLI Profiles
Added or updated the following SLI profiles:
• Anthem
• Assetto Corsa Competizione – AFR enabled for Turing GPUs
• Battlefleet Gothic: Armada 2 – AFR enabled for Turing GPUs
• Life is strange Season 2 – AFR enabled for Turing GPUs
• NBA 2K19 – AFR enabled for Turing GPUs
• Space Hulk Tactics – AFR enabled for Turing GPU
Discontinued Support
32-bit Operating Systems
Beginning with Release 396, NVIDIA is no longer releasing Game Ready drivers for
32-bit operating systems for any GPU architecture.
NVIDIA Fermi GPUs
Beginning with Release 396, the NVIDIA Game Ready driver no longer supports
NVIDIA GPUs based on the Fermi architecture.
Limitations in This Release
The following features are not currently supported or have limited support in this driver
release:
Behavior Change in NvEncCreateBitstreamBuffer API of Video Codec SDK
In the NVIDIA driver, Release 415 and later, the behavior of the Video Codec SDK API
(NvEncCreateBitstreamBuffer) has been changed to return NV_ENC_ERR_UNIMPLEMENTED
instead of NV_ENC_SUCCESS when the encoder instance is configured to run in the motion
estimation-only mode. As an indirect consequence of this change, the AppEncME sample
Release 418 Graphics Drivers for Windows, Version 418.91 RN-08399-418.91_v01 | 5
Chapter 2 : RELEASE 418 DRIVER CHANGES
application from the Video Codec SDK prior to SDK version 8.2.16 will crash due to a
bug in the NvEncoder class.
The latest version of the SDK fixes this bug that affects the AppEncME sample
application. NVIDIA recommends downloading the latest version from https://
developer.nvidia.com/nvidia-video-codec-sdk.
Turing GPU Driver Installation on Windows 10
Drivers for Turing GPUs will not be installed on systems with Windows 10 RS2 or earlier.
This includes Windows 10 Threshold 1, Threshold 2, Redstone 1, and Redstone 2
operating systems.
Crescent Bay and OSVR Headsets on Multiple GPU Systems
With Release 367 and future NVIDIA drivers, Crescent Bay and Open Source Virtual
Reality development kit headsets will not work with VRWorks Direct Mode in systems
that contain GPUs from multiple vendors (for example, NVIDIA and Intel). For such
systems, please disable the Intel integrated graphics (from the system BIOS) in order to
use Direct Mode.
Experimental OpenCL 2.0 Features
Select features in OpenCL 2.0 are available in the driver for evaluation purposes only.
The following are the features as well as a description of known issues with these
features in the driver:
Device side enqueue
•The current implementation is limited to 64-bit platforms only.
•OpenCL 2.0 allows kernels to be enqueued with global_work_size larger than the
compute capability of the NVIDIA GPU. The current implementation supports
only combinations of global_work_size and local_work_size that are within the
compute capability of the NVIDIA GPU.
The maximum supported CUDA grid and block size of NVIDIA GPUs is available
at http://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#computecapabilities. For a given grid dimension, the global_work_size can be determined
by CUDA grid size x CUDA block size.
•For executing kernels (whether from the host or the device), OpenCL 2.0 supports
non-uniform ND-ranges where global_work_size does not need to be divisible by
the local_work_size. This capability is not yet supported in the NVIDIA driver, and
therefore not supported for device side kernel enqueues.
Shared virtual memory
•The current implementation of shared virtual memory is limited to 64-bit platforms
only.
Changes and Fixed Issues in Version 418.91
The following sections list the important changes and the most common issues resolved
in this version. This list is only a subset of the total number of changes made in this driver
version. The NVIDIA bug number is provided for reference.
Fixed Issues in this Release
[Battlefield 1]: Lines appear in the terrain with NVIDIA Control Panel anisotropic
filtering override enabled.[1969966]
[GeForce RTX 20 series]: Event ID 14 error appears in event viewer logs when Digital
Vibrance setting is changed.
Open Issues in Version 418.91 WHQL
As with every released driver, version 418.91 WHQL of the Release 418 driver has open
issues and enhancement requests associated with it. This section includes lists of issues
that are either not fixed or not implemented in this version. Some problems listed may
not have been thoroughly investigated and, in fact, may not be NVIDIA issues. Others
may have workaround solutions.
For notebook computers, issues can be system-specific and may not be seen on your
particular notebook.
Windows 10 Issues
[G-SYNC]: With a G-SYNC and G-SYNC Compatible display connected in clone
mode, flashing occurs on games played on the G-SYNC display with G-SYNC
enabled. [200482157]
[Apex Legends]: DXGI_ERROR_DEVICE_HUNG error message may appear and then
the game crashes.[2503360]
[Hitman 2]: Pixelated corruption appears in the game. [2504274]
[Iray][OptiX]: Iray GPU acceleration crashes and falls back to CPU acceleration.
[2503738]
[HDR][Ni no Kuni 2]: Enabling HDR causes the application to crash when launched.
[2483952]
[ARK Survival]: Multiple errors and then blue-screen crash may occur when playing
the game. [2453173]
[Batman: Arkham Origins]: PhysX fog renders incorrectly [2451459]
[Firefox]: Cursor shows brief corruption when hovering on certain links in Firefox.
[2107201]
Dynamic Super Resolution (DSR) is not available for monitors with 4k2k timings.
[2496987]
Random desktop flicker occurs on some multi-display PCs [2453059]
Windows 7 Issues
Random TDR events occur. [2500396]
[iRay][OptiX]: iRay GPU acceleration crashes and falls back to CPU acceleration.
[2503738]