1 hour ago, WallysWorlds said:

Thanks for the update. I'll download the test version and give it a fly today and will report back.

From what I have read, Activesky does not actually modify the Usercfg.opt file rather it may inadvertently trigger MSFS to resave it when it sends new cloud textures through. My simulated testing by just manually saving this file should therefore be sufficient, but this is software so anything is possible hence your real world feedback of what actually happens now after Activesky periodic theme reloads will be useful.

Been flying for the past hour and the test version of AutoFPS is not showing that message anymore. Everything is working fine. Many thanks for your time with this!

52 minutes ago, WallysWorlds said:

Been flying for the past hour and the test version of AutoFPS is not showing that message anymore. Everything is working fine. Many thanks for your time with this!

Glad to hear it. Thanks for the ongoing feedback I needed to get this sorted.

As there are a few notable other fixes in this test release, I am going to go ahead and formally release it today so that the next test version is a clean slate of changes for when MSFS 2024 SU5 beta rolls out, any day soon I believe.

Edit: Actually, I am thinking of changing/consolidating the target FPS names to be more intuitive with auto MFG detection now working, so I may hold off on formally releasing just yet and put out another test version just to see if I get any hate from changing them.

Edited January 23Jan 23 by Reset XPDR

10 hours ago, Reset XPDR said:

Actually, I am thinking of changing/consolidating the target FPS names to be more intuitive with auto MFG detection now working, so I may hold off on formally releasing just yet and put out another test version just to see if I get any hate from changing them.

Further to this, I have spend the day reworking the target FPS UI to consolidate existing OFG and MFG manual modes into a single Man FG mode, relocated and repurposed the old MFG dropdown to replace the target FPS dropdown when in Man FG mode (including an Auto selection to return you to the original target FPS dropdown), and migration code to auto convert the old to the new while retaining backwards compatibility should you revert versions.

It is not as scary as it sounds, but I am advertising here it in case anyone uncovers any major flaws in the new design before I formally release it. Let me know if the changes causes any grief. It is available as 0.4.6.3-test6 or later, available here.

Revised Target FPS type dropdown:

 

When you select Man FG, it changes to the following, where you can manually select your FG multiplier:

If you now select Auto it will take you back to what you see on the first screenshot.

And for those who have not been following development of 0.4.6.3, in FG mode the app will now auto detect what MFG multiplier you have set if you have configured MFG within MSFS settings. eg.

If you have configured MFG externally, eg. via the nVidia app, instead of within MSFS, you will need to use Man FG and if you were using the MFG dropdown beforehand you will be automatically set up this way. I strongly suggest you switch to using the MSFS MFG setting instead and go back to Auto within the app.

 

Edited January 23Jan 23 by Reset XPDR

5 hours ago, Reset XPDR said:

Further to this, I have spend the day reworking the target FPS UI to consolidate existing OFG and MFG manual modes into a single Man FG mode, relocated and repurposed the old MFG dropdown to replace the target FPS dropdown when in Man FG mode (including an Auto selection to return you to the original target FPS dropdown), and migration code to auto convert the old to the new while retaining backwards compatibility should you revert versions.

It is not as scary as it sounds, but I am advertising here it in case anyone uncovers any major flaws in the new design before I formally release it. Let me know if the changes causes any grief. It is available as 0.4.6.3-test6 or later, available here.

.....

 

Wait....what??? 😉

Seriously, thanks so much for all you do for this app. Much appreciated!

I had an idea today about expanding when Auto Target FPS can be used in the app. Currently, Auto Target FPS is disabled whenever TLOD Base Extra or TLOD Top Extra are active, because any FPS sampling would be distorted by the extra TLOD adjustments, making the baseline unreliable and risking feedback loops.

The new approach would be to simply hold back initial TLOD Extra seeking during a short baseline window, allowing Auto Target FPS to obtain a clean reading before TLOD Extra is applied. This removes the original conflict and makes it feasible for Auto Target FPS to operate safely in any mode that has TLOD Base or TLOD Top Extra enabled, including FPS Cap mode, which can now use a detected FPS cap as the target or fall back to the manual setting if no cap is found.

