On 8/29/2025 at 7:29 PM, Lucky38i said:

Hi @Reset XPDR having a great time so far, was wondering if the expert settings can be graphics mode specific. For example I like to switch back to flat screen once in cruise and would like expert settings that are specific to NFR that I wouldn't use with VR.

As requested and further discussed, I have looked into auto-switching of profiles when using VR. As expected, the simplest solution is to use the existing profile structure and to use the name of the profiles to indicate a VR/non-VR pairing for auto-switching to be activated. To that end, I have updated AutoFPS in 0.4.5.6-test3 or later, available here, to allow auto-switching of flight type profiles in Expert mode when two profiles both share the same initial name and one of them has " VR" appended to it.

For example, here is my existing profile names, with none of them meeting this matching requirement and I want to configure User1 for that purpose:

 

Changing to the User1 profile, then double clicking on it to enter edit mode and renaming it to be paired in VR with the default IFR profile shows the following warning message to make sure you are aware that you have now configured auto-switching correctly:

 

The resultant profiles names will look like this: 

 

When you are in a flight session and using either of one of these VR/non-VR paired flight type profiles, the app will now auto switch between them within 5 seconds of when you switch in or out of VR.

As an added bonus, I have also made the app auto switch to VR as the target FPS type any time you are not in a flight session and change to any flight type profile ending with a " VR" suffix, as it should be a reasonable assumption that you are configuring for VR. It does not do this going to a non " VR" suffixed profile as there is more than one option you may wish to choose from and does not want to be presumptious with an auto selection.

Let me know if this satisfies your request.

14 hours ago, Evan said:

It seems like the taxiway lines are only being drawn out a little ways before me when taxiing and the popping in as I approach. Is there a way to fix this? I just use IFR and auto settings in the app.

That can sometimes happen when using lower TLODs, which you have traded to get the target FPS you desire. If you increase your TLOD you may improve this but then may not achieve your target FPS, so you need to choose what is more important to you.

6 hours ago, ankh21 said:

May i ask a question: 
I use the Cap option, with FG on limited to 60/sec. Works like charm. But sometimes, AutoFPS tries to increase the TLOD, framerate drops a little bit, but TLOD is lowered more than it has been before. For example, i am at FL400 over Germany, which seems to be very demanding on TLOD. So I am very happy seeing a TLOD of 275 or even 300. Then, AutoFPS starts a new seeking phase, but after increasing just a little bit, 280 or 305, it decreases instantly to 225 or 250. So I end up with less TLOD than before. It makes sense to lower TLOD significantly to stabilize frames in demanding situations, but is there a way to recover to the level before? Or to decrease in smaller steps?

Thank you so much!

Matthias

When doing a reseek, the app is looking for the highest TLOD it can achieve while still maintaining a minimum TLOD headroom, the default value of which is 25. The default of 25 was chosen through significant testing of the app in real flight conditions to minimise how often the app changes TLOD and therefore improve smoothness overall.

If at any time during the reseek the FPS drops below your target FPS, it immediately ends the seek and deducts that minimum TLOD headroom in order to reduce the chance of any further TLOD reductions in the immediate future. If it is reducing the TLOD after doing a reseek compared to what you had before, that is telling you that your system was running a bit too close to the performance edge at the time and has backed it away for you.

If you think a 25 minimum TLOD headroom is too much, by all means look for the following line in the config file:

  <add key="TLODBasePlusSeekMinHeadroom" value="25" />

and reduce it to whatever you want to (no lower than 5 though). Just be aware that by doing so your system will run closer to the performance edge and is therefore much more likely to auto decrease more often, which may in turn increase stutters.

Hi All,

Its been a while since I've used AutoFPS and I must say its become a little more.... "complicated" than when I last used it. Hoping for some guidance....

I can maintain around 60 FPS with FSR FG running. So a native 30 FPS and a FG 60 FPS. My objective is to have AutoFPS set the TLOD to 50 and OLOD 100 when on the ground  and gradually increase TLOD to 200 when in flight and reduce OLOD to 20. I would also like AutoFPS to increase clouds from High to Ultra when I'm maintaining 60 FPS.

