Does anybody else find that their settings never recover once they have been reduced? Ever flight I find that if my settings are reduced due (which they generally are due to GPU load on my triple monitor setup), they never recover. It doesn't seem to matter if I have recover set to Alt TOLD Base, Alt TOLD Top or Ground. 

Screenshot here - I've had maintaining 60 FPS for the past 30 minutes but the reduciton hasn't been corrected. Its quite possibly my settings, I've tried several times reading the readme for this app (which is awesome) but i do find it overwhelming confusing. 

If I close and then re-open the app it resumes as it should. 

Edited November 15, 2025Nov 15 by KL Oo

5 minutes ago, KL Oo said:

Does anybody else find that their settings never recover once they have been reduced? Ever flight I find that if my settings are reduced due (which they generally are due to GPU load on my triple monitor setup), they never recover. It doesn't seem to matter if I have recover set to Alt TOLD Base, Alt TOLD Top or Ground. 

Screenshot here - I've had maintaining 60 FPS for the past 30 minutes but the reduciton hasn't been corrected. Its quite possibly my settings, I've tried several times reading the readme for this app (which is awesome) but i do find it overwhelming confusing. 

If I close and then re-open the app it resumes as it should. 

As you say, if your FPS is consistently above your target FPS, and you are not in a critical phase of flight (which you should not be at 21000 ft), then settings reduction recovery should kick in within 60 seconds. 

Message me the contents of your log file associated with when this happened, located in %appdata%\MSFS_AutoFPS\log, and I will look into it.

1 hour ago, Reset XPDR said:

As you say, if your FPS is consistently above your target FPS, and you are not in a critical phase of flight (which you should not be at 21000 ft), then settings reduction recovery should kick in within 60 seconds. 

Message me the contents of your log file associated with when this happened, located in %appdata%\MSFS_AutoFPS\log, and I will look into it.

Thanks mate - message sent 

For anyone wondering the outcome of @KL Oo's issue with settings reduction recovery not working, it was an issue with TLOD Base exceeding TLOD Top, which should never happen, because of the specific (unique) settings being used and was resolved in a recent 0.4.5.9 test version. 0.4.5.9, which also brings a major UI facelift, is nearly ready and should be will be released in the next couple days after I update the Readme with the changes.

I am about to formally release 0.4.5.9 but before I do I want at least one user who has been on the test program and chose Silent Update in RC4 to confirm that the app did indeed silently update to RC5, so that I can be confident it works as advertised before I unleash it on the main user base, planned to be very soon.

Please let me know if anyone has done this. Thanks.

Silent update worked for me....Just opened ver RC4 and it updated to RC5 by itself.

 

2 minutes ago, Chris Boyce said:

Silent update worked for me....Just opened ver RC4 and it updated to RC5 by itself.

 

Excellent. I will now prep for formal release. 

I'm gonna get some test info over to you on the discord discussion today.

I've been absent from the testing for way to long.

3 minutes ago, Chris Boyce said:

I'm gonna get some test info over to you on the discord discussion today.

I've been absent from the testing for way to long.

Well I am about to release, so hopefully not something I need to fix? If so, let me know ASAP.

MSFS_AutoFPS 0.4.5.9 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.

MSFS Compatibility: 1.39.9.0, 1.5.27.0, 1.6.29.0

Release notes for 0.4.5.9

This update delivers major UI refinements with clearer grouping and labeling of TLOD/OLOD settings, replaces Avg Descent Rate in with Alt TLOD Top in FPS Sensitivity and Tolerance modes, removes TLOD Extra from Auto TLOD mode, introduces a new Silent Updates option to update settings, and provides key fixes for settings‑reduction recovery, Non‑Expert mode LOD integrity, and compatibility parsing.

Executive Summary

This release improves LOD clarity, introduces altitude‑based tooltips, strengthens stability across modes, and adds a new update option:

