I have the opposite problem - The ‘Enable’ entries arent there but the ‘Override’ entries are. I think it may depend on what version of the CustomSettingNames.xml file is being used
This can happen if on the first run of the game you have Digital Vibrance turned on in the nVidia App. I had the same problem with Far Cry 3 yesterday. Had been playing it for a week but after updating for DLSS4 it wouldn’t load. Turned DV off and it works again. Worth a try
1 Like
File CustomSettingNames.xml is not officially added to NVIDIA Profile Inspector, so if you have it, you can delete it.
Alternatively, you can change the extension from .xml to .xml_copy.
There should only be three files in the NVIDIA Profile Inspector folder.
If you have more files, be aware that they may affect NVIDIA Profile Inspector.
The options don’t appear without it, at least for me (just tested again to make sure). Problem maybe that people have downloaded it at different times from different sources
“Please add the msfs-2020 or msfs-2024 tag to your post, depending on which sim your post is about.” → I can add “msfs-2020” as a tag after I chose “PC”. Not before that. It took me some minutes to find out… Thanks!
The new NVidia driver brings DLSS4 and so the option for frame-generatrion for older RTX cards disappeared. It was ok using dlssg-to-fsr3-0.100 with RTX 2.xxx or RTX 3.xxx cards.
Now I wonder, which option is better.
DLSS4 brings a performance boost over using pure DLSS 3. But dlssg-to-fsr3 broght the double framerate on my notebook.
I have to admit, that sometimes it got into a struggle with extreme flickering/ghosting which I handled with pressing Alt+Enter twice to enter windowed mode and back to fullscreen again.
What Do You guys, who used dlssg-to-fsr3 so far with Your older PCs?
Go back to a DLSS - 3 driver? Or use the new one (and hope for a release of dlssg-to-fsr4)?
Optiscaler FG works with the new driver and has the hud fix.
Check it out: Release v0.7.0-pre66 · cdozdil/OptiScaler · GitHub
Yes, in my case I do not need the DLSS Swapper, because the swap is being made by NVidia app itself (like you can see in the corner)
I did not download any DLLs or used any other tools like inspector, just used the NVidia app.
Some folks are saying that it can cause CTD on DX11, I am using DX12 however,
I have Nvidia App and DirectX 12 but still crashes in MSFS2020.
There is a quick tutorial above in this topic, I just followed it.
I have written exactly where to download NVIDIA Profile Inspector. If there are no additional files in its folder and you haven’t replaced any game files, it should work.
If you want to see the DLSS version and “render preset” during gameplay, as shown in my screenshots, you’ll need to make changes in the system registry.
. You need to manually add an entry to the system registry. Copy the code below
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore]
"ShowDlssIndicator"=dword:00000400
paste it into Notepad and save the file as DLSS_Indicator.reg (not as a text file, this is very important). Then run the file and agree to make changes to the system registry.
If you no longer want the DLSS version to be displayed, you can edit the registry.
Open registry editor (regedit)
Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore
Double click ShowDlssIndicator
under “Value data” set the value to 0
Click ok and restart PC.
Source https://forums.flightsimulator.com/t/nvidia-game-ready-driver-572-16/702204/281?u=tenpatrol
2 Likes
I am fully aware where to get Profile Inspector. I am also fully aware the archive only has 3 files. What I am saying is, without adding the Names file, I do not get the DLSS options which is why I added it.
Just to add, I got all this to work yesterday but I needed to add the Names file to get it to work
1 Like
There are various types of CTDs - for example, CTD when clicking “Fly,” CTD during flight, CTD in the main menu, CTD during game loading (around 50%) and many other CTDs. You haven’t specified exactly when your CTD occurs.
Ive followed the guide, but it’s showing preset J and the old “swapped” dlss file…the .xml was removed from NI folder.
1 Like
I did all this in NPI but I’m still showing Render preset J. Confused as to how you got Render K.
Thanks for the post re: profile inspector and using it instead of nvidia app… I have always disliked any nvidia stuff other than the drivers, of course. So I use the profileinspector… one question:
I have the newest DLSS version d/l’ed from the swapper:
But I have an odd view in the profile inspector… I think I d/l’ed a new customsettingnames.xml file and that’s the reason.. I am showing the correct dlss version in the overlay (used the regedit tip to get that to show). My profileinspector looks like this:
Questions: Can I delete that customsettings.xml and just use the base?
And do you have any idea what each of these do:
-
Enable DLSS-FG override
-
Enable DLSS-SR override
-
Enable DLSS-RR override
-
Override DLSS-RR preset
-
Override DLSS-SR presets
I am using VR so I don’t need Frame Generation, by the way.
Thanks in advance for the help!!
How do you know it supports the new dlss4?
No mention of this in the notes?
Same for me. Man this is so confusing . Lol
1 Like
File CustomSettingNames.xml is not officially added to NVIDIA Profile Inspector, so if you have it, you can delete it.
Alternatively, you can change the extension from .xml to .xml_copy.
There should only be three files in the NVIDIA Profile Inspector folder.
If you have more files, be aware that they may affect NVIDIA Profile Inspector.
edit
But if you have replaced files using DLSS Swapper or manually and you have customsettings.xml in the NVIDIA Profile Inspector folder, it means you have used a different guide in the past. In this case customsettings.xml file is needed, for example, for the J profile.
It’s up to you which guide you choose to follow.
Thanks! And sorry, this thread has gotten long and somehow I missed someone’s post that’s pretty much identical to mine 
I reverted to just use the default xml in the profileinspector. But do you know if setting these will enable FG? I don’t need/want it since I’m using VR (and VR won’t use FG and I don’t use ASW which is like VR FG lol). Thanks again:
- Enable DLSS-FG override
- Enable DLSS-SR override
- Enable DLSS-RR override
- Override DLSS-RR preset
- Override DLSS-SR presets