TLDR: I am working on tools that let the app detect and understand MSFS memory map changes on its own, and the long term goal is for the app to automatically fix these changes without needing me to release a compatibility update.

A quick update on what I am currently working on. As most users of this app know, it already survives MSFS updates as long as the settings memory map has not changed. When the memory map does change, compatibility breaks and you need to wait for me to patch it up again. This is not a great experience for you and it is not much fun for me either.

You may have noticed in the latest 0.4.6.5 test13 release notes that I have been developing a dev only tool that helps me identify what changes in MSFS updates that involve memory map shifts. This now lets me do the entire compatibility fix workflow inside the app itself instead of relying on external tools like Cheat Engine, which I have only ever used out of necessity.

The next logical step is this. If the app can already detect the changes in dev mode and I can manually update the offsets based on that information, then the app could eventually automate the whole process. It could write the new offsets to the config file and load them on startup without needing my intervention at all.

This would most likely apply only to MSFS 2024. MSFS 2020 has not changed its memory map in more than two years and probably will not again. The dev tool I have been building is tuned specifically to MSFS 2024, so bringing MSFS 2020 into the same automated system would be a lot of work for very little real benefit.

It is still early days and this approach may yet fall flat on its face, but the long term goal is an app that is robust and smart enough to adapt automatically to whatever MSFS updates come our way in future. You will see progressive steps toward this in upcoming test releases.

Phase 1 is now working. It detects when the VR offset has shifted a little, which usually happens when a new 2D setting is added and everything after it moves up in memory. The app can now spot that shift and correct it automatically as an experimental feature, possibly in the next test build I will release.

Phase 2 is about finding where the new setting has split the 2D memory map. This part is trickier because many of the values can look the same when using default profiles and they sit right next to each other. For example, the default High profile sets most things to High, so if the new setting also defaults to High it is not obvious where it slipped in. Even so, the split that happened in SU5 Beta 1 was easy to detect, so it should be possible to auto-fix the more obvious cases.

Even without Phase 2, Phase 1 is enough to pass the primary compatibility test and get the app running. If the secondary test fails, which is what Phase 2 will eventually handle, it only means auto settings reduction is disabled. Everything else still works.

Phase 3 is the manual QA step where I check that each MSFS setting lines up with the offset the app thinks belongs to it. This part cannot be automated, so I will still need to do it after each update. The improvement is that Phases 1 and 2 should keep everyone going until I get to Phase 3, whereas before the app stayed disabled until I had done all of it.

Edited February 17Feb 17 by Reset XPDR

0.4.6.5-test14 is now available and includes the new experimental Phase 1 and Phase 2 auto correction system for MSFS compatibility failures after a new SU release. If this had been in place before SU5 Beta 1 it would have fixed compatibility on its own, so I am pretty happy with how it is performing. It is now set up for the release of SU5 Beta 2 and it will be interesting to see whether it can handle that update automatically as well.

If it does, I will likely promote the feature from experimental to mainstream. In practice, a compatibility fail will not resolve itself without this system, and the worst thing that can happen if it cannot fix a future SU change is the same compatibility fail you would have seen anyway. In other words there is nothing to lose.
If you want to try the experimental mode, the release notes explain how to enable it. Just keep in mind that you will not see anything happen until SU5 Beta 2 arrives and, even then, it could work without needing auto-fix, just to spite me. 😆

 

I originally had two monitors and moved Auto_FPS to my second monitor. Now, I only have one monitor and I cannot see AutoFPS on my only monitor. I think AutoFPS is on my "second monitor", which is no longer there. If true, how can I setup AutoFPS to show on my first monitor?

7 minutes ago, flyblueskies said:

I originally had two monitors and moved Auto_FPS to my second monitor. Now, I only have one monitor and I cannot see AutoFPS on my only monitor. I think AutoFPS is on my "second monitor", which is no longer there. If true, how can I setup AutoFPS to show on my first monitor?

I recently had a similar issue with a different app after I changed monitors.

Since you don't need MSFS open, just open Auto FPS manually. You should see the app icon appear on the taskbar. If there's no sign of the app window on the screen, hover over its icon in the taskbar until the app window thumbnail appears above it. Then right-click over that thumbnail and select Maximize or Move.

Maximize worked for me, and then I just resized the window manually. Since Auto FPS doesn't have a changeable window size, you may have to use Move and the use the left/right arrow keys until in comes into view.

Good luck!

7 hours ago, flyblueskies said:

I originally had two monitors and moved Auto_FPS to my second monitor. Now, I only have one monitor and I cannot see AutoFPS on my only monitor. I think AutoFPS is on my "second monitor", which is no longer there. If true, how can I setup AutoFPS to show on my first monitor?

Further to @mmcmah's suggestions, the app does have the ability to auto-reset window position if you restart the app within 15 seconds of closing it.

Just start AutoFPS, right click on the app icon on the taskbar, and select Close Window. Normally, you would be visually presented with the close dialog box, which you would click yes, but since you can't see it just hit Enter and the app will close. Immediately restart AutoFPS and your app window should be back at position 100,100 on your primary monitor.

4 minutes ago, Reset XPDR said:

Further to @mmcmah's suggestions, the app does have the ability to auto-reset window position if you restart the app within 15 seconds of closing it.

