1 hour 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, 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!

 

Testing now - works perfectly!! I've created 1x, 4x and 8x profiles...it switches automatically. Such a great feature and thanks for implementing it so quickly! You really have one of the best tools for MSFS and great support!!

9 hours ago, Reset XPDR said:

Was that with dynamic settings enabled in the latest test version?

I have tried with the dynamic settings enabled yet. I take it that using this in conjunction helps the changes faster while still having some control over tlod? Dynamic settings in the sim seem to make heavy changes to the point where the tlod was changed too fast or made the tlod seem really low in lower fps scenerios. I guess i will try that next. I use autofps fps cap to "5" and left the olod alone. 

 

2 hours ago, Reset XPDR said:

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.

I moved everything and choosed it right but MSFS 24 didnt want to accept it but now i got it. Now i want to add Auto Start as before. But if i wanted to do this via the Installer it says "Failed to add Auto-Start".

7 hours ago, Reset XPDR said:

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. 

Is this primarily for VR use?

15 hours ago, Reset XPDR said:

App users are reporting much smoother results during takeoff and landing phases with the new hybrid dynamic settings capability enabled in 0.4.5.6-test, so you may want to give that a try. 

If you want to give it a go, download and install from here (or click the + Tests checkbox next to auto updates, restart the app and it will auto update). Then enable by setting ExperimentalFeatures to true in MSFS_AutoFPS.config in the app root install directory prior to running the app, turn on dynamic settings in MSFS settings and set the target FPS for it to 60. Let me know how you go if you try it.

Thanks for the suggestion. I gave it a try but unfortunately I did not see any real difference. I'm still getting the small stutters on takeoff. Since using FSR 3 FG in the FS2024 settings disables V-Sync, then I assume V-Sync should also be set to Off in Nvidia control panel, or at least set to Use the 3D application setting. 
Thanks for your tireless work on Auto FPS!
Al

New beta aaaaaand broken again @Reset XPDR 🤣

I can imagine how annoying it can be... 

40 minutes ago, roi1862 said:

New beta aaaaaand broken again @Reset XPDR 🤣

I can imagine how annoying it can be... 

I was wanting to do a test flight tonight with the new SU4 beta but since it updated again and AutoFPS no longer works I guess that flight is quickly disappearing.  Problems also with non moving jetways

26 minutes ago, cj-ibbotson said:

I was wanting to do a test flight tonight with the new SU4 beta but since it updated again and AutoFPS no longer works I guess that flight is quickly disappearing.  Problems also with non moving jetways

I am sure our man Reset XPDR will update it quickly as always. MS/Asobo should hire him instead of many others they did... 

All the sudden, I can't click the "Auto reduce settings" for VRAM +. I had it working in the past, but all the sudden, it's not checkable. I wasn't using CPU-Z in the past when I was able to check the box, so I figured that might be why it isn't working now for some reason, so I'm running CPU-Z now and I still can't use that function. Any thoughts? Im on MSFS 2024, SU3. 

Ahh this app is getting so confusing these days.

Just woke up. Looking in to the SU4 breakage now. I really wish MS/Asobo would stop changing the memory map so often, but it is a beta so fair game I guess.

Then just do what every developer who wants to preserve their sanity does:

Don't update for Betas and wait until SU4 is released. 😉

Disregard my previous message. I had "Auto Target FPS" box checked. 

1 minute ago, Farlis said:

Then just do what every developer who wants to preserve their sanity does:

Don't update for Betas and wait until SU4 is released. 😉

I don't mind as users are generally patient and then grateful that I support MSFS betas. Well, except for that one user who is demanding that I make the app more bulletproof to memory map changes that I can't possibly forsee. That gets a bit annoying.

 

I won’t use 2024 without the app. So there’s that 😂.