NVIDIA GeForce Game Ready Driver 556.12 Discussion

Please use this thread to discuss the NVIDIA GeForce Game Ready Driver version 556.12.

Game Ready for The First Descendant

This new Game Ready Driver provides the best gaming experience for the latest new games supporting DLSS 3.5 technology including The First Descendant. Further support for new titles leveraging NVIDIA DLSS technology includes the latest update for PAYDAY 3 which supports DLSS 3.

Fixed Gaming Bugs

  • [The Last of Us Part 1] Out of memory error with 555.xx drivers [4663766]
  • [Halo Infinite] Crashing during initial loading screen with 555.99 driver [4685335]
  • [Valorant] In-game statistics incorrectly shows high latency with 555.xx drivers [4668309]

Fixed General Bugs

  • Notebook mux switch is blocked when Overwolf application is running [3804893]

Known Issues

  • [NVENC] Quality and bitrate settings are ignored at 10-bit encoding [4697900]
  • [GeForce Experience] Performance Monitoring overlay may stop refreshing GPU information [4679970]
4 Likes

Nothing bad on my end. The last couple of drivers have been pretty good.

Works great with my i913900k/rtx4090. PCVR with my QPro using Link cable. DX11 and Hags disabled. Updated from 552.44 and better than the 555.xx drivers imho.

1 Like

Just installed, will test over the next few days.

Some good info here: https://www.reddit.com/r/nvidia/comments/1dpqpo4/game_ready_driver_55612_faqdiscussion/

Great here.

All good - 13900K,RTX 4090, 32GB DDR5 @7200

3 Likes

This driver seems substantially better in terms of smoothness and mitigation of micro stutters. Obviously results may vary with individual system specs, and various configuration settings, but give it a try, definitely.

2 Likes

So far so good. 4080Super.

2 Likes

all good with a 4080

2 Likes

Installed a couple of days ago and no issues with my RTX3080. It seems to be a very smooth driver so far. Islandsimpilot confirms this in his recent Youtube video.

I decided to upgrade from v.555.85 which was working fine for me to this new one following your previous positive comments :slightly_smiling_face:

No problems whatsoever so far :+1: I do need more testing time though. I will edit my post later if I find anything fishy… :fish:

Everything is running smoothly and I seem to have gained a few fps too :nerd_face:

Clean install of the Nvidia drivers, cleared shader cache and rolling cache as usual and using NVIDIA DLSS 3 Frame Generation DLL 3.7.10 (the latest).

FS2020 settings: 4K resolution, DX12, DLSS > DLAA, FG is activated.

My setup:
5800X3D - RTX4080 - 32G DDR4 3200 - TV 48’’ 4K LG OLED 120 Hz GSYNC

3 Likes

Appear to be getting +4 fps with this driver. The 0.1% is better too (not sure why capframex uses 0.2%) 22.2 vs 28.9. RJTT, 16L in the PMDG 777.

4070ti low power, 7945HX@4.8GHz, High-Ultra settings, Frame Gen off, DLAA

4 Likes

Can confirm the values ogu1271 measuered.
Did a clean DDU uninstall, installed the clean driver version, and compared to the driver before, which was in my case 552.52 …

Overall performance increase ~ + 5 FPS and 0.5 ms frametime.

==> good to go with!

System: B550 / 5800x3D / 4080 @4k resolution / 64 GB DDR3600 CL16-16-16 RAM

I swore I wouldn’t upgrade from 537.67 until I was forced.
But the positive comments here have me headed to the computer to uninstall it and install 556.12.

Wish me luck!

1 Like

That’s a lot of change, don’t forget to DDU, clear DX caches etc.

You got that right. :wink:

  1. Disable nVidia Shader Cache.
  2. Safe Mode, DDU (keep Global and Program Settings.)
  3. Restart.
  4. Download 556.12
  5. Create installer using NVCleanstall (use downloaded file) and install driver.
  6. Use Corsten’s Cache Removal Tool to clear all MSFS caches.
  7. Delete Rolling Cache file in RAMdrive.
  8. Restart
  9. Start MSFS.
  10. Delete/Restart 15GB Rolling Cache.

Whew!

I ran a 300 second CapFrameX test with 537.67 and again with 556.12 using the following setup:

  • Cabri G2 (cold & dark)
  • KSEZ 0920
  • Preset: Rain
  • I didn’t change any of my other sim options. (4K native, DLSS DLAA, DLL 3.7.10, Sync OFF, Traffic 20%, TLOD and OLOD @ 145)
  • I’m driving one 4K DP monitor for the sim, and one 2K HDMI monitor (used for other apps.)
  • Framerate limited to 60 FPS using RTSS.

Results: for 556.12 vs. 537.67

P95 (+8%)
Average (+9%)
P5 (+9%)
P1 (+9%)
1% Low (+7%)
P0.2 (+9%)
P0.1 +7%
0.1% Low (-13%)

Great result. I didn’t notice any flickering, which is a problem I’ve had with other drivers. If this one is stable it’s a keeper!

The 0.1% Low result is interesting.
FPS on the L-graph looks more consistent.
Overall frametimes seemed more stable as well. I can post a pic of the CapFrameX report of that graph if anyone is interested.

Ignore the incorrect driver version (537.67) in the top picture. It’s actually 536.67. I just wrote it wrong in the notes.

3 Likes

That’s a user-configurable option.

1 Like

CapFrameX is a pretty good tool. I’ve used it in the past to troubleshoot some low frame rates.

Personally, I don’t look at the “Average” numbers because average is average. The numbers don’t say anything about the QUALITY of the FPS. The other two numbers help describe the overall quality of the frame rates. The 1% numbers tell you that 1% of the captured frames had an FPS lower than that number. The 0.2% is a better indicator of quality. It means that 0.2% of the frames captured had an FPS less than that number. However, these numbers don’t tell you when the not-too-good frames were displayed.

Without getting too deep into statistics, what you are looking for and seeing are all the bars visually showing roughly the same improvement.

The biggest problem I had with CapFrameX was making sure I was running the same “capture” flight over and over including traffic, weather, and scenery.

1 Like

In VR - 4090 - 7800X3D

Terrible driver. Stuttery, grainy graphics and flickering on start up screen.

Rolled back to .85

1 Like

I think the L-curve graphs in my post above are an indicator of framerate consistency. I made sure to do the two tests using the same sim settings. As you point out, that’s critical to the testing.