As recently discussed with @mikeymike, I have now updated the latest test version app with auto reversion from test versions as follows:

• Added automatic reversion option from test version to current formal release.  
  • Triggers when the user unchecks the +Tests option while running a test version, which is now allowable.  
  • Prompts the user once to revert, regardless of the selected update mode.  
  • If declined, the app stays on the test version and will only notify or auto update as applicable for the next formal release.

Here's what it looks like just after you uncheck +Tests in a test version:

 

I have also updated the update checker code to be more robust when checking for and offering updates, mainly to help a user who was having an issue with the URL redirect method the app has used in the past. It tests on the bench just fine, but with software being software, let me know if anything strange occurs with these changes. 

 

 

 

Hi, I am still a bit confused about what framerates to set when using hybrid dynamic settings. My monitor is set tot 120 fps, I use FG x2 so I have set my FPS cap to 60 and the max framerate in MSFS 24 (beta 4) also to 60. However, I never reach 120 fps, usually its somewhere between 90 and 110, even when the graphics card (4070 Ti super) usage isn’t on its maximum. It rarely gets above 85%. The AutoFPS usually uses Dynset30. Is this an expected behavior or am I doing something wrong? /

4 hours ago, Reset XPDR said:

That is correct.

Thank you, I've tried it this morning and I've the perception that the combination of autofps and dynamic settings indeed results in a more smooth experience with a lot less microstutters.

12 minutes ago, JWvdH said:

Hi, I am still a bit confused about what framerates to set when using hybrid dynamic settings. My monitor is set tot 120 fps, I use FG x2 so I have set my FPS cap to 60 and the max framerate in MSFS 24 (beta 4) also to 60. However, I never reach 120 fps, usually its somewhere between 90 and 110, even when the graphics card (4070 Ti super) usage isn’t on its maximum. It rarely gets above 85%. The AutoFPS usually uses Dynset30. Is this an expected behavior or am I doing something wrong? /

You should be targeting the FPS that your system, not your monitor, is easily capable of ie. I would use FPS cap automation mode and set a target FG FPS to 90, then in MSFS set max frame rate and dynamic setting to 45. 

The last time I tried Dynamic settings with AutoFPS, some of the terrain would look extremely low res.  Turned it off and used only AutoFPS and it was back to normal.  I'll have to give it another try and see if maybe SU4 fixed that issue.  

Edited October 20, 2025Oct 20 by FakeWayne

19 hours ago, Reset XPDR said:

No worries. FYI, AutoFPS will not actually cap FPS, rather it will work to your target FPS and just happens to have an FPS cap mode optimised for when you are using an externally set FPS cap. If you are not achieving your target FPS, it is generally because your AutoFPS LOD settings and/or MSFS graphics settings are too high. Having said that, 40 FPS is a very low maximum for your system spec, which is very similar to mine in which I can achieve 100 FPS+ in low complexity areas at 4K Ultra settings, so something external to AutoFPS is bringing your system down like this.

I have to investigate this further. I have now a flight from Nice to Toulouse in the Fenix A321 of Transavia, everything ultra with FSLTL traffic (BATC). Busy airspace. With or without AutoFPS it is now just between 45-50 fps. But with AutoFPS is the TLOD 75 in red. In MSFS 2020 I did not have this problem so I have to check further how it comes. But the app is great! I have still MSFS 2020 and still use it with the 2020 version. Thank you.

Apologies if I have missed something as I have not followed this long thread in awhile. I have the latest version installed (0.4.5.8-test2).

Even though I have TLOD base set to 100 (base is 50 feet) and TLOD Top at 400 (Alt top 3000) my TLOD continues to grow and grow.  It doesnt stop at 400.

Flying over the ALPS and its currently showing TLOD at 830!!  Using Multiframe generation (4x) fps set to 30 in sim.  FPS set to 30 in AutoFPS.  Using FPS Cap mode at the moment and a custom user1 profile.

UPDATE

