FYI for those on the 0.4.5.6-test program, I've just released test14 which promotes the new hybrid dynamic setting capability from exerimental to test, meaning all test users can easily try it if they desire. I have done this because the feedback I have received on it, and my own experience, has been very positive and I now want it to be easily accessible to the broader test group before I consider unleashing it as a formal release in the near future and I think it is stable enough to do that. 

As many users do not read release notes, even my trusty testers 😄, I have included a one-time message advising users of the new feature. This is mostly for those users who may not be interested in it, but may have left their dynamic settings enabled because AutoFPS auto-disabled them in the past and now it will no longer do that so they need to be aware of that. The message box will look like this:

 

I have also included in the release notes a section on why the new feature is being added in the first place, again posted here because very few actually read it, as follows:

• The hybrid approach leverages the strengths of both MSFS dynamic settings and AutoFPS:
  • MSFS’s built-in dynamic settings engine is highly responsive, using internal performance metrics not accessible externally. This allows it to adjust LODs more precisely and rapidly than AutoFPS alone.
    • AutoFPS complements this by adjusting the base LOD values that MSFS dynamic settings operate within. It responds to longer-term performance trends, especially increasing LODs in favourable conditions — extending the usable range beyond the default 50–100% window imposed by MSFS dynamic settings.
    • AutoFPS also manages a broader set of performance-critical graphics settings — including Cloud Quality and ten others — offering a more comprehensive performance management regime than dynamic LODs alone.
  • Together, MSFS dynamic settings and AutoFPS now work in tandem to manage both performance and visual quality, each addressing different layers of the optimisation stack.

As usual, constructive feedback, good or bad, is welcome on this change from those who actually try it. 

Would it be feasible to add an option for sim rate detection and specific profiles? When I fly with sim rate 1x I like to set TLOD Top to 400 and it maintains my FPS at 60 well (FPS Cap at 60, Vsync on).

When I fly with sim rate 4x my FPS dip to 40-50 with TLOD Top 400 and using FPS Cap it doesn't seem to drop my TLOD below 400 even with the low frames.

So either - am I doing something wrong, or is there scope to add an option - i.e. if sim rate >1x then have a separate max TLOD field (200 seems to work for me at higher sim rates).

Slightly OT but somehow related: did anyone find a way how the FPS limit for Dynamic Settings within MSFS can be set precisely? I can change this value only in steps of 10FPS, which is not really suitable for my setup...

3 minutes ago, AnkH said:

Slightly OT but somehow related: did anyone find a way how the FPS limit for Dynamic Settings within MSFS can be set precisely? I can change this value only in steps of 10FPS, which is not really suitable for my setup...

It adjusts in steps of 5 FPS in my MSFS settings. You may also be able to set it to something in between by manually editing the UserCfg.opt file for the TargetFrameRate and TargetFrameRateVR settings.

10 minutes ago, Speedbird 217 said:

Would it be feasible to add an option for sim rate detection and specific profiles? When I fly with sim rate 1x I like to set TLOD Top to 400 and it maintains my FPS at 60 well (FPS Cap at 60, Vsync on).

When I fly with sim rate 4x my FPS dip to 40-50 with TLOD Top 400 and using FPS Cap it doesn't seem to drop my TLOD below 400 even with the low frames.

So either - am I doing something wrong, or is there scope to add an option - i.e. if sim rate >1x then have a separate max TLOD field (200 seems to work for me at higher sim rates).

In my experience, scenery isn't able to load fast enough a sim rates like 4X and gets blurry, so IMO it is a moot point what TLOD you have set at the time as visual quality has already been compromised. Also, if you are manually switching sim rate by key presses, is it that much more effort to manually change flight profile in AutoFPS?

In any case, seeing that I enjoy a challenge, I could see if I can extend the VR/non-VR pairing logic I recently introduced, which looks for the same base profile name but one has a " VR" suffix, to do similar but with a " Xx" suffix for both and auto-switch to it. eg if you named one "IFR X1" and the other "IFR X4" I could have it detect them as a sim rate flight profile type pairing and auto-switch to between them when the detected sim rate changes and matches one of the suffixes. Does that sound suitable?

 

 

10 minutes ago, Reset XPDR said:

In my experience, scenery isn't able to load fast enough a sim rates like 4X and gets blurry, so IMO it is a moot point what TLOD you have set at the time as visual quality has already been compromised. Also, if you are manually switching sim rate by key presses, is it that much more effort to manually change flight profile in AutoFPS?

In any case, seeing that I enjoy a challenge, I could see if I can extend the VR/non-VR pairing logic I recently introduced, which looks for the same base profile name but one has a " VR" suffix, to do similar but with a " Xx" suffix for both and auto-switch to it. eg if you named one "IFR X1" and the other "IFR X4" I could have it detect them as a sim rate flight profile type pairing and auto-switch to between them when the detected sim rate changes and matches one of the suffixes. Does that sound suitable?

 

 

