What is wrong in your opinion with the new driver?
That clears it up. I followed your instructions to get DLSS4 working in MSFS2024. Haven’t tried MSFS2020 yet.
Do you know if there is any benefit for autoexposure? Thanks.
If I’m not mistaken, autoexposure is something like automatic brightening and dimming depending on the brightness, for example, when you’re in the cockpit and change your view. As far as I remember, the MSFS 2020 community was very critical of this feature.
If I’m mistaken, please feel free to correct me.
1 Like
I think it’s not the driver but the difference between the sims.
The 2024 sim is not yet fully compatible with the DLSS 4.0 overlay.
Also the dll files are not optimal working with both sims.
In MSFS2020 there is a lot off flikkering during startup of the sim and the frame generation use still a lot of VRAM. While Nvidia has actually said that VRAM usage would be substantially lower with the new driver.
I think that Asobo has something to do by optimizing the Sim.
What plane is that? I really like the cockpit…
I reset Nvidia Inspector and Nvidia App to default. Then deleted both.
Then did DDU clean uninstall of latest driver.
Reinstalled driver.
Simply used DLSS Swapper to put in the latest.
Still no Nvidia App or Inspector.
Still get the latest DLSS files and the latest preset.
And of course the ghosting is still there with DLSS.
Guys just leave this stuff alone, it’s not worth the hassle.
1 Like
Black square TBM 850- with mod (black)
3 Likes
How do you get this “presetK” to show up bottom left?
Since I installed the new NVidia 572.16 driver, FS2024 will no longer load, but will CTD when reaching 90% (The video comes to a standstill for a couple of seconds, then back to desktop it is).
I tried just about anything I can think of, switched DLSS’s via DLLS Swapper, emptied Community folder, tried to run FS2024 as administrator, rebooted multiple times, turned away from the screen while FS loads :)… nothings helps.
FS2020 continues to run fine on the new driver, but for FS2024 I need to turn back to driver 566.36. Anyone experiencing similar behaviour or having idea what could be the cause?
3 Likes
This is all SO dumb and frustrating.
Nvidia says…
" To begin 2025 with a bang, we’re announcing that 75 games and apps will support DLSS 4’s new DLSS Multi Frame Generation technology at launch of our GeForce RTX 50 Series GPUs."
They are saying DLSS will be supported on those games at launch of the 5000 series card, NOT that it will be supported ONLY on 5000s cards, but I have to wonder if in fact you need a 5000 series card to use DLSS 4 for all those games? Or maybe Asobo once again just messed this up and there’s a bug and it’s just not working well, reliably or without hacking?
And MSFS 2024 is on that list. Has Asobo said anything about this circus since this driver release?
I’ve tried it with just the latest Nvidia app and driver, and with the Preset Inspector.
I am using the reg edit to display the DLSS version.
I’m pretty confused at this point, but I swear using the DLSS version readout I had DLSS 310.2.0 displayed on the top and bottom, Preset K shown on the bottom at one point. Then it was showing 310.2.0 at the top and 3.7.10 at the bottom, and now it’s 3.7.10 top and bottom, preset E. I don’t think I changed anything after seeing 3.10.2, just closed and restarted MSFS 2024 several times and it seems to just have overridden and forced 3.7.10 to be used.
Clearly MSFS should NOT have been on that list.
Asobo needs to COMMUNICATE ABOUT THIS!
1 Like
I have played all day on the new driver without a single CTD, 3060ti 16gb I7, community folder only navigraph and AIG models for beyond atc traffic injector. Also i use TAA and not DLSS
This is the most annoying thing. Nothing from Asobo, not one single word… not even telling the community… You have to do this or that… Same Nvidia… But well… That’s why we are here…
1 Like
Very confused, but finally after a lot of back and forth, it seems I have DLSS4 with “less ghosting”.
I tried a lot of different things, both Profile “J”, updating to the 310.2.1 driver, tried to use the Profile Inspector and change profile to “latest”, but still a lot of ghosting.
In the end I gave up DLSS, and switched back to TAA.
But now I had gotten this weird stuttering.
Thus I reset all my Profile Inspector settings and did a reinstall of the latest Nvidia driver.
Then after a restart the stuttering was gone. Then, just for kicks I tried one last time with DLSS, and now, for some weird reason the ghosting was much less.
It is still there, but now it is possible to see most of the numbers on moving gauges.
And thus I could cranck up the settings to Ultra.
Very nice!
(I have a 5800x3D with a 3080ti)
Same here and after that, simply placing the new dll files will show K and 310.2.1
No profile inspector required. Just a clean driver install.
I don’t know if I want to use this dynamic dlss swap. I’m done.
I only wonder if there’re any performance differences between the dlss from the driver vs using the regular method of replacing game files.
1 Like
I was experiencing CTDs while loading MSFS 2020. I uninstalled Nvidia app and I no longer had any CTDs.
Try using DDU, and after restart Install new driver - during driver installation, don’t install Nvidia app - just select driver, PhysX and perform a clean installation.
1 Like
A simple, “We are aware a lot of people are frustrated, confused and disappointed trying to get DLSS 4 working and we are looking into the issues. We will give updated information as soon as we can.” would go A LONG LONG way to feel less hopeless and frustrated!
10 Likes
You only need a 5000 series card to use nVidia MFG. The other DLSS4 stuff works on the 4000 series and some of the stuff works on the 2 and 3 series IIRC.
As these are driver level changes and this “list” has been compiled by nVidia it can hardly be expected that Asobo shows you how to juggle the dll’s (or any of the other hoops you need to jump through).
What Asobo will need to do is add the multi-framegen at some point put as so few people have 5000 cards it is doubtful that it will be any sort of priority
1 Like
I don’t expect Asobo to show me how to juggle DLLs, I expect them to make sure I DON’T HAVE TO. And we don’t know how nVidia compiled that list, but I have a hard time assuming they did so without consulting Asobo before putting MSFS 2024 on it.
Yes. Point 1 is not mandatory, you can keep the updated DLL.