• UI & Terminology Updates: TLOD/OLOD settings regrouped for easier navigation, symbols replaced with descriptive labels, and terminology simplified to distinguish minimums, maximums, and multipliers. Tooltips now show resultant values and recommended IFR/VFR descent rates.
• Functional Changes: Replaced Avg Descent Rate in FPS Sensitivity and Tolerance modes with Alt TLOD Top, Auto TLOD mode no longer supports Extra as it duplicates FPS Cap mode, FPS Cap mode uses a force‑enabled Top Extra multiplier to ensure altitude logic works correctly, and rapid Extra seek logic uses minimum headroom to achieve higher resultant values.
• Silent Updates: Added new option to update settings that installs updates automatically without prompts or release notes and renamed Auto to Prompted Updates. A one‑time migration prompt is provided for Prompted Updates users, and older app versions treat Silent Updates as Prompted Updates for backward compatibility.
• Altitude Defaults: Alt TLOD Top values adjusted to reflect recommended max 2000 fpm descent for IFR and 1350 fpm for VFR, with lower defaults in Sensitivity/Tolerance modes to account for free‑ranging TLOD Max.
• Fixes & Cleanup: Corrected dynamic‑settings behaviour in Non‑Expert mode, resolved TLOD Min/Max conflicts with settings recovery, improved VRAM+ dropdown handling, centralised altitude‑based calculations, expanded logging for reliability and debugging, fixed non‑integer LOD limit failures in Non‑Expert mode, and corrected parsing of MSFS Compatibility lines in release notes.

Does the option to Start Autofps with MSFS work also with 2024?

Thanks

9 minutes ago, 0stones0 said:

Does the option to Start Autofps with MSFS work also with 2024?

Thanks

Yes it does. If you have both MSFS versions, you can choose either or both (default) when you install with that option.

48 minutes ago, Reset XPDR said:

Yes it does. If you have both MSFS versions, you can choose either or both (default) when you install with that option.

During installation I only had option for msfs. Not 2024. I'm guessing it's supposed to  auto opens autofps after starting 2024?

Syntax in EXE file looks correct, best I can tell.

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>ActiveSky utils</Name>
    <Disabled>False</Disabled>
    <Path>C:\Users\Owner\AppData\Roaming\HiFi\AS_FS\AddonFolder\ActiveSkyUtils.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>MSFS_AutoFPS</Name>
    <Path>C:\Users\Owner\AppData\Roaming\MSFS_AutoFPS\bin\MSFS_AutoFPS.exe</Path>
  </Launch.Addon>
</SimBase.Document>

 

 

Edited November 23, 2025Nov 23 by 0stones0
Addded info

1 hour ago, 0stones0 said:

During installation I only had option for msfs. Not 2024. I'm guessing it's supposed to  auto opens autofps after starting 2024?

Syntax in EXE file looks correct, best I can tell.

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>ActiveSky utils</Name>
    <Disabled>False</Disabled>
    <Path>C:\Users\Owner\AppData\Roaming\HiFi\AS_FS\AddonFolder\ActiveSkyUtils.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>MSFS_AutoFPS</Name>
    <Path>C:\Users\Owner\AppData\Roaming\MSFS_AutoFPS\bin\MSFS_AutoFPS.exe</Path>
  </Launch.Addon>
</SimBase.Document>

 

 

If you only have MSFS 2024 installed, the installer will detect that and you will not be presented the selection to choose between MSFS 2020 and/or 2024 as the choice is implicit.

In any case, your EXE.xml file looks correct for MSFS_AutoFPS to start. The simplest way to know for sure is to fire up MSFS 2024, and MSFS_AutoFPS should start up about halfway through the MSFS initial loading process.

10 minutes ago, Reset XPDR said:

If you only have MSFS 2024 installed, the installer will detect that and you will not be presented the selection to choose between MSFS 2020 and/or 2024 as the choice is implicit.

In any case, your EXE.xml file looks correct for MSFS_AutoFPS to start. The simplest way to know for sure is to fire up MSFS 2024, and MSFS_AutoFPS should start up about halfway through the MSFS initial loading process.

Found the issue:

<Descr>Launch</Descr>
<Filename>exe.xml</Filename>

The "exe" file in msfs2024 is all caps. Changed the filename above to EXE and we're good to go.

One other question. Do I still need to run GPUZ when using Dynamic setting in game?

Thanks again.