11 hours ago, RobJC said:

With Developer mode open look at the render resolution of DLSS Quality and compare it to TAA. You will see that TAA renders 1:1 with your screen resolution, while DLSS Quality renders at 67% of your screen resolution. That is where your blurry issues come from. SecondaryScaling is a way to increase the render resolution beyond 67% without using TAA at 100%. 

But then what do you get (by trading TAA for upscaled DLSS)?

5 hours ago, Baron2829 said:

RobJC, I don't know how to thank you for this post. I can't say I fully understand the mechanics of these settings but I get the gist. I'm running a 2080ti and tuned my secondary secondary scaling to 1.65, DLSS balanced. Just teetering on the border of a main thread/gpu limit. Getting an amazingly smooth experience on the ground at CYVR for the first time. I'm talking stutter free! Not 100% sure what's going on, but without your info, I would have missed this massive improvement. Thanks.

Glad it helped you. Definitely a game changer for some of us!

3 minutes ago, Noel said:

But then what do you get (by trading TAA for upscaled DLSS)?

Basically most of the performance benefits of DLSS without losing so much image quality. 

Remember guys, SecondaryScaling goes both ways. If you are happy with image quality but wish you had more performance, try lowering that setting to 0.9, .8, etc. 

10 hours ago, RobJC said:

I messed with PrimaryScaling but never witnessed that parameter actually doing anything. The only values that did anything were the SecondaryScaling value and the DLSS setting (Quality, Performance, etc.). In your examples above SecondaryScaling does what you believe PrimaryScaling was doing. It looks like the one scaling opportunity is accomplished with this parameter, and not with the PrimaryScaling value. I will try to test PrimaryScaling more tomorrow but i suspect that parameter does nothing. 
 

 

Ok, that would explain a lot of my confusion. Why not use the in-game scaling setting vs editing the config file?

I think what they are saying is Quality DLSS is 67%, the other DLSS settings are lower. You can't go higher than 67% using  the in game settings. Editing the config file secondary rendering allows you go higher than 67%. The higher you go, the less artificial tricks DLSS has to play to render at screen resolution. So the image will be better, but the frame rate gained by those tricks will be less. 

I think the default secondary rendering of 1.0 can  be increased to about 1.7 or something (for better image quality). Or reduced to maybe 0.6 (for better fps ). You are doing the same thing as changing the DLSS settings in the game, but you can go below High Performance DLSS setting at one end of the scale, or higher than Quality at the other end (by changing the Secondary Rendering in the config tile).

I may not be entirely correct on this.

Would be nice if Asobo had more presets for DLSS to make this easier.

32 minutes ago, Virtual-Chris said:

Ok, that would explain a lot of my confusion. Why not use the in-game scaling setting vs editing the config file?

There isn’t one for DLSS. 

25 minutes ago, RobJC said:

There isn’t one for DLSS. 

Ah ok. Strange. Thanks. Sorry for derailing your thread as I tried to wrap my head around this. 

10 minutes ago, Virtual-Chris said:

Ah ok. Strange. Thanks. Sorry for derailing your thread as I tried to wrap my head around this. 

No worries Chris. I think we are all trying to wrap our heads around this. 😀

I guess I'm a little thick...I don't see those numbers when I enable the FPS counter in developer mode.

Are they always there or is there some way to turn them on. Maybe I just missed them.

Out of interest I just spent a few minutes looking into this, as a VR user any blurriness is a No No from my point of view, for that reason DLSS has always been ignored but I thought I'd give the methods in this thread a try.

Using OpenXR Toolkit I already lower to 70% Resolution in order to raise general MSFS graphical settings and using TAA(100) I get a nice sharp image with FPS 40+ in most areas, which has served me well for months with my 3070ti. Upon choosing DLSS the FPS increased marginally but at the expense of blurry visuals, so I upped the SecondaryScalingVR which slightly improved the visuals but at the expense of FPS which now went below 40 so it wasn't working as intended for my use.

I then set OpenXR Toolkit to 100% (which of course lowered FPS) and tried again, sure enough setting DLSS and SecondaryScalingVR I could get a clear picture without too much blur, but at the expense of having to dramatically lower MSFS graphical settings just to get near 40fps, which isn't as good as my original TAA setup, so I've returned to using what I've had.
Ultimately I'd rather have higher in game settings to make the world look pretty and average +40fps than a blurry image with more FPS, when/if nVidia create a "Mask" for DLSS areas so Asobo can use that for Garmin screens I may look into it again but as it stands for my personal tastes TAA + OpenXr Toolkit is by far my preferred option.

*******. Imagine spending all this time chasing performance instead of just enjoying the sim. This is like a debugging class. Who has time for this?

Just now, styckx said:

*******. Imagine spending all this time chasing performance instead of just enjoying the sim. This is like a debugging class. Who has time for this?

Because some people enjoy this sort of thing, if it doesn't float your boat then that's fine 🙄

On 10/21/2022 at 4:24 PM, RobJC said:

 

When I set it in NCP, I had to go into MSFS and change the resolution (in this case to 3840 x 2160). This made the following changes...

- Screen 3840 x 2160
- Post 3840 x 2160
- Render 2560 x 1440

As you can see, due to the Quality DLSS setting I had, the Render was 67% of the Post value. Sounds like a great solution, right? The problem I encountered was that at 3840 resolution I had lots of stutters. And I was running MSFS at 3840 but the rendered image was 2560. Not ideal. 

What if I could keep my screen and render resolution at 2560 (native) but increase the post processing to sharpen up the gauges? This is where SecondaryScaling comes in. In the UserCfg.opt file found in \AppData\Roaming\Microsoft Flight Simulator\ I was able to increase the SecondaryScaling value to increase the Post value, without having to run a higher screen resolution.

Here's the part of the file you need to experiment with... 

FSRMode QUALITY
    PrimaryScaling 1.000000
    SecondaryScaling 1.500000
    SharpenAmount 1.000000
  

Sir you are a prophet!. Thanks for making my day. I was struggling same thing, unless I found out my real resolution was 1707, inwhich had to be native 2560. An your scale method worked flawless. However i lost already 6 motnhs:)) 

Honestly I registered here just to thank to you. I spend lots of hours of my life with nvidia control panel, and fs options, restarted million times which take over 4 minutes only to start fs.. I was dissapoitted so much with amg ryzen 9 5700 and nvidia 3090 when i saw ppl with 60fps all the way green.. TAA was only option not to be blurry, but it had lower FPS. now I got all i wanted. I have fixed all 40 fps. and it is always green even in NYC with pmdg. 

thanks once again. +