Can anyone confirm if this fixes the performance issues in 2024?
Itâs widely reported people can not override MSFS 2024 to get DLSS 4 in 2024 with the Nvidia App override settings, the options are greyed and unavailable.
Maybe itâs working for you in 2024, but I think if so, you are in a small minority! Or maybe itâs working for you in 2020 as it seems to be reported it does and you are not making a distinction in your reply between 2020 and 2024?
I had to use the Nvidia Profile Inspector to get DLSS4 overrides enabled for 2024 and other have used DLSS Swapper.
Iâm unaware of anyone actually verifying getting DLSS 4 (v 310.2.0) in 2024 with only the 572.16 driver and Nvidia App? Maybe some have? Maybe some people just assume they have DLSS 4 working, but havenât used the registery edit to display the DLSS info or any clear way to confirm and are just making an incorrect assumption and living in blissful ignorance/delusion on this matter?
I installed the patch and reinstalled the nvidia app and it already placed those DLL 190 files⊠I opened the simulator and it closed as usual when those DLLs are there.
Thanks for info.
After MSFS 2024 was freezing during the shutdown process I tested it 5 times and it closed without any issues.
I wonât speculate on why itâs working now.
This current mainline (non-hotfix) driver has been working fine for me in both FS2020 and '24 since release. And that includes having the Nvidia App installed as well. The release notes for the Hotfix do not address games or issues that are relevant to me, so I will refrain from this fractional update unless circumstances change (such as a new SU1 Beta build that is unstable with the release driver).
Dude the patch notes CLERLY states its for Valorant and FFXVIâŠ
It does not, still terrible performance shortly after starting a flight.
@tenpatrol do I have to do it with my FS2024 and 4070 Ti Super?
If you still want to have the latest DLSS4 without installing the Nvidia app and DLSS Swapper, the recommended tweak remains using Nvidia Profile Inspector and editing the 5 settings, which Iâve described step by step in the first post of this thread.
https://forums.flightsimulator.com/t/nvidia-hotfix-driver-version-572-24/703504
I also can confirm that freeze on exit. (572.16)
I not only had the freeze when I exited MSFS24, my CPU usage remained high when I was in the game. Like something was stuck in a loop for some reason. Resolving I had to revert back to an older driver, leave the beta, then rejoin the beta.
I have run away as far as I can from the latest Nvidia drivers for now.
i9-14900KF, 4080 Super, 32gb DDR5 ram.
Hi TenPetral and all the others,
thank you very much for your engagement. I followed your advice.
Newest driver (hotfix), the newest dlls-files and the adjustments with the nvidia-inspector.
NVidia-App not installed.
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.
with the 5080 just disable the overlay in nvidia app and it runs
From NVIDIA release notes:
âTo be sure, these Hotfix drivers are beta, optional, and provided as-is. They are run through a much-abbreviated QA process. The safest option is to wait for the next WHQL-certified driver.â
So, donât buy snake oil from tweak shamans 
If someone claims any improvement, itâs most likely just a placebo effect or simply that the servers are less busy. Piling up these tweaks and hacks is a recipe for trouble, making it even harder for developers to investigate and fix real bugs.
4 days ago, I wrote âŠ
If the new game ready driver or hotfix helps someone, thatâs fine. If it doesnât and they write about it, thatâs also fine because thatâs what this topic is for.
Thank you for info.
TenPatrol, I saw your post and completely agree with you:
However, this also means that beta drivers come with the same risks, and promoting them is irresponsibleâespecially when youâre fully aware of those risks.
In all fairness I donât believe 572.16 was a beta driver? The hotfix is. The DLSS tweaks never caused me problems. It was the 572.16 driver that messed me up with MSFS24.
Having said that anyone promoting tweaks, registry hacks, or whatever should warn that doing so is at the users own risk and could cause system instability.
I have read the feedback over at Nvidia and there are horror stories related to 572.16 and the hotfix hasnât fixed everything. Itâs a mess.
I believe Microsoft/Asobo should take action and somehow flag such topics or posts (e.g. as âunsupportedâ), ideally through a dedicated, technically skilled forum manager. This hacking voodoo, spreading like a plague, is becoming a serious problem, harming the product, the developers, and the entire community.
Nvidia did the most harm. I blame them 100%. But yeah, some kind of moderation might be helpful to some. I think most like to experiment with tweaks, I know I do. But all the tweaks posted did not cause me the problems the latest Nvidia driver did.
Actually 572.16 should have been labeled as a beta along with all the associated risks.
If my memory serves me right, youâre having issues even with older driver versions and also experiencing some kind of high CPU usage problem.
Anyway, youâre right about the mess. Many players have gone back to older driver versions, which is fine. There are also players who still want to test the game in its beta version along with the beta driver and thatâs perfectly fine too.
There are also players who tweak their system and the game and thatâs okay too - as long as they remember what changes they made and know how to revert them if needed.
That applies to recommendations like choosing the âC,J,Eâ profile in Nvidia Profile Inspector as well - that software is part of the HackingVoodoo group âŠ