Using AutoTLOD (which I though from reading the manual would be what I wanted) doesn't seem to do what I need as when I'm able to maintain 60 FPS on thhe ground, ity just keeps increasing TLOD. So I thought maybe FPS Cap was the way forward as it appears to show the settings I want, only problem is I can't get it to increase clouds from High to Ultra even when FPS are being easily maintained. 

Below is a screenshot of my settings, can anybody tell me why Clouds might not be increasing?

 

Cheers

 

EDITED TO ADD:

Not sure what I'm doing wrong here, but its finally adjusted up the cloud setting, but for some reason has doubled to TLOD from the 200 I was expecting (and set) to 400.... Could it be due to me running a triple monitor setup or frame generation?

Edited August 31, 2025Aug 31 by KL Oo

3 hours ago, Reset XPDR said:

As requested and further discussed, I have looked into auto-switching of profiles when using VR. As expected, the simplest solution is to use the existing profile structure and to use the name of the profiles to indicate a VR/non-VR pairing for auto-switching to be activated. To that end, I have updated AutoFPS in 0.4.5.6-test3 or later, available here, to allow auto-switching of flight type profiles in Expert mode when two profiles both share the same initial name and one of them has " VR" appended to it.

For example, here is my existing profile names, with none of them meeting this matching requirement and I want to configure User1 for that purpose:

 

Changing to the User1 profile, then double clicking on it to enter edit mode and renaming it to be paired in VR with the default IFR profile shows the following warning message to make sure you are aware that you have now configured auto-switching correctly:

 

The resultant profiles names will look like this: 

 

When you are in a flight session and using either of one of these VR/non-VR paired flight type profiles, the app will now auto switch between them within 5 seconds of when you switch in or out of VR.

As an added bonus, I have also made the app auto switch to VR as the target FPS type any time you are not in a flight session and change to any flight type profile ending with a " VR" suffix, as it should be a reasonable assumption that you are configuring for VR. It does not do this going to a non " VR" suffixed profile as there is more than one option you may wish to choose from and does not want to be presumptious with an auto selection.

Let me know if this satisfies your request.

Absolutely fantastic, I’ll give this a try the next time I do a flight, thank you

3 hours ago, Reset XPDR said:

If it is reducing the TLOD after doing a reseek compared to what you had before, that is telling you that your system was running a bit too close to the performance edge at the time and has backed it away for you.

If you think a 25 minimum TLOD headroom is too much, by all means look for the following line in the config file:

  <add key="TLODBasePlusSeekMinHeadroom" value="25" />

and reduce it to whatever you want to (no lower than 5 though). Just be aware that by doing so your system will run closer to the performance edge and is therefore much more likely to auto decrease more often, which may in turn increase stutters.

Oh,wow, thank you so much for this excellent explanation! That’s I like most with your support, you always explain what the software is doing and why. 
But I just forgot that there is a config file to look at. I will try to adjust the mentioned line a little bit. Running the system close to its limits is all we want since the first day of Flight Simulator 😂

Hello,
I switched from MSFS_DynamicLOD to MSFS_AutoFPS, still with the goal of eliminating landing stutters, and it works really well. Thank you so much @Reset XPDR.

I configured it to have a base TLOD of 40 up to 400 Ft. Between 400 Ft and 2,500 Ft, it will increase in increments of 5 up to 250.

The problem I'm having, and I don't know how to solve it, is that in all configurations, MSFS_AutoFPS exceeds the Top TLOD:

If you have an explanation, or better yet, a solution, I would be very grateful. Thank you in advance.

 

Edited August 31, 2025Aug 31 by Area

31 minutes ago, Area said:

Hello,
I switched from MSFS_DynamicLOD to MSFS_AutoFPS, still with the goal of eliminating landing stutters, and it works really well. Thank you so much @Reset XPDR.

I configured it to have a base TLOD of 40 up to 400 Ft. Between 400 Ft and 2,500 Ft, it will increase in increments of 5 up to 250.

The problem I'm having, and I don't know how to solve it, is that in all configurations, MSFS_AutoFPS exceeds the Top TLOD:

 

If you have an explanation, or better yet, a solution, I would be very grateful. Thank you in advance.

 

 

