Question about this add-on. First, really awesome effort Reset to get this to the community. Second, here is my question. What if my goal is not to turn up the eye candy as much as I want to maintain a max FPS? For example, running your app last night I had TLOD of 300, everything looked great, but heat was becoming an issue and eventually I had some instability in the sim. I guess I am looking for a way to set the max I want whatever parameters the app is looking at, so I get smooth performance in situations where it might be under load, but when the system isn't loaded (say during cruise) I don't want the app trying to max my settings out. Maybe this is already there, but I figured I would ask to make sure I understand it. 

2 hours ago, Baber20 said:

I am using framegen. I have capped the fps using RTSS at 40. Since FG disables the option to set in game fps cap. I have set the target fps in autofps app to 40 and option selected to 'FR'. Is this ok ? Or do i need to select a different option in autofps app? 

FG should not disable the option to set MSFS Max Frame Rate. 

You quoted discussion of Dynamic Settings yet don't mention it. Can you please clarify whether you are trying to get Dynamic Settings working with AutoFPS or you are just trying to set up AutoFPS with FG?

31 minutes ago, RobJC said:

Question about this add-on. First, really awesome effort Reset to get this to the community. Second, here is my question. What if my goal is not to turn up the eye candy as much as I want to maintain a max FPS? For example, running your app last night I had TLOD of 300, everything looked great, but heat was becoming an issue and eventually I had some instability in the sim. I guess I am looking for a way to set the max I want whatever parameters the app is looking at, so I get smooth performance in situations where it might be under load, but when the system isn't loaded (say during cruise) I don't want the app trying to max my settings out. Maybe this is already there, but I figured I would ask to make sure I understand it. 

Try setting a lower TLOD Top.

3 hours ago, Reset XPDR said:

Try setting a lower TLOD Top.

Is that the only setting that is dynamically controlled by your app?

6 minutes ago, RobJC said:

Is that the only setting that is dynamically controlled by your app?

That depends on what your settings are. What are they?

See here for a top level summary.

Edited March 26Mar 26 by Reset XPDR

1 minute ago, Reset XPDR said:

That depends on what your settings are. What are they?

I went with the defaults and set the FG setting to 36, which matches my settings in sim. I didn’t touch anything else. I just started using it, so let me take a deeper dive. Thanks for the quick reply. 

20 minutes ago, RobJC said:

I went with the defaults and set the FG setting to 36, which matches my settings in sim. I didn’t touch anything else. I just started using it, so let me take a deeper dive. Thanks for the quick reply. 

No worries. It sounds like you may be using non-Expert mode, which should take care of most settings for you. If you find your TLOD gets too high in this mode, change your default TLOD to a lower value in MSFS when not in a flight session because non-Expert mode generally gives you half of that setting on the ground and double it in the air.

2 hours ago, Reset XPDR said:

No worries. It sounds like you may be using non-Expert mode, which should take care of most settings for you. If you find your TLOD gets too high in this mode, change your default TLOD to a lower value in MSFS when not in a flight session because non-Expert mode generally gives you half of that setting on the ground and double it in the air.

Thanks Reset! I will give that a shot. 

10 hours ago, Reset XPDR said:

You must be in Expert mode, as being in Non-Expert mode will automatically disable Dynamic Settings for the duration of your flight session. Also, from the readme:
 

• Works best when using MSFS-set FPS cap, with Max and Dynamic Settings Target Frame Rates in MSFS settings set to the native frame rate equivalent of the AutoFPS target FPS, and the FPS Cap automation mode in AutoFPS.
• If not using an FPS cap, it is recommended to set the MSFS dynamic settings target frame rate to at least 10 FPS lower than the native frame rate equivalent of the AutoFPS target FPS for best results.

 

Thank you for the explanation, that’s exactly how I have it set up. MSFS is capped at 30 FPS, with both AutoFPS and Dynamic LOD targeting 25 FPS. The sim is running smoothly now 🙂

On 3/24/2026 at 8:59 PM, Reset XPDR said:

I have not implemented this before because it could easily result in FPS remaining way below target at the start of a flight on the ground, which is where most users commence flights from, at a complex airport until TLOD dropped low enough to achieve it, which would make for unhappy users. Also, MSFS already has something similar to this with Dynamic Settings where it will give you your set LODs unless FPS is below target, in which case it will reduce them up to 50% and pretty much instantly, so there is really no need for AutoFPS to duplicate this. If you haven't tried Dynamic Settings yet for this particular scenario, I suggest you do so.

 

