TENPATROL

Of course, CTD may still occur on some hardware configurations and that wouldn’t be surprising since every system is different. In any case, I’m not experiencing CTDs but that doesn’t mean others won’t.

It looks like NVIDIA has fixed CTD during loading MSFS 2020 with Directx 11 and NVIDIA app installed. 1 Download Nvidia Hotfix 572.24 https://nvidia.custhelp.com/app/answers/detail/a_id/5624 2 Uninstall the current NVIDIA driver using DDU in windows safe mode. 3 After the restart, install the downloaded hotfix driver. Source https://forums.flightsimulator.com/t/nvidia-hotfix-driver-version-572-24/703504

Below is a link to the original guide. https://forums.flightsimulator.com/t/nvidia-game-ready-driver-572-16/702204/217?u=tenpatrol

DLSS Swapper is needed if you want to swap files manually and don’t have the latest driver. If you have the latest driver and don’t want to swap files manually or use NVIDIA app, then by following my guide, you will always have the latest DLSS 4 – game files are not replaced. Below is a link to the original guide. https://forums.flightsimulator.com/t/nvidia-game-ready-driver-572-16/702204/217?u=tenpatrol

If you swapped files using DLSS Swapper, you need to restore the original versions of the files. If you've used DLSS Tweaks in the past, you should also restore everything to the original versions and delete the DLSS Tweaks files. After that, please follow my guide, which I’ve written step by step on how to swap DLSS without using the Nvidia app or DLSS Swapper. https://forums.flightsimulator.com/t/nvidia-game-ready-driver-572-16/702204/217?u=tenpatrol edit Reinstall the latest Nvidia driver and do not install Nvidia app. After installation, create a new folder for Nvidia Profile Inspector and extract Nvidia Profile Inspector files into it. This is very important because it ensures that no other XML files interfere with the NPI.

If you're copying my posts, please be sure to add a link to the source. The source is the official MSFS forum. https://forums.flightsimulator.com/t/nvidia-game-ready-driver-572-16/702204/217?u=tenpatrol So could you please edit your post and add a link to the source with a note that you found the suggestion there and the author is TenPatrol? Right now, it looks like you wrote it yourself, but it seems you copied my post and made a few small edits to shorten it. Thank you!

I'm wondering when OP @Ianrivaldosmith will edit his post, as I can see he is active but hasn't done so yet. More information below. https://www.avsim.com/forums/topic/663308-dlss-4-definitive-guide/page/6/#findComment-5356826

Of course, OP must also add the source 😉 You're very welcome. Fly safe capt.

You're very welcome. Fly safe 🙂

It's highly likely that the cause is related to changes you made in the past, which were saved in the Nvidia Profile Inspector. Alternatively, you may have downloaded an XML file at some point and added it to the folder containing the Nvidia Profile Inspector - I'm pretty sure 😉 Go to the folder where you have Nvidia Profile Inspector and delete the file named CustomSettingNames.xml and then run Nvidia Profile Inspector. Fly safe. Source https://forums.flightsimulator.com/t/nvidia-game-ready-driver-572-16/702204/285?u=tenpatrol

If you're copying my posts, please be sure to add a link to the source. The source is the official MSFS forum. https://forums.flightsimulator.com/t/nvidia-game-ready-driver-572-16/702204/217?u=tenpatrol So could you please edit your post and add a link to the source with a note that you found the suggestion there and the author is TenPatrol? Right now, it looks like you wrote it yourself, but it seems you copied my post and made a few small edits to shorten it. Thank you!

If you're testing the MSFS 2024 beta, it's normal because it's actually a beta of the beta version. If you're playing what we'll call the stable version of MSFS 2024, then this behavior is not normal. I recommend checking MSFS without any modifications. For example, try renaming "Community" folder to "Community_Copy" and create a new, empty "Community" folder.

I'm testing MSFS 2024 beta version and haven't noticed any decrease in FPS. I don't have driver 571.96 installed, which still includes DLSSv3 3.8.10.0. Additionally, I don't have the nvngx_dlss.dll file in version 310.1.0.0 from Cyberpunk.

It's better to wait 4 days for the new driver rather than installing driver 571.96. I don't understand why Youtuber Islandsimpilot called this driver "early access" and mentioned DLSS 4 as it's not early access and the driver actually includes DLSSv3 3.8.10.0.

Exactly mate.