If you do not add the extra file. you will NOT be using new processes.
3 Likes
did my test Quality has even less ghosting then performance and keeps it even better readable. DLAA is even better it is TLAA but without the weird fringing you get around small lines like far gears or lamp post.
Balanced 46 FPS ish
Quality 43 FPS ish
DLAA 41 FPS ish
on stand and scrolling the QNH wheel fast to create the blur in the a321Neo in KASE. I’m CPU bound so i think the FPS could even be just some (bad)luck after a reload.
Nope. I have no reg entry named ShowDlssindicator at all. I have tried Override DlsssHud set to Default and then Force Enable, in DLSS Tweaks and nothing shows up in the registry, nor on screen in FS2024.
If this is not present in the system registry, the DLSS version and profile letter will not be displayed in MSFS. 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:00000400paste 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.
BTW, I’ve noticed even some YouTubers are repeating the mistake of calling the file from Cyberpunk “DLSS4” – the DLSS_Indicator clearly shows it’s still version 3 not 4.
Even in Cyberpunk it shows 3.
I’m on Pimax Crystal
Same here, applying the preset J causes a crash on MSFS 2024 on startup - also around 89%. I’ll shelve this for now, but it sounds promising based on the feedback in this thread, so I’ll revisit it perhaps after NVIDIA officially release the new drivers.
Even the sim update 1 beta looks amazing and I feel blessed to be using my Pimax Crystal Light.
Today I experimented flying over the Grand Canyon one of the best moments ever in my flight simulator life.. which started in 1988 “flying” at 3 seconds per frame 
Topic title edited for clarity 
2 Likes
Thanks, that worked. 
You’re welcome
How did you get v310.1 to stay active with the Beta?
When I swap the file, it always gets reverted to 3.7.x when I start the sim, so I can only either run the official MSFS version with v310.1 or the beta with the old DLSS files…
I just played the beta for the first time today. After downloading it from Steam, I used DLSS swapper to update it to 310.1.0 and it worked fine. Just checked now and DLSS Swapper confirms it’s still on 310.1.0
Do the properties of nvngx_dlss.dll in your MSFS Content directory also say that it is version 310.1.0? DLSS Swapper on my end also believed that it had patched the file but in reality it was set to the MSFS’ standard version when I startet the sim.
OK started the beta sim again and 310.1.0.0 was active and working. Rechecked the file details and it still read 310.1.0.0
Still looks amazing in VR too.
2 Likes
Are you using Steam version ? I cant find this file on Steam version for some reason thanks much
Yes, I’m using Steam version. I have it installed on my D drive, so for me it’s in D: Steam Library\steam apps\common\Limitless
1 Like
I found it from another post thanks so much - man I need a vacation
It was fine just wanted to be sure
Did anyone try the upcoming nvidia driver from here ?
You need latest updated profile inspector to use upcoming nvidia driver and test dlss 4 working maeby better with it?
https://github.com/Orbmu2k/nvidiaProfileInspector/releases/tag/2.4.0.8
One report from reddit:
“after upgrading to dlss 3.10 it improved quaility by a lot but dropped fps down 20-25fps. The new driver boosted that 30-35fps at the same quaility def worth doing imo.”
Because .DLL Name is not matching with version of DLSS …
DLSS 3 starting with 2.4.x SDK