Optimizations for 2 New Games To Keep Your Nvidia Graphics Cards On Top Of The Action
Hey gang, Nvidia has released a new GeForce Driver. The GeForce Driver 419.35 has plenty of optimizations for The Division 2 along with Devil May Cry 5. The other game GeForce Driver 419.35 optimizes is Apex Legends. You don’t want to use the 3D Profile for Devil May Cry 5. Those are the main things to note with this release. You can see a list of the fixes in the list below.
What’s New in Release 418
This section summarizes the driver changes previously introduced in Release 418.
Security Updates
Version 419.17 added security updates for driver components.
See the NVIDIA Security Bulletin 4772 for details.
See also the section “Driver Security” on page 12 for actions to take to mitigate
vulnerabilities.
New Features
Added support for
• GeForce GTX 1660 Ti
Implemented performance improvements on multiple titles, such as Witcher 3. when
using G-SYNC and SLI on Pascal and Maxwell GPUs.
NVIDIA Control Panel
Added new Developer->Manage GPU Performance Counters controls as of version
8.1.950.0
Video Codec SDK 9.0 (Released Feb 11, 2019)
Included Features
• Supports NVENC/NVDEC on NVIDIA Turing GPUs
• NVENC API has been updated to support HEVC B-frames on Turing GPUs.
• NVENC API adds the capability to output the encoded bitstream, and motion
vectors from Motion-Estimation-only mode to video memory. This avoids the
overhead of copying the output from system to video memory for processing
pipelines operating directly on video memory.
• NVENC API now accepts CUArray as an input buffer. The SDK contains a sample
application to demonstrate how to feed Vulkan surface to NVENC using VulkanCUDA interop.
More information: https://developer.nvidia.com/nvidia-video-codec-sdk
Optical Flow SDK 1.0 (Released Feb 11, 2019)
This is a new API for Optical Flow and stereo disparity hardware engine, available on
Turing GPUs.
More information: https://developer.nvidia.com/opticalflow-sdk
Release 418 Graphics Drivers for Windows, Version 419.35 RN-08399-419.35_v02 | 6
Chapter 2 : RELEASE 418 DRIVER CHANGES
Application SLI Profiles
Added or updated the following SLI profiles:
• Anthem
• Apex Legends
• Assetto Corsa Competizione – AFR enabled for Turing GPUs
• Battlefleet Gothic: Armada 2 – AFR enabled for Turing GPUs
• Far Cry New Dawn
• 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
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.
Release 418 Graphics Drivers for Windows, Version 419.35 RN-08399-419.35_v02 | 7
Chapter 2 : RELEASE 418 DRIVER CHANGES
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.
Release 418 Graphics Drivers for Windows, Version 419.35 RN-08399-419.35_v02 | 8
Chapter 2 : RELEASE 418 DRIVER CHANGES
Advanced Driver Information
This section contains the following additional information about the driver:
Differing GPU Voltages in SLI Mode
3D Compatibility Mode
Help for Resizing Your HDTV Desktop
Understanding the DirectX Information Shown in the NVIDIA System Information
Window
Differing GPU Voltages in SLI Mode
When non-identical GPUs are used in SLI mode, they may run at different voltages. This
occurs because the GPU clocks are kept as close as possible, and the clock of the higher
performance GPU is limited by that of the other. One benefit is that the higher
performance GPU saves power by running at slightly reduced voltages.
An end-user gains nothing by attempting to raise the voltage of the higher performance
GPU because its clocks must not exceed those of the other GPU.
3D Compatibility Mode
3D Compatibility Mode is an NVIDIA proprietary rendering mode for 3D Vision that
improves the 3D experience for many key DirectX 10 and 11 games. NVIDIA continues to
add game support with new driver versions.
Requirements and Compatibility
Games must be run in DirectX 10 or DirectX 11 mode.
Not compatible with 3D Vision Surround.
Switching Compatibility Modes
Games with 3D Compatibility Mode will launch in this mode by default. You can switch
between 3D Compatibility mode and standard 3D Vision mode as follows:
1 Before starting the game, enable Advanced In-game Settings in the NVIDIA Control
Panel:
a Open the NVIDIA Control Panel and navigate to the Stereoscopic 3D->Set up
stereoscopic 3D page and click Set Keyboard Shortcuts.
b Click the Show advanced in-game settings arrow if the section is not expanded, then
select Enable advanced in-game settings.
c Click OK.
2 Press Ctrl+Alt+F11 during the game to toggle between 3D Compatibility mode and
standard 3D Vision mode.
Changes and Fixed Issues in Version 419.35
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
[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]
[Batman: Arkham Origins]: PhysX fog renders incorrectly [2451459]
[Turing][Star Citizen]: The game flickers and then crashes to the desktop. [2518104]
[GeForce RTX 2080][PhysX][Assassin’s Creed 4 – Black Flag]: Smoke dispersal appears
accelerated. [2498928]
Microsoft.Photos.exe randomly crashes. [200496899]
NVDisplay.Container.exe causes high CPU usage. [200496099]