AutoFPS v0.4.2.15-test can be downloaded here. Feedback welcome as always.

Summary of changes since v0.4.2.14-test:

• Fixed issue where unchecking Auto OLOD when not in a flight caused the app to CTD. (My thanks to @GSaldenfor finding this issue!)

Following the latest changes I have made to AutoFPS up to the v0.4.2.15 test version, I have now taken this app about as far as I would like to go with it without over complicating an already fairly complicated feature set that is well beyond what I originally set out to do.

As such, if you have any burning issues with existing functionality contained up to v0.4.2.15 test version, please speak now before I wind things down to only a 'keeping the app MSFS compatible' level of effort.

Edited May 12, 20242 yr by Reset XPDR

52 minutes ago, Reset XPDR said:

Following the latest changes I have made to AutoFPS up to the v0.4.2.15 test version, I have now taken this app about as far as I would like to go with it without over complicating an already fairly complicated feature set that is well beyond what I originally set out to do.

As such, if you have any burning issues with existing functionality contained up to v0.4.2.15 test version, please speak now before I wind things down to only a 'keeping the app MSFS compatible' level of effort.

The App is working very well. Simple for beginners and enhanced features for experienced users.

I have enormous respect for your work and the drive to perfect the app. 

Thank you 🙏🏼 

I am still using 4.2.10 and it works perfectly. Is there any benefit for updating it?

Edited May 12, 20242 yr by Bobsk8

5 hours ago, Bobsk8 said:

I am still using 4.2.10 and it works perfectly. Is there any benefit for updating it?

I am planning on releasing the final 0.4.2.16 version in a couple of days before I go overseas on holidays, so I suggest waiting until then.

Hi Reset XPDR, I'm loving your addon and I think it's becoming essential. As it grows, do you think you could add a sentence or two to the readme for each of the newer features, so we can understand under what circumstances one setting might be more helpful than another? Trial and error is of course an option, probably a requirement, but it would be great to read your thoughts about when (just for example) Cloud Quality--GPU Load might be more advantageous than TLOD, or (for another example) FPS Tolerance vs. Sensitivity. Most of these features seem to have been added in response to issues brought up in this thread, and it's a bit hard to pull all of it together, especially if my CPU/GPU doesn't match the equipment of the people asking for refinements. I know the readme talks about what they do, but I'm still not sure when one setting is expected to be better than another. Thanks for considering!

Edited May 12, 20242 yr by prolixindec

42 minutes ago, prolixindec said:

Hi Reset XPDR, I'm loving your addon and I think it's becoming essential. As it grows, do you think you could add a sentence or two to the readme for each of the newer features, so we can understand under what circumstances one setting might be more helpful than another? Trial and error is of course an option, probably a requirement, but it would be great to read your thoughts about when (just for example) Cloud Quality--GPU Load might be more advantageous than TLOD, or (for another example) FPS Tolerance vs. Sensitivity. Most of these features seem to have been added in response to issues brought up in this thread, and it's a bit hard to pull all of it together, especially if my CPU/GPU doesn't match the equipment of the people asking for refinements. I know the readme talks about what they do, but I'm still not sure when one setting is expected to be better than another. Thanks for considering!

With the exception of GPU load versus TLOD for cloud quality functionality, which hasn't been formally released hence no coverage yet in the readme but certainly will be, I believe the existing readme provides enough information to know how to use a feature and generally when to use it.

Using your own example, when to use FPS tolerance versus sensitivity is already covered in both the usage and FAQ sections as follows:

• Usage: FPS Automation Method
  • FPS Sensitivity generally gives better results and hence is the default. Use FPS Tolerance if you experience stuttering issues. Use Auto TLOD if you are using an FPS cap and it interferes with setting a suitable target FPS.
• FAQ: I am getting major stuttering, freezes or CTDs in MSFS using this app. What can I do to stop them?
  • ...
  • If this doesn't resolve it, try enabling expert options and reducing the FPS Sensitivity setting to 2, to allow smaller TLOD changes.
  • If still not resolved, try the FPS Tolerance mode, which was the automation method in the original release version that had larger TLOD changes but they occurred less often, with a setting of 5.

I believe this gives sufficient guidance on when to use a particular automation method as succinctly as possible.

Can you give another example of where a setting is described adequately functionality-wise but not sufficiently on when to use it?

I've updated the readme in anticipation of 0.4.2.16 formal release in the next day or so. Since @prolixindecrecently mentioned wanting to know more about GPU load functionality, including when to use it, here is the relevant extract from the updated readme:

• Decrease Cloud Quality - When enabled, will reduce/restore cloud quality by one level if the activation condition is met.
  • Activation Methods
    • TLOD is the original method and is most suitable for systems where TLOD has the largest impact on desired MSFS performance.
    • GPU Load is the new method that allows cloud quality changes to occur independently of TLOD and is most suitable for systems where cloud quality has a similar or larger impact on desired MSFS performance than TLOD does.
    • IFR and VFR flight modes will use the same cloud reduction method.
  • TLOD (FPS Sensitivity and FPS Tolerance TLOD Automation Methods)
    • Decreases when TLOD has already auto reduced to TLOD Min and FPS is still below target FPS by more than the FPS tolerance.
    • Cloud Recovery TLOD with optional +
      • The TLOD level required to cancel an active cloud quality reduction state and restore cloud quality back to its initial higher quality level.
      • Ideally set to 50 TLOD or more above TLOD Min to provide a TLOD buffer to minimise the chance that cloud quality will constantly change down and up.
      • When + is checked, Cloud Recovery TLOD becomes relative to TLOD Min instead of absolute.
  • GPU Load (All TLOD Automation Methods)
    • Requires the GPU-Z companion app to be installed and running for this method to work. If GPU-Z is not running, the user will be alerted to start it in on the app status line in the General section.
    • Decreases when the GPU load, as measured by the GPU-Z companion app, is higher than the user-defined Decrease GPU Load percentage.
    • Cloud Recovery GPU load
      • 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.

Let me know if any of this requires clarifying or expanding.

Edited May 12, 20242 yr by Reset XPDR

In preparation for formal release of AutoFPS v0.4.2.16, hopefully tomorrow, I have put up a pre-release version of it here if anyone wants to try it out a little earlier. If no issues are found, I will just convert this release to be the formal release so you won't need to update again.

The only change since v0.4.2.15-test is:

• Fixed update checking code to correctly handle single and double digit patch releases. The URL for the 0.4.2.16 release will be shortened to 04216 so that older app versions can correctly detect this update. Future releases will not require a truncated URL.

On 5/12/2024 at 2:55 PM, GSalden said:

The App is working very well. Simple for beginners and enhanced features for experienced users.

I have enormous respect for your work and the drive to perfect the app. 

Thank you 🙏🏼 

Well said! I’m using AutoFPS on every single flight and it just works. Can’t fly without it now. 

Enjoy your holiday Reset!

14 hours ago, Reset XPDR said:

In preparation for formal release of AutoFPS v0.4.2.16, hopefully tomorrow, I have put up a pre-release version of it here if anyone wants to try it out a little earlier. If no issues are found, I will just convert this release to be the formal release so you won't need to update again.

I wanted to try the new version, installed it then wanted to try to remove it.

When I click Remove, there is no indication that the app has been removed...

Would be reassuring to see a simple confirmation that it has completed and removed the app. Thanks

Edited May 13, 20242 yr by toby23

2 hours ago, toby23 said:

I wanted to try the new version, installed it then wanted to try to remove it.

When I click Remove, there is no indication that the app has been removed...

Would be reassuring to see a simple confirmation that it has completed and removed the app. Thanks

I just tried it myself. After I clicked Remove I saw this:

Did you not see this too?

Following no major issues being identified in the test phase that haven't already been resolved, I have just formally released MSFS_AutoFPS v0.4.2.16 here. Thank you to everyone who participated in the test phase and provided feedback.

A summary of the changes are:

• A minor update to 0.4.2.10 that provides a new decrease cloud quality method based on GPU load that is independent of TLOD, a progressively hide-able UI by double-clicking on the main window, user-definable LOD step sizing for AutoTLOD automation mode, a simple way to recover window visibility if last window saved position is off screen and can't otherwise be recovered and various minor bug fixes.

My settings:

How I normally run the app with the above settings and with the UI partially collapsed:

As previously advised, my development efforts on this app will now wind down significantly. I will no longer be adding new functionality and will only be fixing any major issues found that do not have a practical workaround, such as a future MSFS update that is incompatible with the core functionality of this app.

I hope that you find this update useful and that this app continues to enhance your MSFS experience.

Edited May 14, 20242 yr by Reset XPDR

Many thanks, Reset!

I note that the app now lets you control cloud setting independent of TLOD setting - via GPU load (and a separate app running in addition).

Would it be an idea to also let cloud setting depend on fps directly, that is to say that low fps may trigger lower cloud settings irrespective of the TLOD?

In this way there would be no need for a separate app monitoring GPU load. I would prefer to avoid yet another app running in the background, while still having the possibility to control cloud settings independent of TLOD.

2 hours ago, LGKR said:

Many thanks, Reset!

I note that the app now lets you control cloud setting independent of TLOD setting - via GPU load (and a separate app running in addition).

Would it be an idea to also let cloud setting depend on fps directly, that is to say that low fps may trigger lower cloud settings irrespective of the TLOD?

In this way there would be no need for a separate app monitoring GPU load. I would prefer to avoid yet another app running in the background, while still having the possibility to control cloud settings independent of TLOD.

If you'd have mentioned this a couple of days ago before I released this final version I could possibly have configured the app to work this way, but it is too late now sorry. I wouldn't worry too much about running GPU-Z in the background as it has a very low footprint on system resources and is tried and tested as a reliable app over many years that it has been out there.

You can achieve close to what you want by running GPU-Z in the background and using AutoTLOD method with TLOD Min set to the fixed TLOD you want and TLOD base altitude set really high, like 80000 ft, so that TLOD stays fixed at TLOD Min for all of your usual flying. When the GPU load increase above your decrease trigger percentage, nominally 95%, cloud quality will drop. IMO this is a much better way of controlling cloud quality as FPS drops are usually not GPU related anyway, so dropping cloud quality based on FPS only would be very hit and miss.

Edited May 14, 20242 yr by Reset XPDR