Better swap 572.16 with 566.14 and fly!
The rest is in my opinion useless and a waste of time.
Wait until Asobo and Nvidia sort things out. 
3 Likes
Not sure if that was directed to me or just a general recommendation given the ambiguous and far from ideal state of these matters?
Each unto his own. Your mileage will vary, etc., etc.
I’ve never had a CTD with 572.16, trying to use DLSS 4 or not.
I did spend WAY more time than I am ok with yesterday and got nowhere useful. Except to seed a thought I had in bed waking up this morning, that the one time I had 310.2 working yesterday was around when I had typed the wrong settings in for the preset, 0x000FFFFF, 5 F’s at the end, not 6. So I decided to try without the F’s not 5 not 5 all zeros to start my experiments today and low and behold, it simply worked first thing I tried today.
Enjoyed flying and X Cub around the Grand Canyon a while and had not issues, it looked great and seems to give better FPS.
So, while yeah, entirely valid to just wait on Asobo to make the sim just work as it should with DLSS4 out of the box and communicate in a reasonable and responsible way about this mess they made. Also seems there are people running 572.16 happily too.
I think anyone trying Nvidia Profile Inspector and not getting 310.2.0 should try different preset values, including 0x00000000.
You don’t type anything into nvidia profile inspector. You just select it based on the pulldown for the setting, Using the recommended bottom setting (one with all the F’s) this worked fine for me.
1 Like
When I revert from 572.16 to 566.14, the override and preset items disappear from the Nvidia Profile Inspector.
Is it because I’m on a 3000 series? I have a 3080ti.
Do I need to do something to get the overrides and presets in 566.14?
Does the person who says they reverted to 566.14 mean they reverted their override and preset changes too?
Off course the presets are not valid for the 566.14 driver and disappear out of the Profile inspector. They simply are not in that driver.
I realized there was pull down selections only after I had changed the fields manually AND didn’t count my 0s and Fs correctly looking at a howto post. I’ve tried it every which way, manually typing, selecting the pull downs and the only way I get 310.2.0 and Preset K is if it’s set to 0x00000000. This last time that finally seems to be working I did use the pull down, but the first I got it working briefly the other day was actually when I manually entered the values and got them WRONG, so I assume it disregarded my entries and used defaults?
But I’ve definitely manually and with the pull down set it to 0x00FFFFFF and I get 3.7.10 and Preset E any time I do.
Go figure. I can’t explain any of it, certainly can’t explain why my settings give different results than other people’s settings. It’s just been a TON of trial and error for me.
1 Like
Help or commiserate with me:
Installed the new Nvidia driver via Nvidia app. Did the dlss alteration. Looked great was getting 120 fps. After 30 minutes down to 10 (first started in the clouds).
Removes the dlss stuff, uninstall Nvidia app, reinstalled ; “optimized” same thing. Crashed a cesna 172, went to b rating and rage quit and rage shut down my pc. Turn out it’s really hard to fly at 10 fps.
Haven’t tried vr yet. May never turn my computer back on
4090, ryzen 9 9900, 64 gigs of ram. 2 4k displays.
DLSS alteration?
Yep it’s bad. I’ve reverted back to 566.45 and all good. I’ll be waiting until the next driver or next msfs update to try out dlss 4 again.
Why doing all this if you have that RIG, 4090, ryzen 9 9900, 64 gigs of ram.
Don’t screw up your resolution and you can play comfortably.
4K, 8K all those pixels need to be processed. 2x4K = 33.177.600 px.
I have 3x 1920x1080 px = 6.220.800 px and with that i can play on high settings comfortably, but not with 5 times the amount.
Some users want to much and the hardware can’t handle that.
2 Likes
dude if you play in vr it doesn t looks that way . you have to render the resolution twice and its not that clear that you think .
1 Like
Dude?
That’s the problem, VR is asking so much from the hardware.
It is not realistic to try to screw up the resolution every time the makers come with there new headsets.
it doesn t matter . as a developer . when you release the game " ready " for the vr platform it should be ok with the latest avalabile technology . but seems its not .
They don’t say that.
It’s VR ready but with what resolution?
It’s the same if i want to play on two 4K monitors, that won’t work without lowering my settings or buying the most expensive hardware on the market.
It’s simply to much to handle for the most hardware.
A new version of the NVIDIA driver is now available for download.
Nvidia Hotfix Driver Version 572.24 - User Support Hub / Install, Performance & Graphics - Microsoft Flight Simulator Forums
2 Likes
Hi TenPetral and all the others,
thank you very much for your engagement. I followed your advice.
Newest driver (hotfix), the newest dll-files and the adjustments with the nvidia-inspector.
Steam-version
MSFS 2024 beta.
I7 147000
RTX 4070
underclocking due to thermalthrotteling
Runs absolutely smooth, like before, but one quality level higher in DLSS Super Resolution (Quality now) with 60 Fps also between the skysrapers in NewYork.
1 Like
Thank you @SpitfireIXc for sharing your experience with the new hotfix driver. It’s really appreciated.
If you could also post about it in topic related to the hotfix driver - it could serve as useful information for others.
Sorry, do you mean that Quality mode in FS24 = DLSS4 Super Resolution ?
I got better results with the new driver.
It’s interesting to see the difference between people who get better with the new driver and those who don’t.
I can’t see any trends in the PC specs you all write sometimes.
I’ve never seen anyone write whether they use 23H2 or 24H2, so
I’m curious to see if there’s a correlation.
I’m using 23H2. Is this complete nonsense?
Results using FS2020 3060Ti and 5800X3D and switching to Direct X 12
I followed this video and just completed my first short flight and it was very smooth, never noticed any stutters at all, Framerate set at 60 max. ( was set at 40fps)
No problem with NVidia App been using it since release.
The Ghosting on the instruments was slight and acceptable, no problem at all on the FBW 320, those with higher spec machines may not even see it.
Driver version 572.16 and DLSS 310.2.1.0
OverKillSimulations
Window 11 pro 64
Thrustmaster Airbus SideStick & 2 Lever Quadrant
Ryzen 5800X3D SCFM 2000 FUMA2 cooler ( Ectotherm compound )
GIGABYTE RTX 3060 Ti 8 GB GAMING OC Pro
Corsair Vengeance LPX 32GB (DDR4-3200)
Gigabyte 1TB M.2 PCIe NVMe
Gigabyte B550 AORUS ELITE
MSI Optix 3440 x 1440