Worked like a charm. MS Store version. I said it in another post… people will have issues when they will update to new drivers… you have to:
BTW just downloaded DLSS swapper for the first time and it installs a nvngx_dlss.dll.dlsss file along with the other files, is that normal? I never seen a .dlsss file before?
My content folder shows:
nvngx_dlss.dll
nvngx_dlss.dll.dlsss
nvngx_dlssg.dll
nvngx_dlssg.dll.dlsss
Is this what everyone else has when using DLSS Swapper?
Is it just me, or is there a lot more pop-up terrain with this driver, especially over Vexcel locations? I’ve set the TLOD to 100 during these tests and VRAM 80-90% (with a 3070 8Gb+BETA 1). Previously, I didn’t experience much terrain morphing in the same location, even with the Beta.
Now I always wonder if it’s the driver or changes at the server level… sigh…
Attention, do not select preset J. According to the README, “latest” is a new model, K, which is newer than J.
How do we get this K preset? Is there another xml file we can get for the nvidia profile inspector app? 
Thanks! Testing now in 2D… with J… Looks like less ghosting, but who knows since I can’t test in VR for a few hours 
are we expecting dlss v4.0 in dlss swapper. i dont see that yet
It’s in the Nvidia app, where it says to select “latest” in the override. It’s the same as preset K, but for me, everything appears grayed out as incompatible. I’ve tried everything suggested here, but it still won’t let me.
Ah ok. I don’t use that nvidia app. I use dlssswapper and profile inspector, so I’ll wait for someone to come out with the file that unlocks that preset. Or just test on the J preset for now. Thanks!
The nvidia app continues to amaze me with its broken features (the fps killer bug was also not fixed, they simply disabled the feature that caused it by default).
Uninstalled it immediately after testing the new overwrite feature which is so broken, man I had a good laugh.
I have a Portal RTX game and in it you can select the preset “last” in the Nvidia application and when you open it in the profile inspector, these values appear as in the screenshot, if I select the preset “K” in nvidia, then the value J is applied, Nvidia writes that you need to select “last” just in it all The implementation, I’ve tested, everything works great.
According to the official documentation, preset K is different from preset J. What I don’t know is whether, like so many things, it’s bugged in the Nvidia app and when you select “latest,” it does it wrong and picks J instead.
it is not under game profile, check under Global one
is it better then the 571.96 that i have installed now, with profile J that i installed now?
No idea, it still won’t let me activate it.
same
I honestly think that Nvidia is making the Nvidia profile inspector look simpler.
That’s my opinion right now.
I am totally confused with what to do now to get the best settings…
Should I delete the nvidia app? If I do this, will my settings set to default if I messed with this override settings?
I guess I need inspector, never used it before and no idea what it does etc…
Hopefully someone that knows what they’re doing will write a clear guide.
The problem right now is that the Nvidia App is buggy.
The other problem is that we don’t really know if DLSS 310.1 is the latest file/algorithm that nvidia requires to use the full potential of DLSS 4.0.
This was presented as a simple solution from “day 0” but it’s not.
Ok I’m confused now, too (not hard to do lol)…
I have the latest driver. Installed after DDU.
I have the dlss swapper and I swapped MSFS to use 310.1.0:
I have the nvidia profile inspector dlss 3.1.11+ etc etc set to use the last setting 0x00FFFFFF (which someone said equates to the new K preset) like this:
Is this right? If not, can someone please explain it to me like I was five years old 
Hello everyone, I was flying normally until I landed and restarted the simulator as usual when I change aircraft. The simulator closed normally, there were no errors. Until I opened the simulator and it showed a window to choose safe or normal mode. Well, the game closed normally, so I clicked continue in normal mode and it went to the initial loading screen of MSFS 2020.
With that, when it got to the middle of loading, it started to close. I restarted, and it closed again. I thought it was a mod of mine installed in the “community” folder. I cleaned the “community” folder, nothing. I cleaned the reserved space and save of the simulator, nothing. Finally, more rudely, I uninstalled the simulator and installed it again, thinking it would go back to normal, nothing.
Both safe mode and normal mode have this
Now I have no idea, I have already removed the driver, reinstalled the Nvidia driver, removed some graphics-related programs like MSI Center, nothing.
One thing to note, I have 2024 installed and it is opening and starting normally.
I will leave the error that appears in the Windows Event Viewer and would appreciate if anyone has experienced this and found a solution.
Windows 11 22H2 26100.3037.
Warning appearing in Event Viewer:
Faulting application name: FlightSimulator.exe, version: 1.38.2.0, timestamp: 0x00000000
Faulting module name: 190_E658703.dll_unloaded, version: 2.7.10.0, timestamp: 0x67940d50
Exception code: 0xc0000005
Fault offset: 0x000000000002ccc0
Faulting process ID: 0x2C7C
Faulting application start time: 0x1DB732E816FF8D5
Faulting application path: C:\Program Files … Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Path to faulting module: 190_E658703.dll
Report ID: 4e3f44bf-3dd4-44e3-a773-88303d3cc7e0
Full name of faulting package: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Application ID for faulting package: App
MSFSReport-Crash.txt (12,8,KB)
