Hi, should i use M or L preset? I read we should use L for 4k..
I use preset L - I only fly in VR with Quest 3/4080/7950x3D - seems to be the best mix of quality and performance. I’m getting 40-42 FPS in VR with 225/150 TLOD/OLD most settings on high with a few Ultras (clouds, rocks). Very impressed to be honest at quality, low latency and smoothness.
Is this not done with selecting preset M in DLSS swapper?
You can use DLSS Swapper to get the dynamic preset. However you need to do two things.
First you need to set the DLSS Override settings, for MSFS, in the Nvidia App to ‘Use 3D app setting’.
Secondly after you have installed the latest DLSS libs with Swapper you must also set the DLSS Preset for MSFS to ‘Nvidia recommended’.
You can easily check that it works by making sure that the screen overlay is activated via either the reg entry or the DLSS Swapper option.
Actually it doesn’t matter if you select the preset in EITHER NVidia app or DLSS Swapper. Whichever is changed last on either program will stay your preset.
You are absolutely correct, if both use the same versions.
However, through Dlss Swapper I am using 310.6.0 whereas if I had the Nvidia App selected I would still be using 310.5.2
When I update in DLSS Swapper it’s also updated in NVidia App. I don’t have two versions. DLSS Swapper updates the game version and preset.
This is not the case.
A simple way to prove it is next time you get a beta don’t use Dlss Swapper and test. If you are using the app as the director then you will get the latest version supplied with that and that, currently, for me is 310.5.2, if you have Dlss Swapper as the director then you get 310.1, currently.
At the moment I am using 310.6 because Dlss Swapper has control. At the moment, my Nvidia App is still at 11.0.6 and so it sets it to 310.5.2
I stand corrected - it was just coincidence that I saw a match on my PC beween DLSS Swapper and the Nvidia App. Although the preset is changed by either app and sticks, now see that Nvida App controls it’s own DLSS use and settings. Learned something new - thanks!
It is not a problem.
It is easy to get caught out unless you have a good handle on how things work. It doesn’t help when some versions that are released by Nvidia are not included in their drivers or app. Version 310.5.3 being the latest one.
At the moment, it doesn’t really matter - I rebooted earlier and got app version 11.0.7 - I am in sync again now with 310.6 but if there is a difference the only way to catch it is to have that display on your screen that tells you what lib version you are actually using.
Very true mate! Lots of ways to go about all this! For me (I only fly in PCVR btw), I’ve found it easiest to avoid using Swapper or the Nvidia app. I currently just use Nvidia Control Panel to set global 3d and game profiles I prefer. I download v310.5.3 from the TechPower website and copy/pastie it into my Steam msfs 2020/2024 game directory (properties/files/browse). I use the regedit mod to Show Dlss Indicator (google how to do this). I get preset M with dlss/performance and preset K with dlss/quality/balanced. Dlss/performance with preset M is currently my preferred way to fly. in VR with msfs 2020/2024.
I have tried using v310.6.0 overrides using Nvida Profile Inspector (together with various forced presets), but this did not improve things, and I lost a bit of performance, together with a bit higher latency.
I mainly fly heli’s dusk/dawn in cities like Osaka, Tokyo, and LA. My PC specs are 9800x3d/rtx5090/64Gb 6000ram. I mainly use a QPro with the official link cable at 750mbps dynamic bitrate and forced 45fps with asw off (40fps for me since I use 80Hz refresh rate).
Depending on your system and mode of flying, your results may differ. Cheers.
I got an CTD if I switch 310.6.0 to preset K in DLSS Swapper. Default preset C is working :(.
With Driver 572.42 and DLSS 310.6.0 (switched by swapper) preset K is running without CTD.
MSFS 2020 DX11 with RTX3080
I am trying to remember if I have got this correct but I think that preset K is for a transformer 2 driver (4.5). Which I think is 595 and upwards.
If I am correct then that would be the reason that it crashed. To use it you would need to update your driver.
Fair enough, I can understand you not wanting to mess with something that is working.
What I would suggest is that when you next update the driver that you use DDU to completely clear out anything connected with the current driver. The reason is that although you don’t need to normally when a big upgrade, like Transformer 2, is included it is best to clear out completely before installing the new one.
Will give it a try in the Future 
I‘m on Driver 572.24 and using DLSS 4.5 with preset M by using DLSS Swapper. So I can confirm that the newest driver is not necessary.
595.97 / 310.6 5070ti
Is DLSS and / or Frame Generation supposed to increase VRAM usage from TAA and no FG, or lower it? I had even lowered my TLOD and OLOD settings from what I was using with TAA and I constantly was getting high VRAM warnings. Went back to TAA and no FG and smooth as silk. Guess I should stop reading all the NVIDIA propaganda they keep emailing me.
Hi, you have a few different parameters and questions in play in your post above. It may help clarify to take these things separately rather than all at once. Leaving FG out of the picture, what DLSS does on my PC is render in 2K and output 4K to my 65” HDTV with entirely satisfactory frame rates. Were I to go back to TAA, the render would be 4K to get 4K output which is a bit more than my 5070Ti is intended to do along with satisfactory frame rates.
While counterintuitive, and as I understand it, FG adds to the processing load and introduces other effects, as you suggest in your post. These various technologies are complex in the setting of MSFS, so this is a good place to find out how others are using them. Hope this helps a little, there is more to your post than I have tried to address. My PC spec is in my profile. Cheers!
Yes, 100% correct you are, way too many parameters, especially when it comes to the monitors everyone is using. There was a thread last summer in which someone nailed it on the head when they said its nearly impossible to share and compare performance data when the monitor technology we are all using is from extreme to another. I am happy where I am without the DLSS and FG so I will just stay here until something else new comes along.