Played around with the FPS value in AutoFPS, it was set to match the native non frame gen value of 30. With frame gen I was getting 120 fps.  If its set to equal or lower than this in AutoFPS then TLOD gets bigger and bigger.  If I set it to say 125 then TLOD drops back down to match TLOD Top setting

Edited October 20, 2025Oct 20 by cj-ibbotson

7 hours ago, FakeWayne said:

The last time I tried Dynamic settings with AutoFPS, some of the terrain would look extremely low res.  Turned it off and used only AutoFPS and it was back to normal.  I'll have to give it another try and see if maybe SU4 fixed that issue.  

The trick to using dynamic settings with AutoFPS without it severely crippling the graphics is to make sure you set it to a target FPS where it is not normally active. With a capped FPS, this seems to be pretty straight forward by setting everything to that cap but with a free range FPS dynamic setting seems to need to be set a little bit higher than your AutoFPS target FPS, otherwise it activates too easily.

I just checked what the readme says on this and it gets the setting recommendation for free range the wrong way around and is possibly why you experienced such a poor result. ie. it currently says:

• If not using an FPS cap, it is recommended to set the MSFS dynamic settings target frame rate to 10 FPS lower than the native frame rate equivalent of the AutoFPS target FPS for best results.

Whereas it should say:

• If not using an FPS cap, it is recommended to set the MSFS dynamic settings target frame rate to 10 FPS higher than the native frame rate equivalent of the AutoFPS target FPS for best results. 

I have amended the readme to reflect this.

1 hour ago, cj-ibbotson said:

Apologies if I have missed something as I have not followed this long thread in awhile. I have the latest version installed (0.4.5.8-test2).

Even though I have TLOD base set to 100 (base is 50 feet) and TLOD Top at 400 (Alt top 3000) my TLOD continues to grow and grow.  It doesnt stop at 400.

Flying over the ALPS and its currently showing TLOD at 830!!  Using Multiframe generation (4x) fps set to 30 in sim.  FPS set to 30 in AutoFPS.  Using FPS Cap mode at the moment and a custom user1 profile.

UPDATE

Played around with the FPS value in AutoFPS, it was set to match the native non frame gen value of 30. With frame gen I was getting 120 fps.  If its set to equal or lower than this in AutoFPS then TLOD gets bigger and bigger.  If I set it to say 125 then TLOD drops back down to match TLOD Top setting

In AutoFPS you set your target FPS to include whatever frame generation tech you are using, so in your case if you can achieve FG 120 FPS capped pretty much all the time then 120 is what you set it to. 

Re TLOD going above the Top value, that is allowable per the readme as it is not a Max as such:

• FPS Cap - a specific configuration of Auto TLOD optimised for when a system FPS cap is in use.
  • TLOD Base + and TLOD Top + are automatically enabled and disabled respectively, and their associated checkboxes are removed from the UI.
  • A TLOD Base - checkbox is provided in Expert mode which excludes TLOD Base + occurring below Alt TLOD Top when checked.
  • The following guidelines should be observed to get the best result from this mode:
    • Set TLOD Base and TLOD Top values within your FPS cap for worst-case performance during your flight type profile. TLOD Base + may increase with better performance but won't drop below the set values.
    • TLOD Base + is applied across the entire altitude schedule, potentially allowing a doubling of TLOD Top if performance conditions are favorable, so be particularly conservative when setting TLOD Top.

It actually goes slightly above this doubling during the seek process, as it wants to ensure there is performance headroom, which is why you saw 830. If you looked about 30 seconds later it would have settled back at 800.

If you don't want it to go as high as 800 and want 400 as a max instead, just set TLOD Top to 200, but you will be missing out on potentially much higher TLOD if performance conditions are favourable, which is the entire point of the FPS cap automation mode.

16 hours ago, Reset XPDR said:

The trick to using dynamic settings with AutoFPS without it severely crippling the graphics is to make sure you set it to a target FPS where it is not normally active. With a capped FPS, this seems to be pretty straight forward by setting everything to that cap but with a free range FPS dynamic setting seems to need to be set a little bit higher than your AutoFPS target FPS, otherwise it activates too easily.

