Jump to content

NVidia Updates


alt3rn1ty

Recommended Posts

The latest WHQL NVidia Driver update, 441.87, has a very nice new feature

Max Frame Rate

BhemUiZ.png

 

It can be set in the Global Settings, or in the individual Program Profiles

Its nice because you do not need any other advanced tools to set this now, just use the NVidia Control Panel. Typical use is when you want to stop stuttering due to the FPS going higher than the monitor / screen refresh rate, I have a laptop monitor which natively has a refresh rate of 60hz, so setting a cap on FPS to 59 means I never get any occasional refresh stutters with games with VSync on.

Release notes in downloadable PDF Format - http://us.download.nvidia.com/Windows/441.87/441.87-win10-win8-win7-release-notes.pdf

Link to comment
Share on other sites

Forgot to mention :

Something else thats new - If you are like me and your laptop machine is restricted to DCH NVidia drivers as opposed to the standard ones, you no longer have to select them specifically on the NVidia Download site ..

https://www.nvidia.co.uk/Download/index.aspx?

In the Download type for Geforce drivers just selecting Game ready drivers, now includes DCH as part of the installer, which are auto used if your machine is detected as needing them

 

I think this went through some teething problems over the last six months, confusing the end users in some cases for a while, and I think it has to do with Microsoft needing signed drivers (or something similar complicating the picture) .. Anyway whatever the underlying issues were, they seem to have been resolved now to make our lives easier keeping on top of the latest graphics drivers.

Link to comment
Share on other sites

Max frame rate is a nice addition, albeit a loooooooooong awaited one. Some games (especially gamebryo games but also other older games like No one lives forever, HoMM5 and SIms 3) need to have the max frame rate set on a number.

I remember Sims 3 refusing to accept the Vsync ON and having some fps numbers to the 600s or more. The game would render everything and anything at excessively high frame rates actually melting your GPU however advanced it was. Only way to cap the max frame rate was with Nvidia Inspector or Nvidia Profile Editor. It's nice that the feature is made standard with this driver update.

Link to comment
Share on other sites

  • 2 weeks later...

Vulkan API version 1.2 has been released :

https://www.khronos.org/news/press/khronos-group-releases-vulkan-1.2

https://www.khronos.org/vulkan/

 

I believe it will be included in NVidia Drivers version 441.99 and above (not currently available for my machine in the WHQL releases, but is in the beta drivers .. So probably going to be updated soon for WHQL)

https://developer.nvidia.com/vulkan-driver

 

I think its already available for AMD machines ..

https://gpuopen.com/vulkan-1-2-driver-available-latest-radeon-software-adrenalin-2020-edition-20-1-2/

Link to comment
Share on other sites

  • 2 weeks later...

NVidia Geforce drivers Version 442.19 WHQL has been released today

Apparently its still using Vulkan 1.1, not 1.2 yet .. I guess it will be in the next release

They tweaked the Max frame rate setting (introduced in the last version) so that you can set Frame rates as low as 20 or up to 1000

Release notes

Link to comment
Share on other sites

  • 5 months later...

v451.48 has been released and has now included the updated Vulkan 1.2

Release notes http://us.download.nvidia.com/Windows/451.48/451.48-nvidia-control-panel-quick-start-guide.pdf

Apparently it supports something called ..

"Hardware-accelerated GPU Scheduling when used with the Windows 10 May 2020 Update"

.. which may be better for Vulkan Games (ymmv)

Quote from here https://www.reddit.com/r/nvidia/comments/hf1292/game_ready_studio_driver_45148_faqdiscussion/

Quote

Driver performance testing

There is a lot to chew up here. The driver itself, when compared to the previous one on the same Windows platform (apples-to-apples so to speak), is not bad at all. Except for a slight loss on Wildlands lower Frame Times, the rest of the metrics are either stable or a bit better than with 446.14. No issues here. But still doesn't catch up with 442.59.

The big feature of this new driver is, of course, the support for WDDM 2.7 and the new Hardware Accelerated GPU Scheduling (HAGS for short). This feature allows your graphics card to manage its own video memory (VRAM) instead of the operating system. This should improve latency and response times, but also frees up some CPU computing power, in exchange of a bit higher GPU usage. As such, results of this new feature are very CPU/GPU dependant, along with the tested game itself. On CPU limited configurations, and/or CPU hungry games like Wildlands or FC5 (usually DX11 games) the new feature may squeeze some extra performance from your computer. On Dx12/Vulkan games (which are usually much less CPU limited), the new feature seems not that useful.

