For those wondering what the outcome was with @LGKR’s AutoFPS failing to attach to MSFS most of the time, we managed to get to the bottom of it and solve it.

The existing attach process only ever assessed the first MSFS window it came across, which isn’t an issue for Steam users because all MSFS windows contain version metadata. However, for MS Store users it does cause a problem if they’re running multi‑window and one of those secondary windows had focus when AutoFPS started. Those windows don’t expose the title or version metadata, and that was what caused the app to fail to attach in LGKR’s case.

The fix was relatively simple: iterate through all MSFS windows until the one containing the main title footprint is found, then extract the version information from that. I’ve incorporated the fix in 0.4.6.5‑test8 or later, validated that it now works no matter how many MSFS windows you have open or which one had focus before starting AutoFPS, and it will be in the 0.4.6.5 release version in a few days.

My thanks go out to LGKR for persisting with running trial test versions and reporting back. It was a tricky one to uncover, but we got there in the end, and now all multi‑window MSFS users will benefit from the fix.

 

32 minutes ago, Reset XPDR said:

It was a tricky one to uncover, but we got there in the end, and now all multi‑window MSFS users will benefit from the fix.

haven't they finally called and offered you a job in their MSFS team, I think it's about time. but then again, we would loose you here, not a good idea.😀

52 minutes ago, turbomax said:

haven't they finally called and offered you a job in their MSFS team, I think it's about time. but then again, we would loose you here, not a good idea.😀

Nah, doing this solo with no one to brow beat me with impossible schedules, holding pointless meetings, giving me poor or forced requirements, and subjecting me to bureaucratic and lengthy change processes is something I am not willing to give up, no matter how much money they threw at me. 

If there is one thing they actually could do to make my life easier, and the app not quite so shady in their eyes, is to expose the settings my app changes in simconnect so that I could finally come out of the darkness of my rebel base here at Avsim and put out a fully legit version of this app, but somehow I don't think that will happen so you are stuck with me here for the forseeable future. 😄

11 hours ago, turbomax said:

haven't they finally called and offered you a job in their MSFS team, I think it's about time. but then again, we would loose you here, not a good idea.😀

Lol, and after that pat on the back I discovered that I completely broke MSFS 2020 compatibility with the app in Test8 and Test9. It has now been fixed in Test10 before too much damage spread, but such dodgy coding should be punished not rewarded, so no MSFS team job for me!  😆

Anyway, I am out of town for a few days, away from my main dev PC, which is a sure sign SU5 beta is about to drop because I won't be able to quickly patch up the app when it breaks compatibility with the app with a settings memory map change. I am taking my backup dev laptop with me though, so if it does happen I should be able to fumble my way through it on the road.

8 hours ago, Reset XPDR said:

Anyway, I am out of town for a few days, away from my main dev PC, which is a sure sign SU5 beta is about to drop because I won't be able to quickly patch up the app when it breaks compatibility with the app with a settings memory map change. I am taking my backup dev laptop with me though, so if it does happen I should be able to fumble my way through it on the road.

Murphy's law has struck and SU5 beta has dropped at the most inconvenient time for me in many months and of course they changed the memory map, making AutoFPS (and DLOD_RE) incompatible with it, so I will get to it when I get to it, hopefully within the next day.

Sir, you're the man!

AutoFPS launched togheter with the simulator and surprise, test11 already released.

Thanks a lot for what you are doing.

FYI, there is a small bug in pre-0.4.6.5-test12 app versions whereby agreeing to the auto update offer for compatibility test fail will result in an invalid download URL and the app will therefore not auto update.

Normal auto-updating works, so you if you experience this and want to use the app with SU5 beta just rerun the app without being in an MSFS flight, check the + Tests option  then change your update option to prompted updates and you should then be offered an auto update that will work. You can uncheck + Tests after that if you want, but just be aware app compatibility updates will always be released as a test version first so if you are staying with SU5 Beta you are best to keep + Tests enabled anyway.

I have fixed it in -test12, and will probably formally release this version as a formal release 0.4.6.5 sometime today so that every in on an app version that will reliably auto update for compatibility reasons when the next SU5 Beta that changes the memory map is released and I have produced a new compatible app version.

