New Nvidia Drivers: 471.96 WHQL 31/8/21, (flickering fix reported)

My name is Manuel and I work for NVIDIA. It seems I can’t post links here (maybe since I am a new user) but for users who are experience crashes in Flight Simulator 2020 after upgrading to driver 471.11, can you go to the NVIDIA forums and search for the GeForce Game Ready Driver 471.11 feedback thread and in there you will find a link to the driver feedback form. Please fill it out so that I can ask our software team to look into this. Please make sure to include all displays that are connected to your graphics card as sometimes crashes may be specific when running multi-monitors.
Also check if disabling GeForce Experience in-game overlay makes a different with the crashes you are seeing. Thank you.

Regards,
Manuel
NVIDIA Forums Rep

6 Likes

Here is the link Manuel is referring to:

1 Like

Hi! If you don’t mind me asking, I run MSFS on a Razer Blade gaming laptop with a 2080S maxq. I’ve been getting different results if I install the “desktop” driver instead of the “notebook” driver. Performance is almost the same, but the desktop driver runs way quieter and appears to have lower overall GPU % utilization. Have you seen or tried anything like this?

No I have not, because I use a large SONY Bravia OLED screen connected to my laptop instead of using the laptop directly.

1 Like

There is zero difference between the desktop and notebook driver. We only rename them differently to track the number of desktop vs. notebook driver downloads.

2 Likes

Hi Manuel,

I must say having you here is certainly a good news!

I’ve been publishing a certain number of guides in these forums for configuring one’s NVidia hardware for FS2020 gaming, both in 4K and in VR, and the latter both with WMR (G2) and SteamVR (Index).

From the feedback gathered in my topics the 457.30 driver was a clear winner for a long time and it is only until recently, since 466.27 at least, that newest drivers are starting to be equaling the venerable 457.30 for many FS2020 VR users. However there are still a lot of assumptions and uncertainties which would greatly benefit from your insights.

The following questions mostly for VR are probably the most discussed about in this forum and are source of very differing reports sometimes in the context of FS2020 VR:

  • Is HAGS offering any benefit in VR or is it known to be causing problems?

  • Is it equally benefiting 20XX and 30XX?

  • Is there any driver version after which the 20XX card series aren’t benefitting much?
    (except the security bulletin, this question is more with regard to performance and/or driver bugs).

  • Is there a clear explanation of Threaded Optimization role?

  • Is there any particular NVidia setting most recommended for WMR/OXR which wouldn’t be recommended for SteamVR/OXR ?
    (here I’m thinking about settings like VR pre-rendered frames)

  • Conversely, is there any setting most recommended for SteamVR/OXR instead, or for both, or actually not recommended at all for any?

  • Is Latency Mode and Vertical sync having any real influence with an HMD working in Direct Mode (it seems it has but this depends on the driver version, sometimes it is better, sometimes worse).

And last but not least:

I can notice there are times when SteamVR motion smoothing is breaking, as if it is no longer syncing in time properly with the game rendering. This started to happen with FS2020 latest world update, which also coincides with 466.27 to 471.11 drivers period and SteamVR 1.17.x (last few versions) and 1.18.x (latest beta versions). When this is happening, the overall rendering reduces to single digit FPS and motion smoothing lags a lot with lots of artifacts. When disabling motion smoothing everything displays back to normal and I can even crank SteamVR fixed rate to 40fps/80Hz without any hiccup, but enabling motion smoothing back is a whole mess again. It seems there is a correlation between either the game not rendering in time, or oversubscribing the VRAM (this is also raising a question to me whether NVidia/Optical Flow, and SteamVR/OXR, can allocate and pin VRAM which can’t be deallocated by the game for example).

I haven’t found any tooling which would enable tracing what is happening, especially whether it is FS2020 use of the OXR API which is problematic here, the SteamVR/OXR driver which has a bug, or the NVidia Optical Flow SDK has a bug ( An Introduction to the NVIDIA Optical Flow SDK | NVIDIA Developer Blog ). This could also be a case where FS2020 is submitting the frames too late and maybe Optical Flow doesn’t have enough time to processing the frame until the next tick, therefore causing desynchronization of some sort, but again there are no tooling that I know of which could help tracing this behavior and finding the root cause in the context of running FS2020 in VR.

Is there something we can do to help Microsoft, Valve and Nvidia assessing what is going wrong in this situation?

Thank you in advance for your assistance with these!


