16 hours ago, Reset XPDR said:

I will do that, since I have made it so that the spike protection checkbox only ever appears if you have RTSS running anyway and could do the same for the hide-able stack panel upon which it would live, so users not using RTSS would not see it anyway. It will make it reappear in the first 0.4.3.0 test build.

@kevinfirth , as promised, the first 0.5.3.0 test build is now released and reinstates the spike detection/protection. Note you must have RTSS running, spike protection enabled AND Log+ enabled for this stack panel to show:

Edited July 30Jul 30 by Reset XPDR

On 7/29/2026 at 4:10 PM, Reset XPDR said:

FYI, for users trying the new Dynamic FG option in 0.5.2.0, please note that you should use MSFS, not RTSS, as the FPS source as it provides the NFR FPS required for this mode. RTSS provides post-FG FPS, which will conflict with your NFR-based Target FPS. For now you will have to manually change back to MSFS if you were using RTSS as your FPS source, but only for Dynamic FG specifically. ie:

This should affect very few, if any, users as you would need to be using both RTSS as FPS source and Dynamic FG together. Nonetheless, it will be automatically enforced in 0.5.3.0 when it is released in the future. The online 0.5.2.0 readme has also been updated with this advice.

Further to this, the first 0.5.3.0 test build has been released which automatically enforces MSFS as the FPS source, regardless of whether RTSS is running or not. Also, DynFG now shows on the app status line in lieu of Man FG that was previously shown:

Wow. 300 pages on this topic. An Avsim record?
Great support and interaction.

First of all great app - My rig wasnt horrible but this does seem to make things smoother and most of all I get a little more info when it isnt why. One thing I have noticed with the latest (I use Auto as it seems to be the best for my setup) I seem to switch to "A Fixed FPS" way more then I did with the previous version (when it never did) - not a deal breaker if it does I just reset it usually will go back to FPS Pri which is best for my setup....but I wonder if thats to be expected with the latest version.

5 hours ago, marcg11 said:

First of all great app - My rig wasnt horrible but this does seem to make things smoother and most of all I get a little more info when it isnt why. One thing I have noticed with the latest (I use Auto as it seems to be the best for my setup) I seem to switch to "A Fixed FPS" way more then I did with the previous version (when it never did) - not a deal breaker if it does I just reset it usually will go back to FPS Pri which is best for my setup....but I wonder if thats to be expected with the latest version.

Nothing has changed in recent app versions re auto detecting a fixed FPS in Auto Target FPS mode. In this mode, the app will switch to AFixedFPS if recent FPS history is within a very tight tolerance (FPS must stay within ±1%, and the jitter must be extremely small: only 0.25%.) of the dominant FPS detected, but will only stay that way if it is detected that way 5 times in a row. Your experience is basically saying that at least the first assessment meet this criteria but then doesn't after that.

This can happen with no fixed FPS set but the view stays constant meaning the FPS is not varying much anyway. Unfortunately, there is no way to tell the difference from a detection point of view, other than confirming that it does the same 4 more times as the app already does.

Edit: Just to demonstrate what it takes to get a permanent auto fixed FPS with a real fixed FPS, here's what a run of 5 detections would need to look like:

2026-08-03 08:57:42.759 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 39.8, 39.8, 39.7, 39.8, 39.8, 39.6, 39.8, 39.8, 39.5, 39.8, 39.8, 39.8, 39.8, 39.6, 39.8, 39.8, 39.7, 39.8, 39.8, 39.7 
2026-08-03 08:57:42.759 [DBG] [ LODController:DetectFixedFPS     ] Atmpt:1 DomFPS:40 Tol:±0.50 SD+:0.000 SDMax:0.125 In:20 Out+:0 FixedFPS:Y 
2026-08-03 08:57:42.759 [DBG] [ LODController:DetectFixedFPS     ] Fixed FPS detected at 40 FPS 
2026-08-03 08:57:42.759 [INF] [ LODController:DetectFixedFPS     ] Auto Target Fixed FPS detected at 40 FPS (override applied) 
2026-08-03 08:57:42.759 [DBG] [ LODController:DetectFixedFPS     ] Auto Target Fixed FPS detection 1/5: confirmed consistent at 40 FPS 
2026-08-03 08:58:03.051 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 39.8, 39.8, 39.7, 39.8, 39.8, 39.6, 39.8, 39.8, 39.7, 39.8, 39.8, 39.7, 39.8, 39.8, 39.6, 39.8, 39.7, 39.8, 39.8, 39.7 
2026-08-03 08:58:03.051 [DBG] [ LODController:DetectFixedFPS     ] Atmpt:1 DomFPS:40 Tol:±0.50 SD+:0.000 SDMax:0.125 In:20 Out+:0 FixedFPS:Y 
2026-08-03 08:58:03.051 [DBG] [ LODController:DetectFixedFPS     ] Fixed FPS detected at 40 FPS 
2026-08-03 08:58:03.051 [DBG] [ LODController:DetectFixedFPS     ] Auto Target Fixed FPS detection 2/5: confirmed consistent at 40 FPS 
2026-08-03 08:58:23.343 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 39.8, 39.8, 39.7, 39.8, 39.7, 39.7, 39.8, 39.8, 39.7, 39.8, 39.8, 39.7, 39.8, 39.7, 39.7, 39.8, 39.8, 39.6, 39.8, 39.8 
2026-08-03 08:58:23.343 [DBG] [ LODController:DetectFixedFPS     ] Atmpt:1 DomFPS:40 Tol:±0.50 SD+:0.000 SDMax:0.125 In:20 Out+:0 FixedFPS:Y 
2026-08-03 08:58:23.343 [DBG] [ LODController:DetectFixedFPS     ] Fixed FPS detected at 40 FPS 
2026-08-03 08:58:23.343 [DBG] [ LODController:DetectFixedFPS     ] Auto Target Fixed FPS detection 3/5: confirmed consistent at 40 FPS 
2026-08-03 08:58:43.651 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 39.7, 39.8, 39.7, 39.8, 39.8, 39.7, 39.8, 39.8, 39.7, 39.8, 39.8, 39.7, 39.8, 39.8, 39.6, 39.8, 39.8, 39.7, 39.8, 39.8 
2026-08-03 08:58:43.651 [DBG] [ LODController:DetectFixedFPS     ] Atmpt:1 DomFPS:40 Tol:±0.50 SD+:0.000 SDMax:0.125 In:20 Out+:0 FixedFPS:Y 
2026-08-03 08:58:43.651 [DBG] [ LODController:DetectFixedFPS     ] Fixed FPS detected at 40 FPS 
2026-08-03 08:58:43.651 [DBG] [ LODController:DetectFixedFPS     ] Auto Target Fixed FPS detection 4/5: confirmed consistent at 40 FPS 
2026-08-03 08:59:03.933 [DBG] [ LODController:DetectFixedFPS     ] RawFPS: 39.7, 39.8, 39.8, 39.6, 39.8, 39.6, 39.8, 39.8, 39.7, 39.8, 39.8, 39.7, 39.8, 39.8, 39.7, 39.8, 39.8, 39.7, 39.8, 39.8 
2026-08-03 08:59:03.933 [DBG] [ LODController:DetectFixedFPS     ] Atmpt:1 DomFPS:40 Tol:±0.50 SD+:0.000 SDMax:0.125 In:20 Out+:0 FixedFPS:Y 
2026-08-03 08:59:03.933 [DBG] [ LODController:DetectFixedFPS     ] Fixed FPS detected at 40 FPS 
2026-08-03 08:59:03.933 [INF] [ LODController:DetectFixedFPS     ] Auto Target Fixed FPS confirmed stable after 5 identical detections. 

Edited August 2Aug 2 by Reset XPDR

Something is going on with my system suddenly. The sim is up and my plane is sitting on the runway but autoFPS shows SimConnect and Session in red. I closed autoFPS and opened it again the condition is the same. I also fell back autoFPS to release level and then back to test+ but nothing changed.

Let me add that I tested the health of simconnect by starting Little Navmap and it connected to the simulator with no problem.

Ideas?

Edited August 6Aug 6 by Rob G
Additional info

1 hour ago, Rob G said:

Something is going on with my system suddenly. The sim is up and my plane is sitting on the runway but autoFPS shows SimConnect and Session in red. I closed autoFPS and opened it again the condition is the same. I also fell back autoFPS to release level and then back to test+ but nothing changed.

Let me add that I tested the health of simconnect by starting Little Navmap and it connected to the simulator with no problem.

Ideas?

Did you try everything the readme suggests to try?

If after installing and running the app your simconnect always stays red, your TLOD and OLOD values show as zero or you see "Critical Exception occurred: MSFS_AutoFPS - Unable to load DLL 'GpuzShMem.x64.dll' or one of its dependencies" in the log file:

• Try reinstalling the app with the Repair option selected, then reboot. If any of the redistributables fail to install during this process, try downloading and installing/repairing (as applicable):

  • A Microsoft official version of “Microsoft Visual C++ 2015 - 2022 Redistributable”, which may be missing from your Windows installation. Try installing this and this.

  • The NET desktop runtime from here if still available. Alternatively, go to the Micrsoft .NET 8.0 download page here and download and install the latest .NET Desktop Runtime X64 version.

• 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. Rebooting is also recommended.

  • If that doesn't fix it, a full clean reinstall of MSFS will be required per the explicit instructions in the FAQ entry here.

10 hours ago, Reset XPDR said:

Did you try everything the readme suggests to try?

If after installing and running the app your simconnect always stays red, your TLOD and OLOD values show as zero or you see "Critical Exception occurred: MSFS_AutoFPS - Unable to load DLL 'GpuzShMem.x64.dll' or one of its dependencies" in the log file:

• Try reinstalling the app with the Repair option selected, then reboot. If any of the redistributables fail to install during this process, try downloading and installing/repairing (as applicable):

  • A Microsoft official version of “Microsoft Visual C++ 2015 - 2022 Redistributable”, which may be missing from your Windows installation. Try installing this and this.

  • The NET desktop runtime from here if still available. Alternatively, go to the Micrsoft .NET 8.0 download page here and download and install the latest .NET Desktop Runtime X64 version.

• 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. Rebooting is also recommended.

  • If that doesn't fix it, a full clean reinstall of MSFS will be required per the explicit instructions in the FAQ entry here.

I have just completed every single step you described, including a clean install. but autoFPS is still not connecting. I have a very extensive backup system on my machine so I could just restore my entire system to a few days ago when it was working. But before I do that I thought I would tell you that nothing has worked to see if you have any further input to give me?

Additional info: I got out of the MSFS 2024 Beta and it still won't work. In fact I even restored my system to two days ago with no luck.

As a test I am going to restore my system to like a week ago and see what I end up with. I will report back. This is a very frustrating situation.

Edited August 6Aug 6 by Rob G
Additional info

2 hours ago, Rob G said:

I have just completed every single step you described, including a clean install. but autoFPS is still not connecting. I have a very extensive backup system on my machine so I could just restore my entire system to a few days ago when it was working. But before I do that I thought I would tell you that nothing has worked to see if you have any further input to give me?

Additional info: I got out of the MSFS 2024 Beta and it still won't work. In fact I even restored my system to two days ago with no luck.

As a test I am going to restore my system to like a week ago and see what I end up with. I will report back. This is a very frustrating situation.

Before you do anything too drastic, send me via PM the contents of one of your app logs, located in %appdata%\MSFS_AutoFPS\log, and I will see if I can tell what is going on.

8 hours ago, Reset XPDR said:

Before you do anything too drastic, send me via PM the contents of one of your app logs, located in %appdata%\MSFS_AutoFPS\log, and I will see if I can tell what is going on.

I PM'd you a link to a log file from tonight. It looks like it's some kind of access denial but I don't understand it.

19 hours ago, Rob G said:

I PM'd you a link to a log file from tonight. It looks like it's some kind of access denial but I don't understand it.

FYI for anyone wondering the outcome, it was Steam being unknowingly run as Admin, with MSFS inheriting that same privilege level, that was blocking AutoFPS being able to attach to the MSFS executable. All resolved now.

On 7/29/2026 at 10:19 PM, Reset XPDR said:

The readme FAQ covers this as follows:

ie. Select this:

then this:

I previously ran x3 FG in sim and had General set to Manual / Target: FG / FPS: 120.

I now want to test the new dynamic FG in SU6, but when I follow the screenshot settings it doesn't seem to recognise the native FPS pre-dynamic FG. My screen outputs 165hz and dynamic FG within MSFS SU6 achieves that no problem as the post-FG FPS. However, the native FPS displayed in AutoFPS with the above settings always show ~30, and with a 40 FPS target that keeps TLOD at lowest setting. I haven't found a way yet to see the pre-FG FPS in SU6, but when I turn off FG completely I get around 55-60 FPS native in the exact same situation. So I'm not sure why AutoFPS reads it as ~30 FPS with the above settings.

Am I missing something? Thanks!

1 hour ago, Speedbird193 said:

I previously ran x3 FG in sim and had General set to Manual / Target: FG / FPS: 120.

I now want to test the new dynamic FG in SU6, but when I follow the screenshot settings it doesn't seem to recognise the native FPS pre-dynamic FG. My screen outputs 165hz and dynamic FG within MSFS SU6 achieves that no problem as the post-FG FPS. However, the native FPS displayed in AutoFPS with the above settings always show ~30, and with a 40 FPS target that keeps TLOD at lowest setting. I haven't found a way yet to see the pre-FG FPS in SU6, but when I turn off FG completely I get around 55-60 FPS native in the exact same situation. So I'm not sure why AutoFPS reads it as ~30 FPS with the above settings.

Am I missing something? Thanks!

MSFS always reports pre-FG FPS via the simconnect interface, which the app scales according to the detected or manually set FG mode. All DynFG mode does is not scale that FPS at all, ie. it is the NFR FPS. As such, if you are seeing ~30 FPS then that is the actual NFR that dynamic FG is scaling. The simplest solution is to lower your Target FPS to suit the NFR FPS you are seeing in the app.

I agree though that it is strange that when you turn off FG completely that you see nearly double the supposedly NFR FPS that you see with DynFG, so maybe there is a bug somewhere or it is to do with how you have enabled dynamic FG within MSFS. As I do not have a 5000 series GPU to test this myself, can I get you to PM me the contents of one of your log files, located in %appdata%MSFS_AutoFPS\log, where you have dynamic FG enabled in MSFS settings and have DynFG selected in AutoFPS. Can you also send me the contents of the first section of your UserCfg.opt file, which will show how setting dynamic FG looks in this file, and your MSFS2024_AutoFPS.config file, located in %appdata%MSFS_AutoFPS, and I will take a look. Also, can you tell me, or show me via a screenshot, how dynamic FG is enabled internally in MSFS.

Edit: Oh, and if you are not using one of the 0.5.3.0 test builds, make sure that your FPS source is set to MSFS, not RTSS, in the app as that can cause issues. 0.5.3.0 automatically enforces the use of MSFS as the FPS source. eg FS shown in the first red box is what you should be using:

Edited August 13Aug 13 by Reset XPDR

On a totally unrelated topic: every time I do an update (when auto-launched with the sim) I get a "running as admin" warning - yet I never do run it as such (and my regular shortcut has it disabled). I'm initially launching it via an option in Addons Linker. This is with 0.5.3.0 RC2, but I've had it with earlier versions.

Is there a startup switch/parameter that I could add (that I could use in Linker)?

1 hour ago, Adamski_NZ said:

On a totally unrelated topic: every time I do an update (when auto-launched with the sim) I get a "running as admin" warning - yet I never do run it as such (and my regular shortcut has it disabled). I'm initially launching it via an option in Addons Linker. This is with 0.5.3.0 RC2, but I've had it with earlier versions.

Is there a startup switch/parameter that I could add (that I could use in Linker)?

What do you mean by "running as admin" warning? Do you mean the app shows Admin in the title bar or does it fail the compatibility test and that is the advice it is giving you?

In any case, if you do see Admin in the title bar, the app is indeed running in Admin mode. Even though you may not have configured the app to start in Admin mode, if the parent app calling it is in Admin mode it will automatically inherit that privilege level. Is that what is happening?