Looks like the same issue I'm having two posts up from yours..... No idea what I'm doing wrong. 

Isn’t that’s the way it works? You are in FPS Cap mode with IFR. So, if your system easily achieves the set TLOD of 200, it increases the TLOD up to 2x of your limit, so you end up with 400 or 500 when your limit is set to 250 before. 
The upper limit should be the TLOD setting your system can run on in nearly every situation. 
If you want to stop at 200, you have to use another mode i guess. 
The readme is very detailed, so perhaps you will find another mode stopping at your given limit. Or you set your upper TLOD limit to 100 or 125, so you will see 200 or 250 with cap and IFR.

Edited August 31, 2025Aug 31 by ankh21

@Area& @KL Oo, as @ankh21says, the lovingly crafted, oft ignored readme covers this:

 

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.

If you don't want TLOD to go above the TLOD Top you set, change to Auto TLOD mode and uncheck TLOD Base +, but if you do you are essentially missing out on free extra TLOD when performance conditions are very favourable.

--- Error ---  

 

Edited August 31, 2025Aug 31 by Area

@ankh21  Thank you very much for the explanation.
@Reset XPDR  Thank you very much for the solution.

Both of you, don't think I didn't read the readme; you'd be making a mistake. But you'll recognize that the MSFS_AutoFPS readme is not comparable to the recipe for cooking pasta. Thus, between reading and understanding, there is a gap that can be more or less extended by two components: first, the technical level of the document written, and second, the reader's level of knowledge and mastery of the subject.
As far as I'm concerned, this gap is very significant. Example:

"The following guidelines should be observed to obtain the best results 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 to the entire altitude program, potentially allowing a doubling of TLOD Top if performance conditions are favorable, so be especially careful when setting TLOD Top."

First, it needs to be translated (thanks, Google Translate), as the translator "makes do" with overly technical terms, and then you need to understand the words first (worst-case, TLOD Base +, etc ) , then how they fit together: the sentences.

But I'm working, I'm working... As written above, I understood the explanation, the solution, and the subtleties of the settings (text in "green").

Thank you again for your help.

Edited August 31, 2025Aug 31 by Area

As they mentioned, they were using the DynamicLOD before, where there is just a adjustment depending on given steps. But the BIG advantage of AutoFPS is the „auto“ 😂

And I can strongly recommend to read the readme. It’s long, but written very systematic. So really most of the questions here are answered there already! At the beginning I was experimenting a lot, but settings fitting to one situation were not ideal in another situation. After really working with the readme, I now have a setting perfect for my system and needs. And I am just doing boring IFR flights. The potentials of this marvelous peace of software are much bigger, seeing the latest version e.g.  

1 minute ago, Area said:

@ankh21  Thank you very much for the explanation.
@Reset XPDR  Thank you very much for the solution.

Both of you, don't think I didn't read the readme; you'd be making a mistake. But you'll recognize that the MSFS_AutoFPS readme is not comparable to the recipe for cooking pasta. Thus, between reading and understanding, there is a gap that can be more or less extended by two components: first, the technical level of the document written, and second, the reader's level of knowledge and mastery of the subject.
As far as I'm concerned, this gap is very significant. Example:

"The following guidelines should be observed to obtain the best results 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 to the entire altitude program, potentially allowing a doubling of TLOD Top if performance conditions are favorable, so be especially careful when setting TLOD Top."

First, it needs to be translated (thanks, Google Translate), as the translator "makes do" with overly technical terms, and then you need to understand the words first (worst-case, TLOD Base +, etc ) , then how they fit together: the sentences.

But I'm working, I'm working... As written above, I understood the explanation, the solution, and the subtleties of the settings (text in "green").

Thank you again for your help.

Oh, tell an Italian that cooking pasta is easy 🫣

Beside of jokes, I think, that asking a question is never wrong! And the author shows on so many pages, that is is always willing to give assistance and explanations! And if you need to translate the Readme to another language, there is double of work for you, so anybody will call you lazy. So my apologies if my answer before sounded like an accusation, that was not my intention! 

It wasn't interpreted as a negative comment - no problem.

Edited August 31, 2025Aug 31 by Area