Arkham Knigth is the black sheep here. Previous reports of HAGS disliking a lot PhysX games seem true, and nVidia driver team has not been able to fix that incompatibility. This game lose a huge chunk of performance with 451.48, and what is worse, it is choppy as hell with heavy stutters.

 

My recommendation:

If you haven't upgraded your Windows 10 yet to v2004, there are no performance reasons to upgrade. Unless you need some specific bug fixed, 442.59 is still performing a bit better.

If you already have the new Windows 10 v2004 May Update installed, then you should probably upgrade to the new driver (and remember to manually enable HAGS, as it's disabled by default). On DX11 games or if your PC have some CPU bottleneck issues this will probably increase the performance of your games, both in raw framerate and with less stuttering. On the other hand, DX12/Vulkan games won't probably see much improvement though (if any).

Just be aware that HAGS is a new feature, and as such is expected to still have some bugs. If you use this feature, remember to disable as much Gameworks/PhysX options as possible on any game that use them, like Arkham Knight.

Link to comment
Share on other sites

Here's the HAGS setting in Win 10 2004, which by the looks of it applies to NVidia and AMD new drivers which support it.

0OzT1q7.png

Link to comment
Share on other sites

  • 1 month later...

452.06 whql released a few days ago.

Apparently its noticeably better for dx12 games https://www.reddit.com/r/nvidia/comments/ibfawg/game_ready_driver_45206_faqdiscussion/

Release notes https://us.download.nvidia.com/Windows/452.06/452.06-win10-win8-win7-release-notes.pdf

Link to comment
Share on other sites

  • 1 month later...

456.71 is out, apparently it also fixes 4 security vulnerabilities according to reddit ..

https://www.reddit.com/r/nvidia/comments/j6qgz8/game_ready_driver_45671_faqdiscussion/

"According to NVIDIA September Security Bulletin, this driver also contains fixes to 4 security vulnerabilities.

CVE‑2020‑5980

CVE‑2020‑5979

CVE‑2020‑5981

CVE‑2020‑5982"

 

Vulkan API included is now at 1.22 since a few versions prior to this one.

Link to comment
Share on other sites

  • 3 months later...

461.40 released yesterday, includes ..

 

 Version 461.09 added security updates for driver components See the NVIDIA Security Bulletin 5142 for details.

 Supports finalized Vulkan Ray Tracing extensions

 Supports CUDA 11.2

 NVIDIA Control Panel

• Added Background Application Max Frame Rate control (Manage 3D Settings page)

• Added Color Accuracy Mode feature (Display > Adjust Desktop Color Settings page)

 

Patch notes - https://uk.download.nvidia.com/Windows/ ... -notes.pdf

 [X4: Foundations][Vulkan]: The game may crash on GeForce RTX 30 series GPUs. [3220107]
 [X4: Foundations][Vulkan]: HUD in the game is broken. [3169099]
 [Resident Evil 2 Remake/Devil May Cry V] Games which used the RE2 engine may crash in
DirectX 11 mode [200686418]
 [DaVinci Resolve]: Error 707, application crash, or application instability may occur. [3225521]
 [Adobe Premiere Pro]: The application may freeze when using Mercury Playback Engine GPU
Acceleration (CUDA). [3230997/200686504]
 [Zoom][NVENC]: Webcam video image colors on the receiving end of Zoom may appear
incorrect. [3205912]
 [Detroit: Become Human]: The game randomly crashes. [3203114]
 [Steam VR game]: Stuttering and lagging occur upon launching a game (without running
running any GPU hardware monitoring tool in the background) [3152190]
 [Assassin's Creed Valhalla]: The game may randomly crash after extended gameplay
[200679654]
 NVIDIA Broadcast Camera filter may hang. [200691869]
 [Zoom]: Chrome browser flickers with Zoom app. [200695072]
 [G-SYNC][Surround][RTX 30 series] PC may restart when enabling NVIDIA Surround with GSYNC enabled on RTX 30 series GPUs. [3202303]

Link to comment
Share on other sites

  • 1 month later...

New NVidia driver released 25th Feb - 461.72

Fixed Issues in this Release

 [G-SYNC][Edge of Eternity/Hitman 2]: The games experience stutter and low FPS when using
hardware-accelerated GPU scheduling in windowed mode. [200685971]

 [G-Sync][Vulkan Apps]: Performance drop occurs when using G-SYNC and switching from
full-screen mode to windowed mode using the in-game settings. [200681477]

 [The Isle]: Freestyle is not supported for the game. [3229829]

 [VIndictus][GeForce Experience]: The game cannot be recorded. [2203875]

 [X4: Foundations][Vulkan]: The application crashes when launched on Windows 10 (Version
1803). [3220107]

 Wallpaper Engine app may crash on startup or upon resume from sleep. [3208963]

 [Blu-ray][HDMI]: Flickering occurs in Blu-ray playback when played over HDMI. [3221611]

 Several desktop applications flicker when Vertical Sync is set to the default “Use the 3D
application setting”. [3252186]

 [Ampere]: Chrome/Edge may experience random TDR while browsing.[3195894]

 LG CX OLED TVs (2020) are not recognized as G-SYNC Compatible displays.[3244055]

 [Surround][RTX 30 series] PC may display “no signal” message when enabling NVIDIA
Surround. [3230565]

 [Notebook]: On some Notebooks, the 'Maximum Graphics Power'' information missing in the
NVIDIA Control Panel > System Information page. [200697069]

Link to comment
Share on other sites

  • 2 weeks later...
On 3/1/2021 at 7:26 AM, alt3rn1ty said:

 LG CX OLED TVs (2020) are not recognized as G-SYNC Compatible displays.[3244055]

 

Aha, that's why it started working! Was thinking there was something wrong with my cable, or that I'd done something else stupid, but it was a driver problem.... I'd bought it because it had G-sync explicilty specified on the box.

Link to comment
Share on other sites

Yeah TVs are gettimg more and more complicated and prone to failure because of the complexity. My mother had bought a brand new Sony Bravia for the digital age, and receiving freeview channels, then one week not so long ago there was a change to the UKs normal first 5 tradional terrestrial channels (BBC1, BBC2, ITV, Channel 4 and Channel 5), the only channels my mother is interested in because she can press those corresponding buttons and not have to go into the menus etcetera (she gets confused easy, and the TV is her only entertainment so its important to have those working well). As far as I can make out it was something to do with an ID change, and the TV needed to be retuned every day just to get back the normal 5 channels. Many aerial trials later and a factory reset on the TV we have things reasonably stable again, but old folks would not be able to sort out such issues.

Thankfully she does not have internet and doesn't want it, but I am dreading the day stuff doesn't work on a tv because some function or other depends on an internet connection and unanticipated shit starts going wrong.

Anyway .. Back to NVidia drivers

New release 461.92 https://uk.download.nvidia.com/Windows/461.92/461.92-win10-win8-win7-release-notes.pdf

Fixed Issues in this Release

 Some desktop applications may flicker or stutter when resizing the window on some PC configurations [3252200].

 [GeForce GTX 1660 SUPER]: Random flickering may appear across the top of the monitor on some PC configurations. [3184254]

 [Vulkan][Red Dead Redemption 2]: The game may display pixelated black dots or artifacts on characters’ skin. [3257041/3266614]

 [Rocket League]: Matches may take longer to load. [3244324]

 [Fortnite]: Shader cache optimizations have been made to reduce intermittent stutter on some PC configurations. [3244272]

 [Detroit: Become Human]: Game may crash when launched with Image Sharpening enabled. [3242624/200667092]

 [Dungeon & Fighter]: The game may blink when choosing characters. [200574764]

 [Zoom]: GeForce Experience In-game Overlay launches when a Zoom meeting starts. [3269577]

 Enabling NVIDIA Surround with 4K HDMI 2.1 TVs may fail. [3184849]

 Blue-screen crash may occur when connecting/disconnecting to/from the Samsung 8k TV. [3188971]

Link to comment
Share on other sites

  • 2 months later...

New version 466.63

Release notes - https://uk.download.nvidia.com/Windows/466.63/466.63-win10-win8-win7-release-notes.pdf

Now has support for DLSS ..

"Game Ready for No Man’s Sky DLSS Patch

This new Game Ready Driver provides support for the latest new titles and updates, including the latest patch for No Man's Sky which introduces NVIDIA DLSS technology. Additionally, this release also provides optimal support for Chivalry 2, Sniper Ghost Warrior Contracts 2, and the new NVIDIA Reflex integrations in War Thunder and Escape from Tarkov."

.. For those lucky enough to already have an RTX GPU

Grump!, new laptop again sometime in the next couple of years :)

 

Link to comment
Share on other sites

  • 3 weeks later...

New version 471.11

Release notes https://uk.download.nvidia.com/Windows/471.11/471.11-win10-win8-win7-release-notes.pdf

New Features and Other Changes

Added support for Windows 10 May 2021 Update (version 21H1).

Added support for CUDA 11.4.

See also“Changes and Fixed Issues in Version 471.11” on page 7

-----------------

Page 7 ..

Fixed Issues in this Release

[World of Warcraft: Shadowlands]: Random flicker may occur in certain locations in the game [3206341]

[SLI][GeForce GTX 980M]: The system locks with a black screen upon booting into Windows. no repro with 457.51. [3266090]

[Surround][GeForce RTX 3090]: With Surround active, setting Bezel Correction disables Surround. [3286449]

[Crossfire][GeForce Experience][FreeStyle]: Freestyle might not work on Crossfire after the game is updated. [200736765]

[HDR]: Some specific HDMI displays might show some flickering in HDR mode. [200729987]

[Steam VR game]: Stuttering and lagging occur upon launching a game while any GPU hardware monitoring tool is running in the background. [3152190]

[NVIDIA Ampere GPU]: Colors may appear incorrect in games if sharpen Freestyle filter is used with HDR enabled. [200658208]

Display may flicker or lose signal when launching a game on an adaptive-sync VRR monitor in multi-monitor configuration when sharing the same display mode [3314055]

DisplayPort monitor may not wake from sleep when co

Link to comment
Share on other sites

  • 2 months later...
  • 3 weeks later...

496.13 whql released

https://uk.download.nvidia.com/Windows/496.13/496.13-win11-win10-release-notes.pdf

What’s New in Release 495

 NVIDIA Control Panel > Manage 3D Settings

• Added Shader Cache Size control to set the maximum amount of disk space to use for storing shader compiles.

• Vertical Sync options for Optimus notebook GPUs are now the same as for desktop GPUs.

Fixed Issues in this Release

 [GeForce RTX 3080]: The system does not boot with two Samsung Odyssey G70A 28" monitors are connected to the GPU. [3359697]

 [GeForce GTX 960]: The primary monitor lost after resume from sleep or shutdown. [3340905]

 [Windows 11]: The screen flashes once after switching to the discrete GPU-only mode in the NVIDIA Control Panel. [3330077]

 [Multiple Apps][Ansel/Freestyle]: Depth of field filter shows blurry characters. [200749545]

 [Notebook]: Vulkan test applications run on the integrated graphics processor instead of the discrete GPU. [200770322]

Link to comment
Share on other sites

  • 3 months later...

There has been quite a few updates to NVidia drivers since last I posted here, but yesterday was a notable release of 511.65

Includes an update to Vulkan 1.3

New Features

 Security updates - see Security Bulletin: NVIDIA GPU Display Driver - February 2022, which is available on the release date of this software and is listed on the NVIDIA Product Security page.

 OpenCL Vulkan Interop New external memory and semaphore sharing extensions provide a generic framework that enables OpenCL to import external memory and semaphore handles to synchronize with the external runtime, coordinating the use of shared memory. Refer to “NVIDIA OpenCL Vulkan Interop” on page 4 for details.

 NVIDIA OpenCL Compiler Upgrade The embedded OpenCL Just-In-Time compiler will offer an opt-in version utilizing CLANG 7.0 and NVVM 7.0 components, providing support for 16-bit floating point and 128-bit integer data types. Refer to “NVIDIA OpenCL Compiler Upgrade” on page 5 for details.

 Added Dead by Daylight- EGS Version application profile.

 Refer also to “Changes and Fixed Issues in Version 511.65” on page 10 “What’s New in Release 510” on page 4.

What’s New in Release 510

 Added support for the NVIDIA GeForce RTX 3050 and RTX 3080 (12GB) GPU.

 Added support for Windows11 Dynamic Refresh Rate.

 Added support for CUDA 11.6. NVIDIA OpenCL Vulkan Interop Starting with R510 driver version 511.65, the NVIDIA OpenCL driver has added support for the following new provisional extension specifications released by Khronos. The specifications are for OpenCL external semaphore and external memory. Release 510 Driver for Windows, Version 511.65 RN-08399-511-65_v02 | 5 Chapter 2. : RELEASE 510 DRIVER CHANGES

https://www.khronos.org/registry/OpenCL/specs/3.0-unified/html/ OpenCL_Ext.html#cl_khr_semaphore

https://www.khronos.org/registry/OpenCL/specs/3.0-unified/html/ OpenCL_Ext.html#cl_khr_external_semaphore

https://www.khronos.org/registry/OpenCL/specs/3.0-unified/html/ OpenCL_Ext.html#cl_khr_external_memory

NVIDIA is seeking developer feedback on this new extension support. OpenCL External semaphore and memory extensions The set of new External Memory and Semaphore Sharing extensions provides a generic framework that enables OpenCL to import external memory and semaphore handles exported by external APIs—using a methodology that will be familiar to Vulkan developers—and then use those semaphores to synchronize with the external runtime, coordinating the use of shared memory. The following key features are supported as part of these extensions:

 Importing memory into buffers using FD, Win32 KMT and NT handles

 Importing memory into images using FD, Win32 KMT and NT handles

 Importing binary semaphores using FD, Win32 KMT and NT handles

 Synchronizing using Wait and Signal on imported semaphores

 Using buffers and images imported in OpenCL kernels and other APIs such as other regular cl_mem. Limitations of the Current Implementation

 Support for importing external memory and semaphores using FD handles on Linux and Win32 NT and KMT handles on Windows. No other handle types are currently available.

 Support for binary semaphores only.

 No support for exporting semaphore or memory from OpenCL.

 clEnqueueAcquireExternalMemObjectsKHR and clEnqueueReleaseExternalMemObjectsKHR APIs are currently not required as execution hand-off can be managed through semaphore wait and signal. But, these may be required in the future for correct functionality. NVIDIA OpenCL Compiler Upgrade The NVIDIA OpenCL driver uses an embedded OpenCL Just-In-Time (JIT) compiler based on the legacy 3.4 versions of the NVVM optimizer component and CLANG compiler front-end. NVIDIA plans to upgrade its OpenCL JIT compiler to use version 7.0 of the CLANG front-end and NVVM optimizer component. NVIDIA is releasing this new OpenCL compiler as an opt-in feature in this driver release, with the default OpenCL compiler remaining the same. In a subsequent driver release, the default compiler will be switched to use the new components, replacing the old compiler. This approach provides an opportunity to solicit feedback from OpenCL customers and work to ensure this Release 510 Driver for Windows, Version 511.65 RN-08399-511-65_v02 | 6 Chapter 2. : RELEASE 510 DRIVER CHANGES feature meets functional and performance expectations for key use-cases prior to the final release. Enabling the OpenCL NVVM 7.0 Compiler As part of this driver install, a new compiler library should be visible in the system folder as “libnvidia-compiler-next” along with the old “libnvidia-compiler”. The driver by default will pick the old compiler unless the following environment variable is set: “NVCL_USE_NVVM70_COMPILER=1” NVVM 7.0 New Compiler Features The new NVVM 7.0 based compiler takes advantage of years of development in the Clang+LLVM framework. In addition to several minor bug fixes and diagnostic improvements, this compiler introduces the following noteworthy features:  16-bit floating point (half) type 16-bit floating point types or “half” type is available as a native data type in the new compiler. This type is enabled by the “cl_khr_fp16” feature guard pragma Example: #pragma OPENCL EXTENSION cl_khr_fp16 : enable half scalar_arith(half n, half k) { half w = n + k; 8 half x = n - k; -1 half y = w * x; -8 half z = y / x; 8 return -z; } __kernel void foo(__global int* x) { half a = 3.5H, b = 4.5H; if (scalar_arith(a, b) == -8.0) *x = 1; return; }

 128-bit integer type 128-bit integer types or “(un)signed long long” is available as a native data type in the new compiler. This type is enabled by default and does not require any macros to be defined Example: typedef unsigned long long ULL; typedef long long LL; LL scalar_arith(ULL n, ULL k) { LL w = n + k; LL x = n - k; LL y = w * x; LL z = y / x; return -z; } __kernel void foo(__global int* x) { ULL a = 0x123456789ABCDEF0ULL; ULL b = 0xFEDCBA9876543210ULL; if (scalar_arith(a, b) < 0) *x = 1; Release 510 Driver for Windows, Version 511.65 RN-08399-511-65_v02 | 7 Chapter 2. : RELEASE 510 DRIVER CHANGES return; }

 Upgraded math libraries The built-in standard math functions (e.g. sin(), cos()) have been upgraded to be on par with CUDA C++. This ensures that your application benefits from high-performance math routines optimized for the latest GPU architectures Known Issues with NVVM 7.0-based Compiler The new Clang/NVVM 7.0 based compiler has stricter error checking compared to the previous compiler. The following use-cases which were allowed with the older compiler may now throw an error.  Updating const variables after they have been assigned

 Using address spaces other than global for kernel pointer parameters

 Using variadic arguments in functions and blocks Discontinued Support

 NvIFR OpenGL support. Release 470 was the last driver branch to support this functionality. NvIFR header files, samples and documentation have been removed from the NVIDIA Capture SDK 7.1.9 release. Future drivers will remove NvIFR.dll and any other reference to NvIFR. For details, see the NVIDIA Video Codec SDK page. Release 510 Driver for Windows, Version 511.65 RN-08399-511-65_v02 | 8 Chapter 2. : RELEASE 510 DRIVER CHANGES Limitations in This Release The following features are not currently supported or have limited support in this driver release:

OpenCL 3.0 Known Issues

 Device-Side-Enqueue related queries may return 0 values, although corresponding built-ins can be safely used by kernel. This is in accordance with conformance requirements described at https://www.khronos.org/ registry/OpenCL/specs/3.0-unified/html/OpenCL_API.html#opencl-3.0-backwardscompatibility

 Shared virtual memory - the current implementation of shared virtual memory is limited to 64-bit platforms only. Using HDR with Games There may be issues resulting from the interaction between in-game HDR settings and the Windows HDR settings. See the NVIDIA Knowledge Base Article 5072 (https:// nvidia.custhelp.com/app/answers/detail/a_id/5072) for details. Implicit SLI Disabled on NVIDIA Ampere GPUs Implicit SLI, where the driver makes assumptions with application profiles to achieve GPU scaling, is disabled on NVIDIA Ampere GPUs. Explicit SLI is still supported, where the application knows the SLI state and uses extensions (such as DirectX 12 linked nodes, Vulkan device groups, or OpenGL multicast extensions) to issue commands to each device in the SLI group. See the NVIDIA Knowledge Base Article 5082 (https://nvidia.custhelp.com/app/answers/detail/a_id/5082) for more information. 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-videocodec-sdk. Connecting Displays to NVIDIA Turing GPUs in SLI Mode To use SLI with NVIDIA Turing GPUs, all displays must be connected to the primary SLI GPU. Release 510 Driver for Windows, Version 511.65 RN-08399-511-65_v02 | 9 Chapter 2. : RELEASE 510 DRIVER CHANGES Turing GPU Driver Installation 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 Crescent Bay and Open Source Virtual Reality development kit headsets do 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. Release 510 Driver for Windows, Version 511.65 RN-08399-511-65_v02 | 10

 

Changes and Fixed Issues in Version 511.65 Changes and Fixed Issues in Version 511.65

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

 [Windows11][Far Cry 6]: Geometric corruption occurs in the benchmark and in gameplay. [3441540]

 Multiple apps report stutter (or light to poor hitching) due to allocation creation. [3426466]

 [Notebook]: With Advanced Optimus configured in dGPU mode, notebook will display a black screen. [3502766]

 Some 3440x1440 monitors may display a black screen when selecting a DLDSR resolution. [3502478]

 [DirectX 12]: GeForce Experience Freestyle filters may cause game to flicker. [3496529]

 [Forza Horizon]: The game freezes when applying livery or vinyl to certain cars when ray tracing is enabled. [3506220/3506340]

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...