Nvidia has finally released a new driver update in which they claim to have fixed the issues causing the blackscreen effect on Oculus Rift headsets. Last week, one of their support team members stated, “We just fixed this bug and will roll out the fix to users in our next GeForce Game Ready driver later this month.” The new Nvidia Driver update number is 391.24 and comes with many new features and patches.
Nvidia Driver 391.24 new features:
Provides the optimal gaming experience for
• Kingdom Come: Deliverance,
• War Thunder,
• Black Desert Online,
• Metal Gear Survive, and
• Fortnite, including support for ShadowPlay Highlights in Battle Royale mode.
• Sea of Thieves
Adds support for NVIDIA Freestyle which lets you apply post-processing filters to your
games while you play.
eGPU
Added pop-up balloon to alert the user if an eGPU has been connected or
disconnected.
NVTray
Due to popular demand, the NV Tray has been added back in this release.
Added or updated the following SLI profiles:
• DIRT 4
• Hot Lava
• Metal Gear Survive
• Ode
• Total War: WARHAMMER II
• X-Morph: Defense
Added or updated the following 3DV profiles:
• FIFI – Good
• Kingdom Come: Deliverace – Not recommended
• Metal Gear Survive – Fair
Limited or no support with 391.24 driver update:
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.
Negative LOD bias clamp for DirectX applications is not supported on Fermi-based GPUs and later.
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.
Fixed issues with 391.24 driver update:
1. [HTC Vive][Oculus Rift]: The VR headset stops working after several launches of the application or after resume from system Hibernate mode. [200395208/2048746]
2. [NVIDIA Freestyle]: NVIDIA Freestyle not enabled for supported games. [2068793]
3. [Media Player Classic Home Cinema]: When launching a video, the system stutters momentarily. [2070328]
4. [G-SYNC]: Alt-tabbing windowed games with G-SYNC enabled and V-Sync ON ingame causes stuttering and drop in frame rate. [2053877]
5. [Firefox]: Driver TDR error may occur when using Firefox. [2049523]
6. [Notebook][Surface Laptop]:Blue-screen crash may occur when installing the driver. [200392051]
7. [Volta GPU]: The display flickers continuously after disabling and enabling the GPU using Device Manager, or when rebooting the system [200391003]
8. [GeForce GTX 1060][Rise of Tomb Raider]: Flickering/corruption occurs when opening the in-game options UI. [200351146]
While Nvidia claims that these issues have been fixed, Oculus Rift users are still complaining that the blackscreen still appears with the update. For now, it is advised to still stay on 388.59 until further notice. You can check out all the patch notes here.