So running into an issue with latest update. If I start it before the sim launches (main menu) sim won’t load into an airport. If I don’t start auto fps at all, it loads fine into the airport…thoughts?

using 2020

Edited August 1, 2025Aug 1 by Danthepilot77

20 minutes ago, Danthepilot77 said:

So running into an issue with latest update. If I start it before the sim launches (main menu) sim won’t load into an airport. If I don’t start auto fps at all, it loads fine into the airport…thoughts?

using 2020

I have been able to load in fine to MSFS 2020, release or beta version, with the latest app version 0.5.4.3, regardless of whether I start AutoFPS before or after I start the flight. Other than reading a few MSFS settings in memory when AutoFPS first starts, it doesn't actually change any setting until the flight session has gone green, ie. you have clicked past Fly Now. As such, it should not have any impact on the sim loading into an airport right up until that point, so I am not sure what is going on with your setup.

Edited August 1, 2025Aug 1 by Reset XPDR

15 minutes ago, Reset XPDR said:

I have been able to load in fine to MSFS 2020, release or beta version, with the latest app version 0.5.4.3, regardless of whether I start AutoFPS before or after I start the flight. Other than reading a few MSFS settings in memory when AutoFPS first starts, it doesn't actually change any setting until the flight session has gone green, ie. you have clicked past Fly Now. As such, it should not have any impact on the sim loading into an airport right up until that point, so I am not sure what is going on with your setup.

Yeah I don’t know either.

All the sudden this evening, msfs is acting up. I’ll load into an airport fine, I went to several, went to load into another one and it loaded all the way in the blue bar and just stopped and never loaded in.

im not sure what’s going on.

ive used aurofps for quite some time now and never had this issue. I’m not understanding why its loading sometime and not others, never seen this.

Edited August 1, 2025Aug 1 by Danthepilot77

Is there a guide anywhere that tells me what is what with this app?

My system is 12700K / 64GB ram / RTX 4080 - I run at 1440p and a second monitor that's not used for MSFS but background stuff.

I also run GPU-Z - I did read somewhere about auto FPS needing that data to monitor vram usage.

What is AutoFPS telling me here?  Do I need to intervene manually?  Or will AF take care of these "red" values?