In general, the UI impact is minimal. Auto Target FPS would simply remain visible more often and could be used more broadly. The only noticeable difference would be in FPS Cap mode when no cap is detected: the Auto Target FPS control would turn orange to indicate this, and the target FPS text box would be re-enabled for backup use.

Any refinements or objections?

Edited January 24Jan 24 by Reset XPDR

@Reset XPDR

no way to buy you a coffee or something similar to show the appreciation for your work? 

1 hour ago, fernandinho said:

@Reset XPDR

no way to buy you a coffee or something similar to show the appreciation for your work? 

He needs a RTX 5090 not a coffee 🤣 

8 hours ago, fernandinho said:

@Reset XPDR

no way to buy you a coffee or something similar to show the appreciation for your work? 

 

6 hours ago, deepstar said:

He needs a RTX 5090 not a coffee 🤣 

Nah, all good. This project keeps my mind ticking over in retirement and that it allows users to get a little bit more out of their flight simming experience is enough reward from me. 

Hi, re the Auto Target FPS post above, what would be the benefit of using Auto Target FPS rather than a manual FPS cap? I use an FPS cap most of the time.

32 minutes ago, Harrier77 said:

Hi, re the Auto Target FPS post above, what would be the benefit of using Auto Target FPS rather than a manual FPS cap? I use an FPS cap most of the time.

Mainly that if you change that cap externally, the app can auto adjust to the new cap, which probably doesn't happen that often with most users but does with me.

The idea actually spawned from how I config my system for takeoff/landing versus cruise. For the former phases, I run my system at high performance and use a cap of 80. For cruise, I slow it down to 40 (using voice commands to invoke hot keys) to reduce noise/power/heat when I am often looking at other things, so in this case I would like it to auto retune to 40 so it doesn't start dumbing down settings. Thinking about it more, this is an extreme edge case that I would not normally entertain, but did since it is my app.

As it turns out, there was method in my previous madness of not allowing Auto Target FPS with TLOD Extra with FPS Sensitivity and Tolerance modes because the calculated auto target FPS ends up causing TLOD Extra to never activate by the way the maths of it comes out. As such, it seems this part of it was a dud idea and I will therefore relegate the initial work I did on it today to the bit bucket.

I will probably still end up doing Auto Target FPS for FPS Cap mode because I have already done a good portion of the leg work and that one is feasible, even if it finds little utility for users other than me.

In short, don't worry about this one any more.

 

On 1/23/2026 at 10:59 AM, Reset XPDR said:

Revised Target FPS type dropdown:

all your screenshots show: 

"This content is no longer available."

why not use ImgBB — Upload Image — Free Image Hosting 

https://imgbb.com/

1 hour ago, turbomax said:

all your screenshots show: 

"This content is no longer available."

why not use ImgBB — Upload Image — Free Image Hosting 

https://imgbb.com/

Because they usually persist long enough to get my point across and in my experience anything seemingly free like that tends to come with undesirable strings attached (usually hidden at first). Having said that, I will check this one out since you suggested it.

Edited January 25Jan 25 by Reset XPDR

6 hours ago, Reset XPDR said:

I will probably still end up doing Auto Target FPS for FPS Cap mode because I have already done a good portion of the leg work and that one is feasible, even if it finds little utility for users other than me.

This one is being tempermental and not yielding any ground-shaking benefit, so I am going to scrap the whole idea.

I haven't received any negative feedback on the rework of the target FPS type dropdowns in 0.4.6.3-test6 and IMO it provides a better way of changing this setting, so I'll probably formally release 0.4.6.3 soon and have a clean slate for the impending SU5 beta.

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

The biggest thing to note in this update is that you no longer have to manually set MFG multiplier in the app. As long as you set the MFG multiplier in the MSFS settings and you are not using the new Man FG, the app will auto detect MFG correctly.

This release enhances MFG auto‑detection for next‑gen GPUs, consolidates target FPS options, streamlines installer behaviour for silent updates, resolves several MSFS 2020 and auto‑FPS logic issues, and expands developer‑mode diagnostics with smarter offset testing and real‑time memory‑scanner improvements.
 

@turbomaxFYI, trying out imgbb like you suggested.

Edited January 26Jan 26 by Reset XPDR