V0.4.5.3 test 5 seems to be working OK in FS beta v1.5.21. Store version

Amazing support, as always!

Edited July 31, 2025Jul 31 by Twenty6

18 hours ago, kkbelos said:

Hi, having an issue with this wonderful little app that has kept my rig alive for longer than I ever thougt.

Currently, running latest AutoFPS version, MSFS2020 SU16 beta (1.39.9.0), even if I think this problem was happening before already. My computer takes a big hit with clouds, especially with overcast. Therefore, I am very interested to use the option to decrease cloud quality, triggered by GPU load (don't want to use TLOD trigger as the drop in FPS seems to be due to cloud mainly, even with the lowest TLOD I still have a drop in FPS). Anyway, with GPU-Z installed, and clouds in ultra at the start, it seems that AutoFPS never decreases cloud quality, no matter the GPU load or the FPS. I set a scenario with plenty of clouds and the GPU load skyrockets, but clouds stay at ultra. I played with the % load for activation and it does not change anything. Even above 98%, no change, clouds stay in ultra. 

I attached 2 screenshots. Any idea what I may be doing wrong? I read the instructions but did not find any solution.

Should now be fixed in 0.4.5.3-test6 or later available here:

whoah. looks helpful. thankfully i am staying with SU2 for now. it seems to be working just fine

except for those passive aggressive planes

12 hours ago, MaGer1965 said:

0.4.5.3-test3 compatibility test fails with latest FS24 b1.5.21.0

Confirmed FIXED with b4.5.3-test6. 

Thank you for the quick adjustment!

Rather than users of 0.4.5.2 having to stumble upon this version's incompatibility with MSFS 2024 1.5.21.0, I have decided to release 0.4.5.3 with the fix in it, amongst other small changes, and thus allow them to auto update before experiencing this. To that end, 0.4.5.3 has been officially released and can be found here if you do not have auto update enabled. Thanks to all who provided useful and responsive feedback during the short development phase, particularly just after MSFS 2024 1.5.21.0 was released where we came to a solution within a few hours.

Release notes for 0.4.5.3

Executive Summary

This update introduces full compatibility with MSFS 2024 SU3 beta (1.5.21.0), adds forced support for OptiFG and MFG graphics modes, fixes decrease cloud quality activation issues in MSFS 2020 and other minor improvements.

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.

 

Edited July 31, 2025Jul 31 by Reset XPDR

10 hours ago, Reset XPDR said:

Can I get a few of you on the SU3 beta to try this new version out and report back, mentioning Steam or MS Store versions. Thanks.

I can confirm dynamic LOD is working again. MS Store. 

Thanks @Reset XPDR !!

Good job. Many thanks 

Thanks for this app. I just installed it a few days ago. I used to use an auto LOD app in 2020, but not in 2024. But, after some freezes and CTDs I decided to try AUTO_FPS. Since trying it, the scenery has looked great; there are no stutters, freezes, or CTDs!

@Reset XPDR

Dont you have a "buy me a coffee" or similar link?

I love the fact you're doing this for free of course, but I think lots of people would be happy to donate something for your work.

How does this app work with frame generation?  Or is it setting actual fps?

Just now, ryanbatc said:

How does this app work with frame generation?  Or is it setting actual fps?

It’s not setting FPS… it’s monitoring FPS (either native or FG - whatever you’re using) and sets TLOD and OLOD on the fly to maintain your target FPS.
 

So for example, if I’m not using AutoFPS, on my system, I get around 100FPS with FG at TLOD 400 and OLOD 200. But when I land at a busy airport, my FPS can drop to below 80FPS. When I’m running AutoFPS, it targets around 95FPS and I see TLOD ramping up to 600-800 when I’m flying with FPS still around 100, and then when I land at a busy airport, it ramps my TLOD down to 200-300 to keep my FPS from dipping into the 80s. It’s perfect, because I don’t need high TLOD when landing, and I need max FPS. And when I’m flying, I have performance headroom to spare, so it uses that to maximize visuals. 

2 hours ago, ConairMSFS said:

@Reset XPDR

Dont you have a "buy me a coffee" or similar link?

I love the fact you're doing this for free of course, but I think lots of people would be happy to donate something for your work.

I appreciate the gesture but I do this out of love for flight simming and that it keeps my mind active in retirement, sometimes a bit too active but that is my own choice 😄Having users like yourself occasionally expressing that they get something out of my efforts is enough for me!

Edited July 31, 2025Jul 31 by Reset XPDR

18 hours ago, Reset XPDR said:

Should now be fixed in 0.4.5.3-test6 or later available here:

Many thanks!!! Indeed, it works now. Really appreciated. I just realized that there is still a small bug, at least on my side. The % GPU recovery value does not stick. I can change it but as soon as I click somewhere else, it goes back to 80

14 minutes ago, kkbelos said:

Many thanks!!! Indeed, it works now. Really appreciated. I just realized that there is still a small bug, at least on my side. The % GPU recovery value does not stick. I can change it but as soon as I click somewhere else, it goes back to 80

No worries. Re GPU recovery value not sticking, that is usually caused because the new value must be at least 10% below your decrease value otherwise it goes back to its previous value. I set it this way so that clouds do not continuously cycle down then up in quality when the recovery is set too close to the decrease trigger value.

This is covered in the readme:

• Decreases when the GPU load, as measured by the GPU-Z companion app, is higher than the user-defined Decrease GPU Load percentage. (50% - 100% allowable)
• Cloud Recovery GPU load (5% - 90% and at least 10% less than Decrease GPU Load allowable)
  • Recovers when the GPU load is lower than the user-defined Recover GPU Load percentage.
  • Ideally set to at least 15% lower than the Decrease GPU Load percentage to provide a GPU load buffer to minimise the chance that cloud quality will constantly change down and up.

If that is not it, post up a screenshot so I can recreate the issue and fix it.

Edited July 31, 2025Jul 31 by Reset XPDR

28 minutes ago, Reset XPDR said:

No worries. Re GPU recovery value not sticking, that is usually caused because the new value must be at least 10% below your decrease value otherwise it goes back to its previous value. I set it this way so that clouds do not continuously cycle down then up in quality when the recovery is set too close to the decrease trigger value.

This is covered in the readme:

• Decreases when the GPU load, as measured by the GPU-Z companion app, is higher than the user-defined Decrease GPU Load percentage. (50% - 100% allowable)
• Cloud Recovery GPU load (5% - 90% and at least 10% less than Decrease GPU Load allowable)
  • Recovers when the GPU load is lower than the user-defined Recover GPU Load percentage.
  • Ideally set to at least 15% lower than the Decrease GPU Load percentage to provide a GPU load buffer to minimise the chance that cloud quality will constantly change down and up.

If that is not it, post up a screenshot so I can recreate the issue and fix it.

Ahh yes, sorry for that. I had read the instructions looking for the initial issue, but did not remember to look again when I saw I could not change the number. You are fully right and it works as described. Many thanks again man.