my approach is to get 40fps (spacewarp in vr brings it to 80) at 90% of situations (including at start of flight on ground), which i have with my upper desired tlod of 165, but was hoping autofps could step in when things get extra heavy (built up cities seems to be where its needed). I forgot to mention i'm on msfs2020 so no dynamic settings. 
hence the desire for an option for autoFPS to start from max (i.e. TLOD Base Min x Extra mult, or from my configured setting in MSFS gfx settings), and decrease if needed after the settle time (i.e. start high and reduce if needed, rather than start low and increase if possible.)

anyways i don't mean to nag, just thought i'd explain further as i figured it would be a fairly common approach to configuring settings so might be something others would find useful

11 hours ago, cjk28 said:

my approach is to get 40fps (spacewarp in vr brings it to 80) at 90% of situations (including at start of flight on ground), which i have with my upper desired tlod of 165, but was hoping autofps could step in when things get extra heavy (built up cities seems to be where its needed). I forgot to mention i'm on msfs2020 so no dynamic settings. 
hence the desire for an option for autoFPS to start from max (i.e. TLOD Base Min x Extra mult, or from my configured setting in MSFS gfx settings), and decrease if needed after the settle time (i.e. start high and reduce if needed, rather than start low and increase if possible.)

With an effective FPS cap situation like yours, you should be using FPS Cap mode, not FPS Sensitivity mode, with target FPS set to 40 and it would start you out with a higher TLOD in the air, but not necessarily as high as you would like.

12 hours ago, cjk28 said:

anyways i don't mean to nag, just thought i'd explain further as i figured it would be a fairly common approach to configuring settings so might be something others would find useful

There have been a few features suggested in the past that I initially did not see the merit of, that ended up being pretty useful (eg. Auto VR profile switching that I now use all the time), so I am currently looking into this one given that it may be useful to more users than just you. 

I already have a working prototype but I just have to make sure it doesn't break anything else, as tends to happen with changes to complex software, before putting it out for you, and possibly others, to test. eg. here's what it does immediately after connecting to a flight session.

 

 

 

@cjk28, 0.4.6.7-RC4 or later, available here, fully implements the Start Max feature previously discussed. The release notes describes what it does:

RC4:
- Added Start Max feature to all automation modes supporting TLOD Extra. Defaults to disabled. When enabled:
  - Starts with maximum TLOD Extra instead of beginning at minimum and ramping upward.
  - Replaces the initial 30-second FPS timer with a normal settle event, reducing startup settle time at the cost of potentially incomplete initial stabilisation.
  - Due to the aggressive behaviour, initial performance may be sub-optimal and the final achievable TLOD Extra may be lower than when the feature is disabled.
- Adjusted Expert Options panel position in Test Mode so it moves down correctly when a dual‑line status message is displayed.

Please give it a go and let me know how it goes. If anyone else tries it, let me know what you think too.

wow thanks so much, seems to work nicely! currently have set tlod base alt to 10ft as i dont really want to couple tlod to altitude, bit of a bodge but seems to work. i'll spend some more time comparing fps cap vs fps sensitivity, the latter seems to be working fine though... one thing i found trying fps cap mode, i can easily get the app to crash and require config delete to fix as follows:
fresh config
click expert
user 1
select fps cap
base min 42
base extra 4x
top extra 1.5x -crash

10 hours ago, cjk28 said:

wow thanks so much, seems to work nicely! currently have set tlod base alt to 10ft as i dont really want to couple tlod to altitude, bit of a bodge but seems to work. i'll spend some more time comparing fps cap vs fps sensitivity, the latter seems to be working fine though... one thing i found trying fps cap mode, i can easily get the app to crash and require config delete to fix as follows:
fresh config
click expert
user 1
select fps cap
base min 42
base extra 4x
top extra 1.5x -crash

I am glad you like it. In fact, I have been using Start Max for most of my recent flights where I have had a lot of performance headroom and I actually quite like it. It is quick and only causes a minor performance drop sometimes, but for less than 10 seconds. I may even enhance it in the next version of the app to give a mid point setting too.

Re the crash, yes I can reproduce it too. I will fix in the next update, and also remove that message about hybrid Dynamic Settings while I am there as it is no longer a new feature.

Edit: This crash has now been fixed in 0.4.6.7-RC5 or later, available here.

Edited March 31Mar 31 by Reset XPDR

@Reset XPDR I'm loving AutoFPS but I do have a quick question. One thing I've noticed is occasionally I'll see my fps in AutoFPS showing 150+ fps at times which is incorrect since I have my fps locked at 115. I went to go turn on debug to see the in game fps and as soon as I did that, AutoFPS began reflecting the correct FPS and never went beyond the 115 cap. Any ideas why this is happening? Thanks!