28 minutes ago, Reset XPDR said:

If you mean because of an Simconnect Exception 31 Detected error when you run AutoFPS immediately after MSFS has updated, then follow the first instruction on the pop up that appears and that should fix it:

1. If MSFS was recently updated, restart MSFS first to allow it to finish rebuilding WASM modules, then restart this app.

If it is something else let me know specifically what it is, otherwise it is working fine on my system after an MSFS 2024 and app restart.

 

Sorry, my bad. I just fired up the sim and got the error message, so thought it broke again. Just tried again after relaunching the sim and it's working - false alarm!

Just tried a flight in MSFS 2020 with lots of weather/clouds and terrain. Apart from a few super long pauses, smooth as butter! Amazing.

7 minutes ago, Speedbird 217 said:

Sorry, my bad. I just fired up the sim and got the error message, so thought it broke again. Just tried again after relaunching the sim and it's working - false alarm!

No worries. This is a new thing since SU4 where it seems to mess up WASM on the first start of MSFS after it has updated. It even does it now if you switch back to SU3, hence the addition of the aforementioned suggestion to try it all again after a restart as the first step.

 

1 hour ago, Speedbird 217 said:

Sorry, my bad. I just fired up the sim and got the error message, so thought it broke again. Just tried again after relaunching the sim and it's working - false alarm!

In fairness to you, and anticipating that others will likely think similar when confronted with such a blunt message, I have revised the app to give a much more user friendly suggestion to restart MSFS to restablish SimConnect communcations after an update if it experiences this error, ie.

If you decide to ignore it and not restart MSFS, only then you will be poked in the eyes with the previous message until you do 😄

(note missing . and space between the first and second sentence under point 2 is noted and will be fixed next version)

MSFS_AutoFPS 0.4.5.6 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 update adds support for MSFS 2024 SU4 beta, introduces hybrid dynamic settings automation in expert mode, enables automatic flight profile switching for VR and sim rate, and delivers a range of UI, installer, config file, logging, and stability improvements.

Executive Summary

SU4 Compatibility
MSFS 2024 beta version 1.6.7.0 is now supported.

Hybrid Dynamic Settings Support
Expert mode now supports coordinated automation between MSFS dynamic settings and AutoFPS, with clear status indicators, tooltips, and instant adjustment controls in test mode. For best results, users should apply an FPS cap or offset the MSFS target frame rate to align with AutoFPS behavior.

Auto Flight Profile Switching
Flight type profiles now auto-switch based on VR mode and sim rate, using suffix-based pairing for seamless transitions. Visual indicators and guardrails clarify active pairings and prevent unintended collisions.

Other Improvements and Fixes
UI responsiveness has been enhanced with dynamic status line scaling and refined layout alignment. Stability, recovery logic, installer behaviour, config file integrity, logging, and memory detection have all been improved, while redundant code paths have been removed for cleaner operation.

Please review the updated readme here, which provides a detailed description of the app, installation, features and settings, before asking any questions or raising any issues about the app.

First of all I’m very sorry but I’m so confused because this is my first time configuring MSFS AutoFPS and testing fenix in Fs2024.

Can anybody help me giving me an optimal msfs autofps configuration optimal values???.

i’d downloaded last version 0.4.5.6 today and those are my pc specs:

AMD Ryzer 9 9950X3D,64 MB RAM,RTX 5080….

Fs2024 (almost high and ULTRA,clouds and textures ULTRA,fauna and live traffic OFF).

Thank you very much for anybody helping me.

2 hours ago, BenzAmg said:

Can anybody help me giving me an optimal msfs autofps configuration optimal values???.

That doesn't exist, it's entirely dependent on one's system. I would read the readme.md to the fullest. You honestly don't tinker if you don't want to.

My only advice to you is, because you have a 9950X3D, you have a split CCD. use something like process laso to ensure MSFS is on a core that is a part of the stacked cache.

2 hours ago, Lucky38i said:

That doesn't exist, it's entirely dependent on one's system. I would read the readme.md to the fullest. You honestly don't tinker if you don't want to.

My only advice to you is, because you have a 9950X3D, you have a split CCD. use something like process laso to ensure MSFS is on a core that is a part of the stacked cache.

Thanks mate!

Sorry if this was already asked. With the new Version and support for Dynamic Settings, I have MSFS_AutoFPS currently configured for FPS Cap with a target FG FPS of 60. In MSFS 2024 Dynamic Settings is enabled and the Max Framerate is also configured to 60. My Monitor support a maximum of 60 Hz. From the readme, I got that this is the optimal config?

5 hours ago, eXpress48 said:

Sorry if this was already asked. With the new Version and support for Dynamic Settings, I have MSFS_AutoFPS currently configured for FPS Cap with a target FG FPS of 60. In MSFS 2024 Dynamic Settings is enabled and the Max Framerate is also configured to 60. My Monitor support a maximum of 60 Hz. From the readme, I got that this is the optimal config?

Not quite. The readme says:

• Works best when using an 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.

The native frame rate equivalent of your target FG FPS of 60 is actually 30, so 30 is what you need to set MSFS 2024 dynamic settings and max frame rate to.

Note, if you are on the SU4 beta, max frame rate is currently a bit broken and sets a max frame rate slightly lower than what you have set, so it you are using max frame rate in SU4 you need to check what it is actually setting and, if wrong, adjust accordingly. See this post for more details. 

Thank for the answer and sorry for the confusion!

14 minutes ago, eXpress48 said:

Thank for the answer and sorry for the confusion!

That's all right. As this is a new feature, I am happy to explain. Users have become used to being able to set actual FG target FPS in AutoFPS, because that then makes sense with what FPS the app is showing, but within MSFS every FPS setting is native frame rate. Of course MS/Asobo don't tell you that it is native frame rate - we have had to work it out for ourselves - which I why native frame rate is explicitly mentioned in the AutoFPS readme.

On 9/9/2025 at 8:44 PM, Reset XPDR said:

Yes, with 0.4.5.6-test installed and following the instructions in the release notes to enable it.

 

It is not a Max, it is a Top and the top is what you get without any TLOD extra, which comes from excess performance. Per the readme, it is possible to see up to double your Top value. So, not an issue rather a pleasant feature.

Thanks again for this amazing tool!

Can you elaborate on this statement above?  I have my TLOD passing my "top" and reaching 400.   During cruise I'm noticing some uneven performance and I'm wondering if it's due to that.   I don't need more than TLOD 200.  Is there a way to stop it from passing the top setpoint?

I notice that on the latest version, whenever I go into MSFS 2024 settings, AutoFPS resets settings to TLOD minimum. Also, even without auto settings reduce activated, autofps is reducing stuff in poor conditions. Is this normal? I don’t seem to remember that happening before. Shouldn’t dynamic settings be taking control of that (when activated)? Also this is anecdotal, but performance seems worse than in the earlier test versions with dynamic settings.

Edited September 23, 2025Sep 23 by agent00729

10 hours ago, KAPtain_Rich said:

Thanks again for this amazing tool!

Can you elaborate on this statement above?  I have my TLOD passing my "top" and reaching 400.   During cruise I'm noticing some uneven performance and I'm wondering if it's due to that.   I don't need more than TLOD 200.  Is there a way to stop it from passing the top setpoint?

You will get uneven performance if you pan your external view rapidly at high TLODs, with or without this app setting it. Quite simply, stop doing that or if you do don't be surprised that there are a few stutters.

In any case, yes you can limit it to 200, by either setting TLOD Top to 100 so that when doubles it goes to 200 max or switch to Auto TLOD auto method and uncheck TLOD Base + in which case it will strictly adhere to TLOD Base and Top.