It appears that MFG is available in SU2 with DLSS on. There is now a Framerate Multiplier field with 2X, 3X, and 4X settings available. Folks with a 5 series card and an interest in this capability might want to check it out, I have not flight tested it yet.
1 Like
The DLSS compatibility issue with 572.xx branch drivers has been resolved with this SU2 update as well. As an RTX 3090 user, I had the option of rolling back to driver 566.36 if I wanted to use DLSS. With SU2, I no longer have to. Well done.
3 Likes
Before today I just about hated every DLSS setting I could try on my new 5070Ti, so I was looking forward to SU2 to see what I could get out of it. Right now I’m liking TAA with 2X FG but the sim is not letting me select 4X FG with TAA or DLSS. Wondering about that.
3 Likes
Sounds like they still have some work to do on it. But a definite improvement so far.
2 Likes
Same, 5080 and I can choose 3x or 4x but it always reverts back to 2x.
4 Likes
And I just took a tear through a bunch of DLSS/DLAA combinations looking at the G1000NXi in the C208, not liking what I am seeing at 2X! Going back to TAA for a while with FG off. Thoughts?
1 Like
Amen to using TAA instead of DLAA. While DLAA is good, TAA is definitely better visual quality. And with your 5070Ti, I’m sure your frame rate is still solid.
3 Likes
With a 4070ti DLSS is still blurry. TAA makes my PC sound like it’s gonna take off. 2020 was great with DLSS
1 Like
There’s nothing in the release notes about DLSS 4 ( Sim Update 2 Beta (1.4.7.0) Release Notes - March 25, 2025 - Sim Update 2 Beta | MSFS 2024 / Beta News - Microsoft Flight Simulator Forums) though they did indicate on one of the developer streams SU2 would implement DLSS4 (at some point, who knows?).
Could you elaborate a little more on how/why you came to this conclusion?
I downgraded to 566.36 to restore usable 2024 performance (572.x drivers would lock up the game in free flight), but might upgrade again if they are supporting it properly. Or maybe wait for NVidia to release some more stable drivers, as the issues are bigger than MSFS it seems. https://www.reddit.com/r/hardware/comments/1jhkzxo/psa_nvidia_widespread_black_screen_or_hard_os/
As per usual, some people have issues and some don’t though. Silicon and driver lottery!
1 Like
Check the description in the right info box when selecting DLSS in the graphics settings. You will find a confirmation there.
1 Like
Thanks. Can you post a screenshot?
I usually wait for an update or 2 before jumping into the beta, just in case it’s twitchier than usual twitchy.
Yes, thanks. They don’t say DLSS4 specifically but mutli FG is DLSS4 specific for 50* cards only so I guess that’s confirmation of official DLSS4 support now.
Though going by some comments above it still seems to be a wip as they can’t actually select 3 or 4 it seems.
At least it seems more stable now for x2 at least, is it?
Is it smoother or just not freezing?
Were you using DLSS4 before SU2 beta?
If so, are you saying it’s worse than before?
In my testing before reverting to older driver, DLSS4 was significantly sharper even on DLSS performance than DLSS3 with FG, on a par with TAA.
That was replicated on MSFD 2024, Starfield, and EA WRC using NVProfile Inspector global DLSS4 override. The only one that wasn’t stable with it was MSFS 2024, it would freeze after a while, FG especially.
I can’t imagine that’s gone backward sharpness wise, as it’s driver specific (DLSS4>DLSS3), not game implementation dependant (on MSFS 2024 side for stability).
NVidia bears a lot of responsibility for these performance issues too, it’s not just MSFS DLSS implementation issues. NVidia driver releases are a real lottery atm.
1 Like
They do say DLSS4 specifically for the Anti-Aliasing setting.
Ok, I took the plunge and updated back to 572.83 + SU2 [4070 OC]
Ran a race around my test circuit @ Mollis on High Quality TLod 200 + Ultra Clouds + FG and it hung in there this time. A couple of small glitches but it recovered, wheres before the screen would blackout and it would lock up windows for about 5 minutes before CTD.
It would typically do that straight off the runway here, but I made it all the way round back to land. If I dropped the settings a touch in some areas I could eliminate the hitches, I just wanted to see if it would choke completely.
So looks fixed to me, hopefully NVidia will also continue to improve performance. DLSS4 is sharp enough for me.
That was @ 300kt. Now to test it at 600 in the F35 to see if that kills it!
Update: That worked. I got a black screen for a few seconds when it was loading the F35 cockpit, but it came good eventually.
I think it is also important to understand that FG is not there to make games playable at 60-70 fps, but to smoothen out performance in high refresh rate scenarios.
FG is intended to being used starting at a minimum (non-FG) base framerate of 50-60 fps. A LOT of people do not realize that. But you also have to blame NVIDIA for not making that very clear. They probably do it on purpose to create the illusion for potential customers that FG will make anything playbale for you…
3 Likes
While that might be technically true, it works quite well below 50-60 fps to smooth things out, despite that being the so called technical limit.
I’ve been running an RTX 2060 for a long time, and FSR 3.1 FG works on the 20 series card unlike NVidia’s restriction, and works really well. Starfield is butter smooth with it.
Use your eye to judge. If it works, use it. Or drop your settings a bit. Lots of ways to reach your target rate depending on the quality you want, or are prepared to work with, depending on the scene complexity.
Tbh I think the MFG is a bit more marketing spin than actually useful compared to FGx2, but I guess we’ll see. How many FPS do you really need to enjoy a game?
5 Likes
I 100% agree with you.
It’s for you only to decide if it works for you or not in any scenarios you want to use it, for sure.
But I am just reading so many complaints from people about artifacts, smearing, etc. while using both upscaling and FG with low base fps and resolutions. Those people simply do not understand what they are doing and they have 100% false expectations while blaming NVIDIA or Asobo.
3 Likes
it seems that SU2 beta 1 is packed with dlss v4 (310.1 version, not the latast 310.2.1) and preset is set to J. Same ghosting in VR as swapped 310.2.1 with K profile
1 Like