Just start AutoFPS, right click on the app icon on the taskbar, and select Close Window. Normally, you would be visually presented with the close dialog box, which you would click yes, but since you can't see it just hit Enter and the app will close. Immediately restart AutoFPS and your app window should be back at position 100,100 on your primary monitor.

Genius!

Why do I get blinking /lightning effect in AutoFPS ( MSFS_AutoFPS v0.4.6.4)?

 

Edited February 21Feb 21 by airbusa333

9 hours ago, airbusa333 said:

Why do I get blinking /lightning effect in AutoFPS ( MSFS_AutoFPS v0.4.6.4)?

 

PM me the contents of your log file, located in %appdata%\MSFS_AutoFPS\log, where this happens and provide me a lot more detail on what the actual issue is, which is not at all obvious from what you have posted.

On 2/19/2026 at 9:23 PM, Reset XPDR said:

0.4.6.5-test14 is now available and includes the new experimental Phase 1 and Phase 2 auto correction system for MSFS compatibility failures after a new SU release. If this had been in place before SU5 Beta 1 it would have fixed compatibility on its own, so I am pretty happy with how it is performing. It is now set up for the release of SU5 Beta 2 and it will be interesting to see whether it can handle that update automatically as well.

If it does, I will likely promote the feature from experimental to mainstream. In practice, a compatibility fail will not resolve itself without this system, and the worst thing that can happen if it cannot fix a future SU change is the same compatibility fail you would have seen anyway. In other words there is nothing to lose.
If you want to try the experimental mode, the release notes explain how to enable it. Just keep in mind that you will not see anything happen until SU5 Beta 2 arrives and, even then, it could work without needing auto-fix, just to spite me. 😆

A quick update on the new auto correction system for MSFS compatibility failures after a new SU release. Due to the success it has demonstrated so far, It has now been promoted from requiring experimental mode to be enabled to working with any test version from now on, meaning that it will work without user intervention for 0.4.6.5-test16 or later.

Also, my prediction about SU5 Beta 2 probably not needing Phase 1 auto correction turned out to be true, just to spite me. 😄 All it needed was a normal offset update, which the app has been able to do for a long time. Nonetheless, the test versions of the app are now poised for any potential shape shifting offset shenanigans that future SU betas may throw at us. I am now updating DynamicLOD_ResetEdition to be able to do the same.

On 2/21/2026 at 8:57 PM, Reset XPDR said:

A quick update on the new auto correction system for MSFS compatibility failures after a new SU release. Due to the success it has demonstrated so far, It has now been promoted from requiring experimental mode to be enabled to working with any test version from now on, meaning that it will work without user intervention for 0.4.6.5-test16 or later.

Also, my prediction about SU5 Beta 2 probably not needing Phase 1 auto correction turned out to be true, just to spite me. 😄 All it needed was a normal offset update, which the app has been able to do for a long time. Nonetheless, the test versions of the app are now poised for any potential shape shifting offset shenanigans that future SU betas may throw at us. I am now updating DynamicLOD_ResetEdition to be able to do the same.

I recently installed SU4 and I'd like to test AutoFPS. Which stable version do you recommend that I try?

I've been testing the default msfs 2024 Dynamic setting @30 fps and I'm pleasantly surprised that it's doing a good job keeping the sim smooth. I just don't like that I get some loading scenery when panning. It's brief loading, but noticeable.

For msfs 2020, your ap has always been indispensable.

Thank you!!!

Jose

18 minutes ago, CFIJose said:

I recently installed SU4 and I'd like to test AutoFPS. Which stable version do you recommend that I try?

I've been testing the default msfs 2024 Dynamic setting @30 fps and I'm pleasantly surprised that it's doing a good job keeping the sim smooth. I just don't like that I get some loading scenery when panning. It's brief loading, but noticeable.

For msfs 2020, your ap has always been indispensable.

Thank you!!!

Jose

Hi Jose that loading scenery when panning (in my case just in complex airports) or like some other users call it stutters while panning is what I would like to fix primarily. Dynamic settings may mitigate this issue but very little. Until now I stayed away from AutoFPS but would be great to read more experiences from other users if they were able to fix this issue with AutoFPS. I don't know if SU5 will fix that.

9 minutes ago, alexcolka said:

Hi Jose that loading scenery when panning (in my case just in complex airports) or like some other users call it stutters while panning is what I would like to fix primarily. Dynamic settings may mitigate this issue but very little. Until now I stayed away from AutoFPS but would be great to read more experiences from other users if they were able to fix this issue with AutoFPS. I don't know if SU5 will fix that.

With AutoFPS, I never had any panning issues. It only happens without it when using the dynamic setting found in msfs 2024.

11 minutes ago, CFIJose said:

With AutoFPS, I never had any panning issues. It only happens without it when using the dynamic setting found in msfs 2024.

This sounds great to me, I will try AutoFPS when able, thanks for telling me.

6 hours ago, alexcolka said:

This sounds great to me, I will try AutoFPS when able, thanks for telling me.

Just add to these already helpful replies, AutoFPS is also capable of working with Dynamic Settings enabled when in Expert mode. As long as you follow the guidance I have provided in the readme about how to set Dynamic Settings target FPS relative to AutoFPS's target FPS, with regards to FPS caps being used in particular, then the Dynamic Settings actually complements AutoFPS.

In AutoFPS Non-Expert mode, which is the default and is recommended for new users like you anyway, Dynamic Settings is automatically disabled during a flight session and restored to its original setting when exiting a flight, so you don't need to worry about it in that mode.