It works and in its panel you can choose DLSS or FSR3 frame gen.
Just force profile K with nVidia inspector because the inbuilt DLSS profile selector may cause CTD.
This is what I meant when I said peoples problems may depend on what version of the Names file they are using. Most of us probably started trying this stuff straight away and were using the early guide so the differences they were seeing were down to that rather than your version of the guide (as were mine)
1 Like
ok, so if you did this is the “early days” – we have to have the .xml and manually select “profile K,” is that correct?
If you used the early guide then yes.
Just to add - Once you get the DLSS Override options appearing in the nVidia App you can choose the ‘Latest’ option and this will always select the latest letter regardless of what is in the Names file for nVidia Inspecter. You wont have to faff with that anymore
1 Like
I have looked at the NVIDIA forum and many report issues/CTDs with 572.16 in many games. Most have reported rolling back to 566.36. Maybe we need to wait for a driver update or hotfix from NVIDIA 
1 Like
I have just tried your recommendation and in 2024 without the nvidia app installed and without the npi xml file, it doesn’t work.
Preset E // 3.7.20
Now if I add the xml file and install the nvidia app…
Preset E // 3.7.20
Same.
Must say that I repaired the game files so the last official dlss dll are present. Steam version.
I am seeing the same thing. I am not using MSFS 2024 beta. I wonder if that is the reason why we are seeing this and only seeing Render J
Did you select ‘Latest’ in the nVidia App override options? Also do you have the very latest dll’s? If so it will then say ‘K’
Ok, here’s a follow up - anybody know what autoexposure ON means? And should I have this off? And, if so, how to turn it off? I have no idea what it does, it just shows up in the overlay:
(All this messing around is making me want to just go back to TAA 
)
Did you update the dll’s? 3.7 are old versions
My guide does not enable FG – you can turn FG on in MSFS settings, but since you’re playing in VR, it’s unnecessary for you anyway.
1 Like
Lol I assumed it was to do with lighting. It is turned on in 2020 for me but off in 2024
Yeah. In the Nvidia app I have FrameGen override set to latest. I’m not on the beta for 2024 . The latest DLL is see in the swapper is what is set in my DLSS swapper. 310.1 is the latest in there.
Any idea what it does or if it should be on/off?
I didn’t do the dll manual override on purpose.
(I already tested K that way and works)
The OP said (If I’m not wrong) that this method gives you the latest dlls without manually injecting the 310.2.1 files. Am I right?
Why do you need Swapper if you have “Latest” selected in the Nvidia app?
I was just curious why I’m only able to get Render J and not K. Is it bc I’m not on the Beta?
A guy found a fix on reddit. He said he filled his bath tub with cold water, and tossed his PC inside the tub. Said he hasn’t had anymore issues with the new DLSS. May be worth a shot
7 Likes
Yes, also Nvidia Profile Inspector it’s an integral part of my guide.
Following my guide, there’s no need to replace files or use the Nvidia app.
If you select Latest for All DLSS Technologies then it will use it for Super Resolution as well rather than just FG