PS: here are the links to my settings topics:
My 2070 SUPER VR settings and suggestions (Index - SteamVR)
My 2070 SUPER VR settings and suggestion (Reverb G2 - WMR)
My 2070 SUPER 4K settings and suggestions - episode 2

7 Likes

Hi Manuel, it’s terrific to have someone from Nvidia following and giving some great advice here. The topic of Nvidia drivers is very popular in this forum, there are driver threads popping up all the time. I hope you can post links soon and welcome to the forum. BRGDS. Charles.

2 Likes

Captain, you have quite a ‘handle’ on this subject and it’s very interesting. I hope you get some good feedback from your observations. Fantastic stuff that adds extra value to this forum. :grinning:Cheers! Charles

2 Likes

I would like to have confirm, if Nvidia has lowered the power limit with their newer drivers :wink:

With 460.89 i can use the bios power limit of 450W.
With the newer ones I can’t, even if bios is set to 450W, I see power limit bit is set at 390W when overclocking.

That causes CTDs

1 Like

Wowza! Youse guys aren’t kidding! Before 471.11 and the Nordic update, flying over upper Manhattan at 70 to 100 kts at 1K to 1.5K ft in an ICON A5 using ULTRA settings with a 2070S at 1440p used to be a blurry stuttery mess but now it’s very sharp and quite smooth except for occasional barely perceptible microstutters here and there while banking. And my usual undemanding joyride out over Mann Gulch, MT is awesomely sharp and detailed. Haven’t tried VR yet.

1 Like

I tried my simulator today. I started at Birmingham EGBB, (Maccosim add-on). I only have a 1080P monitor but choose high graphics settings, some ULTRA for trees etc. but Render Scaling, (all three of the sliders) at recommended settings. Using the C152 I had a completely stutter free experience with FPS 40-49. I have not enjoyed performance like this for many months especially without severe stuttering. When I changed the WX setting to rain from clear skies and then to rain and high winds, my simulator crashed to desktop. Charles

1 Like

Thanks for the welcome :slight_smile:

2 Likes

Anything with ‘performance’ in the title must be welcome! If your interested, I would jump in quick, today is the day you need to register! :grinning_face_with_smiling_eyes: I guess GPU drivers have a part to play in this too…

Download GeForce 471.22 hotfix drivers. The hotfix addresses a fixDoom Eternal that may crash as well as other fixes.

  • Doom Eternal may crash to desktop during gameplay [3331270]
  • League of Legends [Tencent] may fail to launch [200744747]
  • Mouse cursor color may shift when connected to certain DSC monitors in HDR mode [200741796]
  • [HDMI 2.1][8K] HDMI audio playback may become distorted after changing display modes [3268312]
  • Some displays screen resolution limited to 640x480 after driver update [3330750]

The slimmed skinny version without bloatware can be found here…471.11 + Hotfix 471.22 - Clean Version | guru3D Forums

your nvidia link is pointing to driver 417.22, not 471.22.

1 Like

Hi William, I assume you are referring to the ‘weight watchers’ driver? The new hot-fix is there, it’s just a little further down the page. It is a little confusing, I must admit. The two driver versions both appear in the page title.
Anyhow, here is the header from the download page…
Clean Hotfix 471.22 GTX - x64 Desktop/Notebook
To prevent any confusion, hotfix driver links are removed once a newer version of the WHQL driver is released’.

Thank you for your alert. BRGDS. Charles

No…the “https://www.nvidia.com/Download/driver…” link you wrote ABOVE “The slimmed skinny version…” takes you to driver version 417.22, not 471.22.
if that is intentional, then i apologize for my incorrect correction. :smiley:

1 Like

Oh, I see what you mean. I am a bit slow today. I do apologise, it’s an ‘admin’ error on my part. :blush: I have deleted that link to the 417.22 WHQL driver which is not a ‘slimmed’ driver. The link to the skinny driver is OK. Charles

1 Like

On my Aorus 3080 Extreme I had to roll back the driver all back to 460.89.

Also the BIOS from the card from F6 to F3.

Seems in the recent drivers there’s a power limit coded at 380w, which is a shame. My card was running so good and stable at 420 watts at 2100 mhz.

But… FS crashes now anyway, whenever the card is overclocked, so the power limit enhancement is not important anymore

1 Like

what a horror power consumption… I hope the graphics card manufactors will in future spend a bit more time into a good hardware design and avoid this waste of energy.

1 Like