Yes, similar, but in both the DLAA and DLSS Quality tests, Preset M used more resources than K. And because I was really trying to push the limits (3 screens, 4K, Ultra settings…) It was just possible with Preset K with some minor stutters, but with Preset M, it was really struggling - a subjective observation hinted at in the numbers:
Frame time worse (the 2nd number, under FPS)
GPU and CPU memory was higher
TLOD and LOD Factors (where the sim dynamically reduces TLOD to try to maintain minimum FPS set in settings) were lower
On screen stutters were worse
Preset M does show slightly more detail in distant objects (which I probably won’t notice), but to use it I would have to reduce other settings (TLOD, LOD, shadows, etc). I’ve opted to try K for now, which does line up with what NVIDIA’s FAQ suggests, that M is really for DLSS Performance (50% render scale).
I also had a few crashes yesterday. Very frustrating. Only change was the DLSS and driver update. But it’s MSFS, you can never be sure it is NOT the cause.
Watched a Utube by VRFlightsimguy on this subject and he seemed to think preset L was the better choice as although visuals were slightly better with M, L had a better performance.
Haven’t had a chance, yet, to try it for myself as away from my sim for a bit.
I have a feeling it maybe some setting relating to color calibration. If I am the only person noticing this, must be my rig. Overall it is an improvement.
I had great success using the new driver with the M preset in VR on my machine but….I switched out of VR to get some dinner and when I went back into it later, there was noticeable stuttering. I have noticed this behavior before where making major changes during a flight can result in a very different experience when you go back to your defaults. Generally it settles back down if you leave it alone. This has also happened to me when I changed sim rate and then went back.
Are you sure? The general consensus has been that M performs better. Which makes sense since M is optimized for the Performance quality level and L is for Ultra Performance.
It could very well be caused by problems on the Asobo server side. Yesterday folks were complaning of large FPS drops during sessions for no apparent reason. Today everything was fine.
RTX 3060 12gb settings that I have found that work very well for 4K.
Use image scaling in Nvidia control panel in global settings set to 1440p on a 2160p screen.
Set for MSFS24 DLSS Override Super Resolution to Performance (50%) in Nvidia App.
Set Model Pre sets to Model M in Nvidia App.
Set Nvidia VSYNC ON in Nvidia App
Set Negative LOD Bias to CLAMP in Nvidia App.
Set MSFS24 to new resolution of 2731x1440 so Nvidia App upscales to 4K resolution.
Then set MSFS24 to maximum frame rate of 60 for a 60hz screen.
Set Target Frame Rate in MSFS24 to 30 in Dynamic settings.
Use 2x Frame Generation.
Nvidia DLSS Mode in MSFS set to PERFORMANCE.
I use High pre set in MSFS24 with TLOD at 250-300, OLOD 200, Ultra Clouds, High everything else except Motion Blur OFF.
I also use Active Sky in passive mode with Realturb CAT for winds, AIG Traffic controller set at 99%, and FSRealistic, and smoothtrack on my phone for head tracking.