That sounds like a neat solution. I usually set sim rate via the Fenix MCDU or in the case of the PMDG/ini A350 it has auto-cruise where it adjusts sim rate on its own. So having AutoFPS detect sim rate >1x and then apply a light profile would help to free up system resources (and avoid issues with aircraft systems...I don't recommend flying 4x over NYC with TLOD400, it even has the potential to flip the Fenix on its head when FPS drop enough) and reduce TLOD via a special profile when a high value is not needed. When flying at 1x it would then still allow the benefits of a high TLOD when it's actually needed, so best of both worlds.

21 minutes ago, Speedbird 217 said:

That sounds like a neat solution. I usually set sim rate via the Fenix MCDU or in the case of the PMDG/ini A350 it has auto-cruise where it adjusts sim rate on its own. So having AutoFPS detect sim rate >1x and then apply a light profile would help to free up system resources (and avoid issues with aircraft systems...I don't recommend flying 4x over NYC with TLOD400, it even has the potential to flip the Fenix on its head when FPS drop enough) and reduce TLOD via a special profile when a high value is not needed. When flying at 1x it would then still allow the benefits of a high TLOD when it's actually needed, so best of both worlds.

OK, I'll have a go at it. Stay tuned!

I get this Error Message

I've been using AutoFPS since MSFS 2024 came out, but now I'm suddenly getting this error when running MSFS 24. I don't get the message in MSFS 2020. I've already deleted the WASM folder, as described...

16 minutes ago, Konderbt said:

I get this Error Message

I've been using AutoFPS since MSFS 2024 came out, but now I'm suddenly getting this error when running MSFS 24. I don't get the message in MSFS 2020. I've already deleted the WASM folder, as described...

Looks like it is time for Step 2, which is not as painful as it sounds for MSFS 2024. Instructions from the readme are as follows:

• If that doesn't fix it, a full clean reinstall of MSFS will be required, which can be done in less than 15 minutes for MSFS 2024 but may take many hours for MSFS 2020.
  • If reinstalling MSFS 2024, you need to do a clean install, as outlined for your MSFS version here.
    • Ensure you backup/relocate your Community folder BEFORE you do this, then put it back when the reinstallation is complete.
    • All your settings, controller assignments, career progression and your pilot profile are retained.

1 hour ago, Reset XPDR said:

It adjusts in steps of 5 FPS in my MSFS settings. You may also be able to set it to something in between by manually editing the UserCfg.opt file for the TargetFrameRate and TargetFrameRateVR settings.

Ok, good to know, thanks for the heads up. Still trying to find the best option for my situation with the fact, that I only get "issues" at my home airport (LSZH from MK Studios) in conjunction with the ini A350, where I simply do not reach my 72FPS limit, only if I turn down the settings quiet dramatically. Which I do not want of course, so in my case, the ideal situation would be accepting something like 60FPS (which can be achieved in above mentioned scenario) and still having the 72FPS for en route or any other scenario. So basically a AutoFPS setup that only starts acting if FPS are above 72, but not if they are below. Strange need, I know...

I was really surprised because I've been using autoFPS for a long time and never had any problems. I'll let you know if it works after reinstalling.

1 hour ago, Speedbird 217 said:

That sounds like a neat solution. I usually set sim rate via the Fenix MCDU or in the case of the PMDG/ini A350 it has auto-cruise where it adjusts sim rate on its own. So having AutoFPS detect sim rate >1x and then apply a light profile would help to free up system resources (and avoid issues with aircraft systems...I don't recommend flying 4x over NYC with TLOD400, it even has the potential to flip the Fenix on its head when FPS drop enough) and reduce TLOD via a special profile when a high value is not needed. When flying at 1x it would then still allow the benefits of a high TLOD when it's actually needed, so best of both worlds.

It turned out to be pretty simple to add to the existing VR/Non-VR flight type profile switching code. Update to 0.4.5.6-test16 here and give it a go.  Make sure you name two profiles the same, one with 1X and one with 4X suffixes (other values work too eg. 2X, 8X etc, as long as there is an actual matching sim rate) eg:

When the sim rate changes to 4X, it will auto-switch to the 4X profile and vice versa for 1X. Any undefined xX will just leave it on the profile it is currently using. Enjoy!

 

Edited September 10, 2025Sep 10 by Reset XPDR
Update to reflect change from Xx to xX in test16

23 minutes ago, Reset XPDR said:

It turned out to be pretty simple to add to the existing VR/Non-VR flight type profile switching code. Update to 0.4.5.6-test16 here and give it a go.  Make sure you name two profiles the same, one with 1X and one with 4X suffixes (other values work too eg. 2X, 8X etc) eg:

When the sim rate changes to 4X, it will auto-switch to the 4X profile and vice versa for 1X. Any undefined xX will just leave it on the profile it is currently using. Enjoy!

 

Wow - that's amazing! Thank you so much, will give this a try later today!

57 minutes ago, Reset XPDR said:

Looks like it is time for Step 2, which is not as painful as it sounds for MSFS 2024. Instructions from the readme are as follows:

• If that doesn't fix it, a full clean reinstall of MSFS will be required, which can be done in less than 15 minutes for MSFS 2024 but may take many hours for MSFS 2020.
  • If reinstalling MSFS 2024, you need to do a clean install, as outlined for your MSFS version here.
    • Ensure you backup/relocate your Community folder BEFORE you do this, then put it back when the reinstallation is complete.
    • All your settings, controller assignments, career progression and your pilot profile are retained.

I've done everything and I'm no longer getting the warning. BUT now I'm getting a warning that the Modi WASM module isn't found in the Community folder. I've already clicked "Update" several times in the installer, but I'm still getting an error message with a code...

35 minutes ago, Konderbt said:

I've done everything and I'm no longer getting the warning. BUT now I'm getting a warning that the Modi WASM module isn't found in the Community folder. I've already clicked "Update" several times in the installer, but I'm still getting an error message with a code...

If you didn't copy out your community folder and put it back, the mobiflight module won't be there. Installing the app with the clean install option checked should do the trick. If not, run the installer and select remove, then reinstall the app.