NVIDIA GeForce Game Ready Driver 537.58 Discussion

Talgmar,

Here is a little bonus for you. These .jpg files below show which folders are removed when creating your own cleaned driver. A simple edit is required of the setup.cfg file. I often create my own cleaned driver using the guide below. Credit to CptLucky8 who originally posted these images on this forum.

As you can see, NvContainer is deleted during the editing process along with NVTelemetry

This is great news, and I will try the clean driver a little later.

But just to be sure since you linked a image to the Nvidia folder and not Nvidia Corporation folder.
There is no Nvidia Corporation folder? in your C:\ProgramData?

1 Like

Talgmar,

Yes there is an Nvidia Corporation folder which has a folder called GameSessionTelemetery, this contains a ‘plugin.log’ but no Game Session log. I don’t know if that is good news for you or not.

You have worked me hard today! :grin:

Nvidia Corporation

Charles.

Haha, Im sorry for that, Im really trying not to. I just dont wanna go through the whole DDU process and install clean driver process and then realize it still has that stuff.

But yeah, as you can see you still have the GameSessionTelemetry folder, that contains the telemetryplugin.log thats being read and written to continiously. Which is what Im trying to avoid having.

Again, sorry for the hassle :smiley:

1 Like

That’s OK, I have learnt much in the process! :grinning:
All good fun


Yours aye.

Charles.

1 Like

again a new NVIDIA driver, has anyone noticed and tested it yet, I don’t dare to
 :joy:
But it is not yet offered to me as an update in the NVCP, I discovered it by chance directly at Nvidia, because I just wanted to clean up my driver remnants with DDU


NVIDIA GeForce Game Ready Driver 545.84 Discussion - General Discussion & Community Support / Tech Talk - Microsoft Flight Simulator Forums

537.58 is the latest Studio Driver, the Game Ready driver is 545.84. Nothing wrong in using the Studio driver for MSFS, just not best optimised for other games.

As TenPatrol says, info on another thread as above. Nobody yet commented.

Gotta say the latest Nvidia driver is working perfectly for me as well on my 4090. Even getting a few more FPS (still use TAA and Frame Gen)

1 Like

Hi there, I unfortunately have repeated CTDs with FG on. If not too much to ask, can you share your main settings in game and NCP ? My system is not as high end as yours (I have 4080 and i 13700) but perhaps I am also setting something the wrong way. I should add that I am sometimes moving the ATC dialog box to a second monitor that is different resolution from my main one and I think this may be causing some issues but not sure. Many thanks.

Hi sure, I don’t mind! Keep in mind a couple of things (sorry if you already know this, just trying to be helpful):

  1. Must be on DX12beta to use Frame Generation
  2. When I got my 4090, I initially had settings in 3840x2160, DLSS3 (MSFS calls it Nvidia Super Res DLSS), Frame Generation = ON, VSync = OFF, etc and that works just as great
 but technically DLSS “lowers” the native resolution, so others told me to try TAA vs DLSS.
  3. In re: to CTDs, this most likely is due to an overclock you might have on your CPU or GPU, or your level of terrain detail settings are just too high for your current setup.
  4. I never use native MSFS pop-up windows (i.e. ATC, Weather settings, etc.) - in fact, I downloaded a mod that removes that entire toolbar from the top because I hate it. So to your point, I’m not sure if the pop-up of your ATC menu and then moving it to a different monitor is what’s causing your CTDs?

Anyways, here are my current settings:
(I am using HDR, so my screenshots look odd here, sorry)



1 Like

Thank you so much for the comprehensive response.

I am indeed using FG with DX12 and HAGS on as instructed with TAA and my TLOD is between 200 and 250 OLOD 150 or 200 - I dont think they are the cause of CTDs but will try lowering somewhat (although too low causes increases in the infamous popping up of coastlines, roocks etc.).

May I ask additionally for whether you are limiting frames in NCP ? I had rea d in another post that to avoid tearing, when using FG one needs to limit frames in NCP a couple of notches below the monitor refresh rate. I have 2k that can do 60-100-120-144 but I set it at 60 Mhz and limit frames in NCP to 56.

1 Like

I do NOT limit any frames in ncp. I keep everything default so to speak and I don’t use vsync. I’ve seen vsync have issues in MSFS (natively or even via NCP).

The only setting I ensure is always on in ncp is Low Latency set to ULTRA

1 Like

Why do you use low latency set to Ultra in NCP? Do you really see a difference here? Even with FG on?

I was always limiting them - will try without as you suggest. Many thanks again.

Any improvements?

I honestly don’t know, to be fair. I doubt it does much, but I do use the ultra ow latency settings for other games I play.

1 Like

Hi, I think yes, your suggestions helped, thanks again.

I still need to set Vsync to ON in NCP otherwise I get screen tearing and if I pop the ATC screen out to the second monitor I still get CTDs.

So to sum up I think that if I want FG - DX12 - HAGS On I should not be popping ATC to a second monitor otherwise I should be going for vanilla DX11 with HAGS off and no FG but then I can be popping the ATC window to the second monitor.