15 minutes ago, Reset XPDR said:

What auto method, TLOD Base and Top Mins and Auto Setting Reduction settings are you using? If you are using FPS Cap mode (implied by your mention of an FPS cap) and your TLOD Top Min is 200 and you are not using Auto Settings Reduction, then yes TLOD will not go below TLOD Top Min, as the settings name implies. If your setting are something else, please let me know in more detail so I can try and reproduce.

Okay, well that would explain things.  Yes, I was using FPS Cap mode without Auto Reduction enabled.  

I'm capping frame rate to 38 in sim, (for half VR refresh rate).  I'll give Auto TLOD mode a try and see how that works out for me.  

1 hour ago, FakeWayne said:

Okay, well that would explain things.  Yes, I was using FPS Cap mode without Auto Reduction enabled.  

I'm capping frame rate to 38 in sim, (for half VR refresh rate).  I'll give Auto TLOD mode a try and see how that works out for me.  

You should still use FPS Cap mode, as it is more flexible than Auto TLOD when using an FPS cap, but just set TLOD Top Min lower to something like 100 and set its Extra multiplier to whatever you would like it to go up to when performance is good.

If you were previously using TLOD Top Min 200 and X2 Extra, that gives a range of 200 to 400 above Alt TLOD Top. If you want a similar max but lower min, then try setting TLOD Top Min to 100 and X4 Extra, which will give you 100 to 400. Note your TLOD Base Min times its multiplier will have to be lower than 100 for the logic to function correctly (the app won't let you set it higher in any case), so I suggest you try TLOD Base Min 50 and X2 for its multiplier. Also make sure Alt TLOD Top gives you a reasonable FPM equivalent for transition between Top and Base. The tooltips over the Extra multipliers will tell you what the maxs will be and over Alt TLOD Top will show you what the recommended Alt TLOD Top should be for the recommended FPM descent.

Here's a screenshot of the settings I suggest from what you are telling me, which will give you a total TLOD range of 50 minimum on the ground and up to as high as 400 in the air:

Edited December 9, 2025Dec 9 by Reset XPDR

3 hours ago, Reset XPDR said:

I am not sure what you mean by this. Please elaborate.

Let's say my wide open rate at the moment is 115FPS-frame gen.  Can AutoFPS sense this as 115, then lock the rate at say 105?  And of course this is a case of constant real-time fluctuation.  I ask because I have performance maximally free of micro stutters, what very few remain, when frames are locked, the higher the better, but with some significant headroom over the lock to accommodate transient spikes in demand.  Adding dynamic change though might negatively impact that so might not work.

2 hours ago, Noel said:

Let's say my wide open rate at the moment is 115FPS-frame gen.  Can AutoFPS sense this as 115, then lock the rate at say 105?  And of course this is a case of constant real-time fluctuation.  I ask because I have performance maximally free of micro stutters, what very few remain, when frames are locked, the higher the better, but with some significant headroom over the lock to accommodate transient spikes in demand.  Adding dynamic change though might negatively impact that so might not work.

I think what you are asking for is what Auto Target FPS already does, namely it monitors the average FPS and then sets your target FPS slightly lower than this (5% for IFR, 10% for VFR, plus another 10% if above 3000 ft) for a bit of headroom. It only does this initially when the flight session starts and where you are stopped again somewhere else.

If Auto Target FPS kept changing dynamically as you fly, you would always end up with excess FPS and hence TLOD would always be maxed out, so other than having TLOD Base Min on the ground and up to Alt TLOD Base, you would get TLOD Base Max everywhere else in which case you have bypassed most of the automation that AutoFPS is capable of.

If you really do want a fixed TLOD profile with at least some range of automation between the two extremes, use Auto TLOD where it will be TLOD Base Min on the ground and up to Alt TLOD Base, TLOD Top Max above Alt TLOD Top, and proportionally scaled in between those two altitude thresholds.

Edit: I just reread your scenerio and have another suggestion. If your free range FPS is normally 115 and you are confident your system can achieve 105 FPS pretty much all the time, including the worst-case performance conditions, then I recommend that you set max frame rate in MSFS to 50, which is the native FPS of 100 FPS with 2X FG, then use FPS Cap mode in AutoFPS with a target FG FPS set to 100. This mode is specifically designed to work with a matching FPS cap and will give you FPS Sensitivity mode like results. Having an FPS cap set in MSFS also tends to minimise stutters as the sim knows what it is targeting internally and can manage performance headroom much better than AutoFPS can because it knows exactly what the headroom actually is. I suggest you give this a try first.

Edited December 10, 2025Dec 10 by Reset XPDR

4 hours ago, Reset XPDR said:

You should still use FPS Cap mode, as it is more flexible than Auto TLOD when using an FPS cap, but just set TLOD Top Min lower to something like 100 and set its Extra multiplier to whatever you would like it to go up to when performance is good.

If you were previously using TLOD Top Min 200 and X2 Extra, that gives a range of 200 to 400 above Alt TLOD Top. If you want a similar max but lower min, then try setting TLOD Top Min to 100 and X4 Extra, which will give you 100 to 400. Note your TLOD Base Min times its multiplier will have to be lower than 100 for the logic to function correctly (the app won't let you set it higher in any case), so I suggest you try TLOD Base Min 50 and X2 for its multiplier. Also make sure Alt TLOD Top gives you a reasonable FPM equivalent for transition between Top and Base. The tooltips over the Extra multipliers will tell you what the maxs will be and over Alt TLOD Top will show you what the recommended Alt TLOD Top should be for the recommended FPM descent.

Here's a screenshot of the settings I suggest from what you are telling me, which will give you a total TLOD range of 50 minimum on the ground and up to as high as 400 in the air:

 

You are awesome!...Thank you so much for the help!  NOW everything is working great!  

So for some reason the latest auto fps version changes my clouds setting to medium when I don’t have “decrease cloud setting option” checked. Even on ultra which is my sim setting, doesn’t effect fps hardly any and I still achieve my fps.

Using 2020.

Any idea why this is??

After SU4 I'm getting wasm module error exception 31. any ideas?

Oh, I got another error previously about WASM not having started fully or something.
Either way, AUTO FPS is broken for me at the moment.

Edited December 12, 2025Dec 12 by FreedFlyer97231

1 hour ago, Danthepilot77 said:

So for some reason the latest auto fps version changes my clouds setting to medium when I don’t have “decrease cloud setting option” checked. Even on ultra which is my sim setting, doesn’t effect fps hardly any and I still achieve my fps.

Using 2020.

Any idea why this is??

No, it should not do that. Which specific app version?

Edit: I just tried it in the latest 0.4.5.11 release and clouds stay set to default (Ultra in this case) with Decrease Cloud Quality unchecked, even with FPS way below target.

 

If you are not on 0.4.5.11, udpate to that. If you are and this is still an issue, direct message me the contents (you can't attach files here) of your latest log file, located in %appdata%/MSFS_AutoFPS/log, and I will take a look.

Edited December 12, 2025Dec 12 by Reset XPDR

18 minutes ago, FreedFlyer97231 said:

After SU4 I'm getting wasm module error exception 31. any ideas?

Oh, I got another error previously about WASM not having started fully or something.
Either way, AUTO FPS is broken for me at the moment.

From the Readme:

• If still not resolved and the error code in your AutoFPS log file is Exception 31, you most likely have a corrupt MSFS WASM installation.
  • First, try deleting the MSFS WASM folder, located under the Microsoft Flight Simulator directory in either %appdata% or %localappdata% for Steam and MS Store install directories respectively, which will rebuild when you next run MSFS.
  • If that doesn't fix it, a full clean reinstall of MSFS will be required, which can be done in less than 15 minutes for MSFS 2024 but may take many hours for MSFS 2020.
    • If reinstalling MSFS 2024, you need to do a CLEAN install, not just an uninstall/reinstall as doing the latter does not remove the likely-offending MSFS appdata folder and hence will not resolve the issue.
      • Backup or relocate your Community folder before proceeding, and restore it after reinstallation is complete.
      • Follow the CLEAN install instructions outlined for your MSFS version here EXPLICITLY. Do NOT skip the step where you manually delete the MSFS install in your user folder.
      • All your settings, controller assignments, career progression and your pilot profile are retained.
      • If you chose not to restore your Community folder, you will need to install this app again to install the required mobiflight module there.

MSFS_AutoFPS 0.4.5.12 has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase.

This release improves MSFS/AutoFPS settings mismatch handling, Silent Update behaviour, Auto Settings Reduction, and Additional Cloud Quality, while enhancing UI consistency, logging clarity, and overall code reliability.

On 12/10/2025 at 1:27 AM, Reset XPDR said:

I think what you are asking for is what Auto Target FPS already does, namely it monitors the average FPS and then sets your target FPS slightly lower than this (5% for IFR, 10% for VFR, plus another 10% if above 3000 ft) for a bit of headroom. It only does this initially when the flight session starts and where you are stopped again somewhere else.

If Auto Target FPS kept changing dynamically as you fly, you would always end up with excess FPS and hence TLOD would always be maxed out, so other than having TLOD Base Min on the ground and up to Alt TLOD Base, you would get TLOD Base Max everywhere else in which case you have bypassed most of the automation that AutoFPS is capable of.

If you really do want a fixed TLOD profile with at least some range of automation between the two extremes, use Auto TLOD where it will be TLOD Base Min on the ground and up to Alt TLOD Base, TLOD Top Max above Alt TLOD Top, and proportionally scaled in between those two altitude thresholds.

Edit: I just reread your scenerio and have another suggestion. If your free range FPS is normally 115 and you are confident your system can achieve 105 FPS pretty much all the time, including the worst-case performance conditions, then I recommend that you set max frame rate in MSFS to 50, which is the native FPS of 100 FPS with 2X FG, then use FPS Cap mode in AutoFPS with a target FG FPS set to 100. This mode is specifically designed to work with a matching FPS cap and will give you FPS Sensitivity mode like results. Having an FPS cap set in MSFS also tends to minimise stutters as the sim knows what it is targeting internally and can manage performance headroom much better than AutoFPS can because it knows exactly what the headroom actually is. I suggest you give this a try first.

Oof... reinstall the sim... I dont really want to do that. I just set this all up fresh a couple months ago.

But if it was a WASM/simconnect issue, I'd expect other add-ons that use WASM to also not function, yet they do. Maybe consecutive sim updates will fix the issue.

Edited December 13, 2025Dec 13 by FreedFlyer97231

15 minutes ago, FreedFlyer97231 said:

Oof... reinstall the sim... I dont really want to do that. I just set this all up fresh a couple months ago.

But if it was a WASM issue, I'd expect other add-ons that use WASM to also not function, yet they do. Maybe consecutive sim updates will fix the issue.

Unfortunately, I have never experienced it nor am I able to reproduce it, so I am at a loss as to what to recommend other than reinstalling the sim, which has worked for everyone who has had the issue and, usually begrudgingly beforehand like you, done it. I really wish it was otherwise, but this issue has been elusive since the days of MSFS 2020 only and I would love to find a less nuclear option to resolve.

Fortunately, MSFS 2024 is relatively quick to clean remove and reinstall. You can be back up and running as you were beforehand within 15 minutes, as long as you follow the specific instructions provided.

BTW, in my experience with helping others with this, those WASM issues left unresolved end up having impacts on other MSFS apps and addons that use them, so consider AutoFPS the canary in the coalmine for such potential future issues.

In short, the medicine is not as bad as it seems and usually fixes other MSFS issues lurking under the surface.

Edited December 13, 2025Dec 13 by Reset XPDR

6 hours ago, Reset XPDR said:

Unfortunately, I have never experienced it nor am I able to reproduce it, so I am at a loss as to what to recommend other than reinstalling the sim, which has worked for everyone who has had the issue and, usually begrudgingly beforehand like you, done it. I really wish it was otherwise, but this issue has been elusive since the days of MSFS 2020 only and I would love to find a less nuclear option to resolve.

Fortunately, MSFS 2024 is relatively quick to clean remove and reinstall. You can be back up and running as you were beforehand within 15 minutes, as long as you follow the specific instructions provided.

BTW, in my experience with helping others with this, those WASM issues left unresolved end up having impacts on other MSFS apps and addons that use them, so consider AutoFPS the canary in the coalmine for such potential future issues.

 

Hey, quick update... it's working again. (?)

Not sure if this is due to the recent update, or... I'm using this flight recorder called Flight Echo; it probably also connects to simconnect in order to record various states of the FenixSim add-ons. I usually start this before the sim (otherwise I forget), and naturally AutoFPS starts with FSUIPC automatically. I wonder if FlightEcho is somehow interfering. 

Since I know it's working, I'll do some playing around in the next week.

Edited December 13, 2025Dec 13 by FreedFlyer97231

6 hours ago, FreedFlyer97231 said:

Hey, quick update... it's working again. (?)

Not sure if this is due to the recent update, or... I'm using this flight recorder called Flight Echo; it probably also connects to simconnect in order to record various states of the FenixSim add-ons. I usually start this before the sim (otherwise I forget), and naturally AutoFPS starts with FSUIPC automatically. I wonder if FlightEcho is somehow interfering. 

Since I know it's working, I'll do some playing around in the next week.

Well that's good news, although why it would do it for one sim version and not another with the same startup sequence escapes me. Let me know if changing startup sequence triggers the issue and is repeatable.

Wow, the initial uptake on this latest update has been very high - over 6000 in two days, which is about twice the normal rate! Either the older versions were that bad that anything newer was worth the risk 😆or a lot of users have chosen silent updates and are being stealth updated, although now you get the release notes pop up so that you know it has updated.

Edited December 15, 2025Dec 15 by Reset XPDR