Just to verify: if I use the FPS Cap mode and I have my FPS limited via usercfg.opt to 36 FPS (before Frame Gen, target FPS WITH Frame Gen is then 72), what number should I put into the FPS field? 36 or 72? or slightly lower numbers, e.g. 34 or 70? 

And what does AutoFPS do, when I e.g. switch tabs resulting in a transient loss of FG and thus lower FPS? Sorry, I am sure it was already asked and discussed, but 208 pages thread is simply too much...

FYI: I put (1) the fps limit in MSFS2024 (SU3 in UI or usercfg.opt for previous versions) to 30fps, (2) then 60 fps in my nvidia driver and (3) put auto in MSFS_AutoFPS. I run frame generation x2 (in MSFS) with a 5070ti.

Edited June 18, 2025Jun 18 by vbazillio

36 minutes ago, AnkH said:

Just to verify: if I use the FPS Cap mode and I have my FPS limited via usercfg.opt to 36 FPS (before Frame Gen, target FPS WITH Frame Gen is then 72), what number should I put into the FPS field? 36 or 72? or slightly lower numbers, e.g. 34 or 70? 

And what does AutoFPS do, when I e.g. switch tabs resulting in a transient loss of FG and thus lower FPS? Sorry, I am sure it was already asked and discussed, but 208 pages thread is simply too much...

You don't ever have to read 208 pages to find out how to use the app. The readme, located on github and in the app's bin directory, in both text and pdf format, is lovingly and painstakingly updated and ignored after each formal release and provides ready answers to your questions.

The short answers to both of your questions are that you set your target FG FPS to be the same as your after-FG FPS cap in FPS Cap mode and the app knows that FG becomes inactive when MSFS loses focus and factors that in.

Edited June 18, 2025Jun 18 by Reset XPDR

7 hours ago, Reset XPDR said:

The new LSFG version 3.2 is being detected fine for me, including the correct multiplier:

What specific issue are you having?

This is how my AutoFPS looks if I set it to LSFG while LSFG is running.

 

24 minutes ago, mobiel said:

This is how my AutoFPS looks if I set it to LSFG while LSFG is running.

 

That's because you are using LSFG in Adaptive mode, as indicated on the status line, and you have manually changed from NFR to LSFG, which is not a valid configuration per the readme FAQ:

Quote

When adaptive frame generation is detected, a base FPS will be used for the target FPS because the frame generation multiplier is variable and is not currently detectable.

Edit: Upon rereading this, it may not be clear that base FPS refers to the new term NFR (Native Frame Rate) so I have updated that entry in the FAQ to clarify this.

 

Edited June 18, 2025Jun 18 by Reset XPDR

how do i get auto fps to revert back settings after unscaling lossless?

its stuck in lossless settings at 60fps

thanks

mike

1 hour ago, mikeymike said:

how do i get auto fps to revert back settings after unscaling lossless?

its stuck in lossless settings at 60fps

thanks

mike

Due to there not currently being any way to detect that lossless scaling frame generation is actually active, AutoFPS must assume that if you have the lossless scaling app running then you either intend to use, or are currently using, its frame generation, regardless of whether you have scaled to MSFS or not. As such, the only way to break out of LSFG detection is to close the lossless scaling app.

In short, with AutoFPS only have the lossless scaling app running if you are going to use lossless scaling with MSFS, otherwise close it.

 

53 minutes ago, Reset XPDR said:

Due to there not currently being any way to detect that lossless scaling frame generation is actually active, AutoFPS must assume that if you have the lossless scaling app running then you either intend to use, or are currently using, its frame generation, regardless of whether you have scaled to MSFS or not. As such, the only way to break out of LSFG detection is to close the lossless scaling app.

In short, with AutoFPS only have the lossless scaling app running if you are going to use lossless scaling with MSFS, otherwise close it.

 

Thanks for getting back to me

 

I did indeed close lossless scaling .

Then I restarted autofps 

Yet lossless was showing active.

Checked task manager lossless. was shut down.

 

37 minutes ago, mikeymike said:

Thanks for getting back to me

 

I did indeed close lossless scaling .

Then I restarted autofps 

Yet lossless was showing active.

Checked task manager lossless. was shut down.

 

 

The following feature was introduced in 0.4.5.0:

• Implemented functionality to store the last used graphics mode and automatically set it as the default on the next app launch.

Was it that? If so, that is now normal.

If you want to change the target FPS to another graphics mode than that the app started with before you start a flight session, just use the target FPS type drop down list.

When you start a flight session the current graphics mode will be auto detected and change on the UI if different to what you currently have showing. If you start and exit lossless scaling while in the flight session, it will auto detect within 5 seconds but if you are back at the main menu it will stay with what it last was when you finished your flight unless you manually change it yourself.

Edited June 20, 2025Jun 20 by Reset XPDR

3 hours ago, Reset XPDR said:

 

The following feature was introduced in 0.4.5.0:

• Implemented functionality to store the last used graphics mode and automatically set it as the default on the next app launch.

Was it that? If so, that is now normal.

If you want to change the target FPS to another graphics mode than that the app started with before you start a flight session, just use the target FPS type drop down list.

When you start a flight session the current graphics mode will be auto detected and change on the UI if different to what you currently have showing. If you start and exit lossless scaling while in the flight session, it will auto detect within 5 seconds but if you are back at the main menu it will stay with what it last was when you finished your flight unless you manually change it yourself.

Understood, thank-you.

 

Mike 

Has anyone experienced that with 2024 and AutoFPS things become more blurry? I've noticed on a couple of my flights that when I am flying with AUTOFPS the sight distance becomes blurry. Things like the ground textures which are immediately next to the aircraft. This is while having the TLOD set to a high level. Leaving the AUTOFPS off for a session and things are crisper and not blurry around me. Am I crazy or is there something here?

On 6/21/2025 at 6:07 PM, spearmint_flyer said:

Has anyone experienced that with 2024 and AutoFPS things become more blurry? I've noticed on a couple of my flights that when I am flying with AUTOFPS the sight distance becomes blurry. Things like the ground textures which are immediately next to the aircraft. This is while having the TLOD set to a high level. Leaving the AUTOFPS off for a session and things are crisper and not blurry around me. Am I crazy or is there something here?

Yes, the fps per se are wonderful but the image quality are way worse.

There should not be any visual difference between a TLOD value being set in MSFS settiings and being set to the same value by AutoFPS. It is exactly the same MSFS setting being set.

13 minutes ago, Reset XPDR said:

There should not be any visual difference between a TLOD value being set in MSFS settiings and being set to the same value by AutoFPS. It is exactly the same MSFS setting being set.

Yes, I am now using just Dynamic Settings in MSFS and the visual quality is word not allowed. I have a whole thread on it as the visual quality is just abysmal.

There are 200 pages here and all II do in 2024 with my 3060ti is select AMD FSR3 with an LOD of 100.  

What else do I need since the sim looks and performs awesome low and high?

dd

Edited June 24, 2025Jun 24 by Sky_Pilot071