So, if I'm capping to 40 fps in AutoFPS, I should be capping to 40 fps Dynamic also?  Because that's currently what I'm doing, and it's definitely causing terrible res ground textures.  Turn off Dynamic, and textures are instantly better.

11 hours ago, FakeWayne said:

So, if I'm capping to 40 fps in AutoFPS, I should be capping to 40 fps Dynamic also?  Because that's currently what I'm doing, and it's definitely causing terrible res ground textures.  Turn off Dynamic, and textures are instantly better.

The way you say "I'm capping to 40 fps in AutoFPS" concerns me a bit because,. as mentioned here before, AutoFPS does not actually cap your FPS itself, rather it has an FPS cap automation mode that does work with an FPS cap set elsewhere, eg. MSFS max frame rate, RTSS, nVidia CP/App. If your FPS is truly capped to 40 in one of the ways just mentioned and AutoFPS shows your system is achieving that 40 FPS steady state and dynamic setting is set to 40 FPS, then dynamic setting should not be active.

You can verify this by observing what the FPS view in Developer Mode is showing you. eg. here is my setup right now, with my FPS capped at 40 via MSFS Max Frame Rate settings (it is actually set to 41 to achieve 40 because SU4 has broken this particular setting) and Dynamic Setting set to 40 FPS. You can see that Dynamic Setting is not active because the Terrain and Object LOD factors are both 1.00, which is the same as what they would show if Dynamic Setting is disabled.

 

If you believe you have set it up correctly and it is not behaving like this for you, please post a similar screen shot of the AutoFPS window on top of MSFS with its FPS view showing so that I can see if anything else is the issue.

 

 

14 hours ago, Reset XPDR said:

The way you say "I'm capping to 40 fps in AutoFPS" concerns me a bit because,. as mentioned here before, AutoFPS does not actually cap your FPS itself, rather it has an FPS cap automation mode that does work with an FPS cap set elsewhere, eg. MSFS max frame rate, RTSS, nVidia CP/App. If your FPS is truly capped to 40 in one of the ways just mentioned and AutoFPS shows your system is achieving that 40 FPS steady state and dynamic setting is set to 40 FPS, then dynamic setting should not be active.

Yeah, that was poor wording on my part.  I'm fully aware of that.

Thanks for the explanation! That all makes sense.

On 10/22/2025 at 11:20 AM, Reset XPDR said:

my FPS capped at 40 via MSFS Max Frame Rate settings (it is actually set to 41 to achieve 40 because SU4 has broken this particular setting)

FYI, Max Frame Rate is now fixed in SU4 1.6.18.0, so you can now set it to, for example, 40 and the sim will lock to 40 FPS as it should. Note that this setting is based on the native frame rate to which you wish to lock MSFS. ie. if your intended max is 120 FPS for 4X MFG, then 30 is the native frame rate and that is what you set for MSFS Max Frame Rate. AutoFPS would be set to 120 for target MFG FPS and 4X in the MFG dropdown list in this example.

Edited October 24, 2025Oct 24 by Reset XPDR

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

MSFS Compatibility: 1.39.9.0, 1.5.27.0, 1.6.19.0.

Release notes for 0.4.5.8

This update introduces a rollback option for test users, improves update handling for speed and resilience, and fixes several sim rate and UI issues.

Executive Summary

This release strengthens update handling, adds rollback support for test users, and resolves sim rate and UI inconsistencies:

• Test Version Rollback: Users opting out of + Test are now offered a one‑time automatic reversion to the latest formal release.
• Smarter Updates: Update checks are faster, safer, and more resilient, with reuse of recent data, URL verification, and protection against missing files.
• Fixes & Optimisations: Corrected sim rate reset logic, restored sim rate display in MFG mode, and fixed MFG multiplier dropdown visibility.

What setting manages tree draw distance? I can easily get TLODS of 1000 and OLODs if 400, but the tree draw distance is still disappointingly small.