SU2 Beta - Frame Limiter in User.cfg

Very good, I limited it to 30 and used the frame generator to go up to 60 with vsync and the smoothness is incredible, because the fps doesn’t fluctuate. This has to be implemented within the simulator!

4 Likes

(post deleted by author)

It would be so great if Asobo publish ANY change they do in a documentation not just some hightlights in release notes… it would help so much…

2 Likes

Can you describe your settings? I’m in doubt over this new frame cap.

Currently I have this:
Monitor at 4k and 60hz
frame gen: on
vsync: on on nvcp
reflex: off
freesync: on for both monitor and nvcp

Is there any advantage to use this new frame cap on userCfg file? Isn’t fsr3 frame gen supposed to cap my frames to half the monitor (30hz)?

I have just done this and WOW yes a massive increase in fluidity! This is the way to go!

On another note I almost gave up on the Sim yesterday, but a just re-installed it and I can now actually load a flight.

Is there any difference to limiting the FPS in user.cfg vs. the Nvidia game profile for MSFS?

1 Like

If you set vertical sync on in the Nvidia control panel it’s pretty much the same thing when using frame gen.

Negative, because with the nvidia or amd panel the fps within the game is free, for example: When limiting the fps to 60 through the nvidia application and turning on the fg, the game frame will oscillate and you may have 40 and 45 fps and it will only generate the rest to 60. By limiting 30fps in the cfg itself it will generate the missing 30fps and will have greater stability!

1 Like

Just saying if you monitor is 60hz and you have vertical sync on in the control panel and FG on in the game, the sim will never output more than 30fps. You can tell so by using the dev mode and looking at the FPS output. FG will make it 60 and the overlay will say 60 but not the game itself. Get what I’m saying?

2 Likes

Oh yes, it’s true!

Agree. And this is the crux of the matter for FG. The view may become smooth but we still have control resolution at the underlying frame rate for the sim, meaning that when hand flying we are not doing so at the higher rate FG delivers for the sight picture, so the sim may/will feel sluggish on the controls/response. This may not matter when on A/P or Autoland, but hand flying is not improved by FG save for what the pilot sees (which may be helpful for some pilot).

Hi, trying to understand what you mean here - doesn’t the limit include FG-based frames, so if you set it to say, 30, the sim would try to achieve 30 FPS with or without FG, and how is that different to setting the limit the Nvidia panel, where the sim would also try to achieve the set target with or without FG?

The sim outputs fps at whatever your hardware can achieve. FG adds an extra frame per output frame. The rest is math. Given your monitors hz, vertical sync will match your monitors hz. No, the frame limit would not apply to FG. Hope that explains it.

1 Like

Thanks, I understand how FG adds to the FPS but the FPS indicator would include these frames in the counter but okay I see so the frame limiter set to 60 would mean 30 max from the sim and 30 max from FG. But any difference from using the in game frame limiter or GPU app option?

Other way around. If you set the limit to 30 in the cfg file, you would get 30 max from the sim but 60 with FG. It really matters on your monitor. Mine is 60 hz So I use vertical sync knowing it will limit it to 30 in the sim and 60 on the monitor. If I had a 120hz monitor I wouldn’t use vertical sync because my system is strong enough to probably achieve mote.

okay, so your trying to achieve your monitor‘s target refresh rate with 60 FPS but if you leave the game frame limiter off and use the Nvidia app and limit to 60, the sim with FG would attempt to achieve 60 as well and with vsync on would compensate when it drops lower - I am trying to understand if there is any difference to using the in-game limiter to achieve the target FPS.

Yes. I use vertical sync because without it, I get screen tearing with FG. What works best for me is vertical sync on in the Nvidia app, TAA and FG on in the sim. Silky smooth constant 60fps in 2k
high-ultra settings. I could go 4k but then I’m pushing my 4070 to the max. Each system is different so you’ll have to figure out what is best for you.

This works so cool, i had a smooth expierience. I have set the frame limiter to 30, with frame generation on and set the fps in the nvidia control panel to 60 for msfs24. Before i had very little stuttering on taxi with the fenix and now… butter smooth wuth 60 FPS

1 Like

I am finding setting the limit using the parameter in user.cfg works better than using the in game method of dividing your monitor’s refresh rate. Using the in game method produces rhythmic stutters every second (you can even see the spike every second if you use the dev mode frame
counter) where as using the limit in the cfg file doesn’t. Also, I’m able to set a higher monitor refresh rate of 120 yet keep 30 fps as my limit which the divisor method doesn’t allow. I find using the higher monitor refresh even with the low cap helps. So, I do hope the parameter remains available and is eventually exposed in the in game options.

My current standard with Radeon in FS24 is using the driver “Radeon chill” FPS limiter + AMD FMF 2.1, which is quite a good smooth experience (considering it’s MSFS :smiley: )

Just tried the UserCfg.opt frame limit option instead of the Radeon chill setting. For me it creates a more unstable picture with tearing etc.; so I will stick with my driver options