NVIDIA GeForce Game Ready Driver 595.97 Discussion

I’m a fool – The drivers were fine; It was the VR Headset connecting/disconnecting.

Driver works fine for me, no discernible difference to 591.86 which I was previously running.

5080 MSFS2024 SU5 Beta 1.7.16.0

I did a number of msfs2020/2024 tests today in VR with my QPro/9800x3d/rtx5090/Link Cable and found I got the best clarity and less ghosting (during panning) using dlss v310.5.2 instead of v310.5.3, dlss/quality, and with preset K. No difference in performance btw. Not what I expected, lol!

I also tested this all out by rolling back to 591.74 and 591.86 (using DDU in safe mode beforehand) and still found that the latest 595.97 gave a bit better smoother results.

Everyone’s systems and flying styles (I mainly fly heli’s dusk/dawn in cities like NYC, Osaka, Tokyo, and LA) are different so yrmv. Cheers.

***Update (5 days later);

I tried the latest dlss v310.6.0 by first just copy/pasting this into my msfs2020/2024 steam program directory. This worked ok but only gave me preset C for some reason. I then needed to use nvidia profile inspector dlss global overrides and recommended presets. This gave me preset M with dlss/performance and preset K with dlss/quality/balanced. I also tried going to NPI msfs2020/2024 profiles to force presets. After testing a number of dlss/preset combinations I’ve now settled on dlss/performance with preset M (= recommended one) for msfs2024 and dlss/quality preset K for msfs2020 This all seems very stable so I’ll probably stick with this for now.

I can’t honestly say there are any significant differences/improvements compared to v310.5.2 with dlss/quality and preset K btw, lol!

I tried this with my Q3 using Air Link (wifi6) and this also worked very well. I also tried using Virtual Desktop and this resulted in a lot of black square artifacts around my cockpit. These seem to reduce a bit after a few minutes flying. The VD developer says that this is a fault with the latest Meta non-beta v85 (201) update so maybe this will eventually get fixed. I don’t see any of these with my QPro/Link but I do see a few of these with my Q3/Air Link (but much less than with VD). So, maybe a wifi thing, who knows?

Seems good here on a 4090

I have significant issues with 595.97 in MS 2024. Every 30-60 minutes I encounter lag-spikes (freezing screen) for up to 60 seconds without a game crash. It recovers by itself.

I rolled back to 591.86 and the game freezes disappered completely.

RTX 3090 - W11 - MS24 Stable (no Beta)

1 Like

This driver is causing flickering in low-light conditions, such as during sunset or sunrise.

3 Likes

Personally feels better, less stutters for me

5070ti, 7800x3d, 32gb ddr5 6000, 1tb ssd

1 Like

I am not sure if this was caused by the driver update (hadn’t update in some time) but they day after updating I had pretty noticable stuttering. After rolling back and debugging four hours I found that frame gen seemed to be the issue. However, when I changed the setting to AMD and then back to Nvidia DLSS, it is now smooth again. No idea what is going on, but perhaps this could be useful for someone.

3 Likes

Can you explain a bit more what you mean by changing to AMD settings? What driver are you using? Can you go into more detail?

Im using right now Driver 591.84 no flickering on my screen, as soon as i go to 595 or 596.01 fliclering is present.

1 Like

I am still good with this driver on an ASUS 5080.

Are you using DLSS? Sounds more like latency issue. Turn it on / ultra, if disabled

I’m using TAA; this problem exists in TAA. In DLSS, this issue is still present, but the flickering is less noticeable.

1 Like

Using Upscale Lab at 90 Hz broke the detection of my Pimax Crystal Light; I had to revert to version 595.79 to resolve the issue.

Yep! I have the same issue and at certain angles like cabin passenger views flickering along the edges.

1 Like

Thank you for confirming this issue; some people may not notice or care at all.

1 Like

Sadly I think you may be correct. Been a long time since we’ve had the option to use the freestyle filters with MSFS. I’ve also asked the question on the Nvida forums but have never had any response.

3 Likes

Bit of a weird one, and I’ve seen a few others mention the same thing.

Since yesterday, the debug FPS overlay only shows the base (pre–frame generation) FPS, even with DLSS Frame Gen enabled. The NVIDIA overlay does the same — it reports the lower number — but visually you can tell frame gen is definitely active because the motion is much smoother.

What’s even stranger is how the frame cap behaves. It technically works, but it’s really inconsistent. For example, trying to lock 40 → 120 (3×) or 60 → 120 (2×) doesn’t line up cleanly anymore. Instead, it overshoots quite a bit — I’m often seeing 140+ FPS — and the “base” framerate itself won’t sit steady at 40 or 60. It constantly fluctuates and seems to drift above and below the target.

At first I thought this was just me not fully understanding how frame gen behaves on the new system (Ryzen 7 9800X3D, 64 GB RAM, RTX 5080), but it’s interesting that others are reporting exactly the same behavior. That makes it feel less like a local setup issue and more like something tied to the sim or driver.

What’s also curious is that with the same driver, this all worked much more predictably on my previous 5080 mobile setup. The only major difference is that this is SU4, while the laptop was running SU5 beta.

I might jump back into the beta soon to compare, but for now I want to spend some time flying the Fenix. Still, it’ll be interesting to see how SU4 vs SU5 handles frame gen and frame pacing.

1 Like

I am frequentlly looking at this topic before changing to a new driver and find it very useful. I think that the same kind of topics would be useful for DLSS versions. 5 days ago i moved from DLSS 310.2.1 tyo DLSS 310.5.3 on my rtx 5080. I got a lot of artefacts in external view of MSFS 2020 and try to solve them touching a lot of parameters in ODT, OpenXRtoolkit and MSFS itself with no results. Then i remember what i made 5 days ago. Going back to 310.2.1 solves everything. So changing of drvers may be dangerous, but DLSS versions changes are also critical.

2 Likes

Feel free to join the discussion about Nvidia DLSS in the thread linked below.

https://forums.flightsimulator.com/t/dlss-main-thread-latest-version-310-6-0-feedback-and-tips-discussion/761814

1 Like

Thank you Tenpatrol. I will look at it.

1 Like