(I had just departed payware KGRB - that scenery is extremely tough on vram I've noticed, worse than ini lol) - but then as I came into MSP area, having TLOD of 600 is amazing!

*one other note - I re-enabled TIN because I think this nifty little app is doing a nice job overall.  So thanks to Reset XPNDR!

 

On 7/31/2025 at 2:21 AM, Reset XPDR said:

BTW, while all these MSFS SU3 shenanigans were going on, it looks like the issue identified here has now been resolved:

It turned out to be using FPS sensitivity mode while using a target FPS set to the same value as the system FPS cap, which restricts TLOD changes to reductions only because there is no FPS headroom above. The solution was to switch to FPS Cap mode, where a matching target FPS and system FPS cap is properly catered for.

FPS Cap mode fixed the issue, i've just test it now, thank you.

4 hours ago, ryanbatc said:

Is there a guide anywhere that tells me what is what with this app?

My system is 12700K / 64GB ram / RTX 4080 - I run at 1440p and a second monitor that's not used for MSFS but background stuff.

I also run GPU-Z - I did read somewhere about auto FPS needing that data to monitor vram usage.

What is AutoFPS telling me here?  Do I need to intervene manually?  Or will AF take care of these "red" values?

(I had just departed payware KGRB - that scenery is extremely tough on vram I've noticed, worse than ini lol) - but then as I came into MSP area, having TLOD of 600 is amazing!

*one other note - I re-enabled TIN because I think this nifty little app is doing a nice job overall.  So thanks to Reset XPNDR!

 

 

Not a guide as such (maybe one day), but there is a readme that has a FAQ and a usage section that describes what each setting does in detail here (text format) and here (pdf format).

Your screenshot is telling you that, because of the scenery load and high TLOD being set, your VRAM usage went high enough that AutoFPS commenced settings reduction to bring it down to a point where it is now locked. These setting should auto recover when you move far enough away from the complex scenery. I wouldn't worry too much about the reduction though as you are still getting 88% of the original very high TLOD it set and OLOD is the same proportion.

If this is happening regularly enough and you want to keep using non-expert mode, you should switch to the IFR profile which will give you more conservative TLODs. 

 

 

Is there any kind of documentation about the behaviour of the default dynamic framerate feature?

I'd like to know what that feature does in comparison to fabulous AutoFPS.

Edited August 2, 2025Aug 2 by skylane182

6 minutes ago, skylane182 said:

Is there any kind of documentation about the behaviour of the default dynamic framerate feature?

I'd like to know what that feature does in comparison to fabulous AutoFPS.

Do you think that this the appropriate thread to ask this ?

Just open a new topic and surely people will respond.

My experience : nothing beats AutoFPS

2 hours ago, skylane182 said:

Is there any kind of documentation about the behaviour of the default dynamic framerate feature?

I'd like to know what that feature does in comparison to fabulous AutoFPS.

I haven't found any documentation on MSFS's 2024 dynamic setting, but my own assessment of it from observation is as follows:

• It adjusts both TLOD and OLOD, the former initially then the latter if still significantly under target FPS. AutoFPS adjusts these settings independently, with OLOD changing inversely proportional to altitude by default, and can also change a lot more settings when auto settings reduction and VRAM+ are active.
• It only ever adjusts down to as low as 50% of your currently set TLOD and/or OLOD, whereas AutoFPS in non-expert mode uses the default values as a centre point for adjustments and in expert mode is configurable to whatever range you want, including above the max of 400 settable within the MSFS settings menu.
• It is much quicker than AutoFPS at responding to FPS reductions, due to it having internal access to MSFS performance metrics that AutoFPS does not, which also means it tends to overreact to short term stutters which are quite common now.
• It seems to work off a native frame rate target FPS rather than actual FPS when frame generation is in use, so you need to be mindful of this when using it with FG. ie. You can be achieving 150 FPS with DLSS FG with a target FPS of 100 and it will still reduce OLOD and TLOD to 50%.

19 hours ago, GSalden said:

Do you think that this the appropriate thread to ask this ?

Yes, I thought that. My question was out of technical interest and in no kind against AutoFPS. I thought here might be a lot of people who know a lot about that topic so there might be knowledge about the differences.
Sorry, I did not mean to offend anyone. I've no doubt AutoFPS is better. 

 

17 hours ago, Reset XPDR said:

I haven't found any documentation on MSFS's 2024 dynamic setting, but my own assessment of it from observation is as follows:

• It adjusts both TLOD and OLOD, the former initially then the latter if still significantly under target FPS. AutoFPS adjusts these settings independently, with OLOD changing inversely proportional to altitude by default, and can also change a lot more settings when auto settings reduction and VRAM+ are active.
• It only ever adjusts down to as low as 50% of your currently set TLOD and/or OLOD, whereas AutoFPS in non-expert mode uses the default values as a centre point for adjustments and in expert mode is configurable to whatever range you want, including above the max of 400 settable within the MSFS settings menu.
• It is much quicker than AutoFPS at responding to FPS reductions, due to it having internal access to MSFS performance metrics that AutoFPS does not, which also means it tends to overreact to short term stutters which are quite common now.
• It seems to work off a native frame rate target FPS rather than actual FPS when frame generation is in use, so you need to be mindful of this when using it with FG. ie. You can be achieving 150 FPS with DLSS FG with a target FPS of 100 and it will still reduce OLOD and TLOD to 50%.

Thanks, that was the kind of explanation I was searching for. 

I actually dare to claim that absolute perfection down to the decimal was reached today over sweden from a small place in norway. Frametime like the screenshot on the ground at Gardermoen using Aerosoft scenery and settings are also attached from within the sim. No traffic is enabled. Absolute perfection term is in regards to reach my hardwares absolute max potential since I am running a 2560x1440@60Hz (59.946 exactly measured) monitor with no sync capabilities so the task of reaching this level hasn't been easy when having a 2080Ti and have to use another factor which is nukems dlss-fsr-mod which requires tuning the sim using external software and make them all work with eachother, and add all those factors together that has to be finetuned, I can't really see where I can get more out of it without having to buy a new monitor. One of the most dangerous and bold statements to make as a simmer, but this setup is not the usual one these days (I have found less than I can count fingers on one hand in regards to number of videos close to my setup) and would never done it if I had a monitor with just some form of sync capability besides having to rely on the old vsync and use quite some time to get to a point like this. 

Edited August 3, 2025Aug 3 by Benjamin H

7 hours ago, skylane182 said:

Thanks, that was the kind of explanation I was searching for. 

Since I went to the effort of putting that answer together, I thought I may as well add it to the FAQ section of the readme, mildly edited for readability as follows:

 

Quote

 

How does AutoFPS compare to the in-built Dynamic Setting feature that MS included in MSFS 2024?

• Dynamic Setting adjusts both TLOD and OLOD, the former initially then the latter if still significantly under target FPS. AutoFPS adjusts these settings independently, with OLOD changing inversely proportional to altitude by default, and can also change a lot more settings when auto settings reduction and VRAM+ are active.
• Dynamic Setting only ever adjusts down to as low as 50% of your currently set TLOD and/or OLOD, whereas AutoFPS in non-expert mode uses the default values as a centre point for adjustments and in expert mode is configurable to whatever range you want, including above the max of 400 settable within the MSFS settings menu.
• Dynamic Setting is much quicker than AutoFPS at responding to FPS reductions, due to it having internal access to MSFS performance metrics that AutoFPS does not, which also means it tends to overreact to short term stutters which are quite common now.
• Dynamic Setting seems to work off a native frame rate target FPS rather than actual FPS when frame generation is in use, so you need to be mindful of this when using it with FG. ie. You can be achieving 150 FPS with DLSS FG with a target FPS of 100 and it will still reduce OLOD and TLOD to 50%. AutoFPS accommodates most mainstream FG types and allows an applicable target FPS to be set for each FG type.

 

@Reset XPDR Would it be possible to change the name of Auto FPS in the main window when it opens to not include the version number and to stay the same for each release?  I use OpenKneeboard for VR and I have a tab that I keep a window capture of AutoFPS in so that I can see what it's doing while I am in VR.  Since the name changes with every release OpenKneeboard doesn't recognize the window each time a new version comes out and I have to set up the window capture again for all the profiles of every aircraft I fly.  Just a quality of life improvement I would like that would be helpful.  Maybe the version number can just go on the main UI screen instead of in the window name.

6 hours ago, thetford569 said:

@Reset XPDR Would it be possible to change the name of Auto FPS in the main window when it opens to not include the version number and to stay the same for each release?  I use OpenKneeboard for VR and I have a tab that I keep a window capture of AutoFPS in so that I can see what it's doing while I am in VR.  Since the name changes with every release OpenKneeboard doesn't recognize the window each time a new version comes out and I have to set up the window capture again for all the profiles of every aircraft I fly.  Just a quality of life improvement I would like that would be helpful.  Maybe the version number can just go on the main UI screen instead of in the window name.

You can use a wildcard for the window name when defining the window capture for AutoFPS so that it doesn't care what comes after the initial app name eg.

I just tried it and it works with any AutoFPS version number in the title. As such, there should be no need for me to hide the version number from the app window title (which I find useful when providing support and viewing screenshots).

BTW, I was aware that this tool existed but had not tried it until now. It will actually be very useful for me as I can now test AutoFPS in VR and actually see what it is doing without having to lift my headset off to peer at the 2D screen, so thanks for bringing this app to my attention!

Edited August 4, 2025Aug 4 by Reset XPDR

20 hours ago, Reset XPDR said:

You can use a wildcard for the window name when defining the window capture for AutoFPS so that it doesn't care what comes after the initial app name eg.

I just tried it and it works with any AutoFPS version number in the title. As such, there should be no need for me to hide the version number from the app window title (which I find useful when providing support and viewing screenshots).

BTW, I was aware that this tool existed but had not tried it until now. It will actually be very useful for me as I can now test AutoFPS in VR and actually see what it is doing without having to lift my headset off to peer at the 2D screen, so thanks for bringing this app to my attention!

Glad we could help each other out!  I love OpenKneeboard and my Wacom tablet to write stuff and view pdf checklists!