As always, hats off to you for your contribution to your fellow simmers, both AutoFPS and DynamicLOD has been the most set and forget addons I have installed (I am still on DynamicLOD due to a little bit more manual control over the steps for OLOD/TLOD, but AutoFPS is also used from time to time of course), and when others asks me for any recommendations for better performance during all stages of flights, I bring up both of them everytime and tell them about the more manual control you have with DynamicLOD, but if you have it in you to "set and forget" the settings, AutoFPS is the one (given that the person has one or the other use of the sim, in a Cessna below or an airliner above FL100).

I am wondering if it is possible in a future version of DynamicLOD to have a compact window like AutoFPS has? The way you can click your way through it is actually very useful if you are doing testing and can have a small window on top with the most important info visible. Like it is with AutoFPS in this image.

Edited February 14Feb 14 by Benjamin H
Few too many pints

27 minutes ago, Benjamin H said:

As always, hats off to you for your contribution to your fellow simmers, both AutoFPS and DynamicLOD has been the most set and forget addons I have installed (I am still on DynamicLOD due to a little bit more manual control over the steps for OLOD/TLOD, but AutoFPS is also used from time to time of course), and when others asks me for any recommendations for better performance during all stages of flights, I bring up both of them everytime and tell them about the more manual control you have with DynamicLOD, but if you have it in you to "set and forget" the settings, AutoFPS is the one (given that the person has one or the other use of the sim, in a Cessna below or an airliner above FL100).

I am wondering if it is possible in a future version of DynamicLOD to have a compact window like AutoFPS has? The way you can click your way through it is actually very useful if you are doing testing and can have a small window on top with the most important info visible. Like it is with AutoFPS in this image.

It is a little more complicated than with AutoFPS as the latter is simply vertically collapsing the stack panels holding expert settings and general sections, whereas DLOD_RE would require vertical and horizontal collapsing and resizing of a window that was never designed with that intent. Nonetheless, I like that idea and will look at implementing it if it can be done without a major rework of the UI and with no undesirable side effects. I am currently focused on continued SU5 Beta compatibility with these apps, so will look at it after that settles down a bit, usually within a few SU Beta updates.

I can't seem to install test 12 version (for su5 beta?)

I just grabbed a fresh copy from the GitHub site too so I'm a little perplexed

 

1 hour ago, ryanbatc said:

I can't seem to install test 12 version (for su5 beta?)

I just grabbed a fresh copy from the GitHub site too so I'm a little perplexed

 

Hi;

Test version is under this link https://github.com/ResetXPDR/MSFS_AutoFPS/releases/tag/v0.4.6.5-test

On 2/12/2026 at 7:55 PM, turbomax said:

haven't they finally called and offered you a job in their MSFS team, I think it's about time. but then again, we would loose you here, not a good idea.😀

He is a best thing that happened to us after MSFS.... 🙂😃

5 hours ago, ryanbatc said:

I can't seem to install test 12 version (for su5 beta?)

I just grabbed a fresh copy from the GitHub site too so I'm a little perplexed

 

Yeah, sorry about that. I am aware of this issue in older versions of the app. It is caused by having one too many v characters in the URL that gets built, and this is the first time it has actually fired during a live compatibility update, so I did not realise it was still present until now.

Test12 fixes it, but only after it has already been installed. The only practical step I can take right now is to formally release 0.4.6.5 as it is, so that everyone who normally auto updates will be on a corrected version before the next SU5 memory map change. Those changes usually appear early in the beta cycle, and with everyone on a fixed build, the compatibility auto update will work properly from now on.

So expect to see AutoFPS 0.4.6.5, and DynamicLOD_ResetEdition 0.5.6 as well, released today.

Well, some good news. I’ve managed to sort out the “File does not exist at the given URL” message that shows up when running pre‑0.4.6.5‑test12 with the SU5 Beta and the compat test fails. I’ve set up a mirror URL that serves the correct installer to those older versions, and it does this without affecting normal auto updates or anyone already on test12 or later. I've also done the same for DynamicLOD_ResetEdition (test7 being the fixed one), which was afflicted by the same bug.

The nice part is this means there’s no need to rush out 0.4.6.5 just to deal with this. Even if we did, it wouldn’t fully fix things anyway because it usually takes about a month for most users to catch up to a new version. So we can just keep going as usual.

You’ll still see compat fails whenever MS changes the MSFS settings memory map, but the test builds that fix those changes should now flow through properly to anyone on a reasonably recent version.

As always, thanks Reset!