2 hours ago, scotchegg said:

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.

I am pretty sure it is TLOD. MSFS 2024 is somewhat nerfed compared to 2020 when it comes to tree draw distance.

I may be wrong but autofps seems to be triggering cockpit LOD issues in VR in inbuilds  a350 . Similar to what was seen in SU3 now fixed in SU4. Turning off issue disappears . This is with SU4 beta . Temporarily had to turn off to use. 

18 minutes ago, cannow said:

I may be wrong but autofps seems to be triggering cockpit LOD issues in VR in inbuilds  a350 . Similar to what was seen in SU3 now fixed in SU4. Turning off issue disappears . This is with SU4 beta . Temporarily had to turn off to use. 

Unfortunately, I don't have the inBuilds A350 so I am unable to reproduce. What specific cockpit LOD issues are you referring to? It would also be helpful to know what sim values AutoFPS is showing and  whether auto settings reduction is active or not when this is occurring.

Hello

Is GPU-Z still needed?

Kind regards

Ramon

12 minutes ago, Metall4You said:

Hello

Is GPU-Z still needed?

Kind regards

Ramon

Per the readme, which is updated with each new version, GPU-Z is only needed if you want to use the GPU load method for cloud reduction with MSFS 2020 and/or VRAM+ for both MSFS 2020 and 2024. 

On 10/30/2025 at 2:44 AM, Reset XPDR said:

I am pretty sure it is TLOD. MSFS 2024 is somewhat nerfed compared to 2020 when it comes to tree draw distance.

Really wish MSobo would let us tweak a few settings like certain LOD objects. 

All's fairly quiet on the AutoFPS front, so I thought I would take the opportunity to prototype a rework of the Expert options UI panel to be cleaner and more descriptive for TLOD and OLOD settings. By cleaner I mean grouping like items together and by more descriptive I mean using these savings to provide textual abbreviations instead of the + and - nomenclature previously used.

First, a side by side comparison of the old and proposed new:

As you can see, I have grouped each LOD setting with its corresponding altitude component, which means I can be more descriptive with TLOD options and remove an entire line with OLOD options. 

The TLOD options map as follows: 

• "+" after TLOD Min, being the old TLOD Min Extra symbol, is replaced with the more descriptive "Extra" label and a new multiplier drop down which will allow you to set what multiple of TLOD Min is allowable under favourable performance conditions. Previously, you were limited to either disabled (ie. 1X) or enabled (2X but changeable in the config file for VFR or IFR flight types).
• "+" prior to TLOD Max, being the old Mountains Extra symbol, is replaced with the more descriptive "Mtns" label.
• "-" after TLOD Max, being the old Half TLOD Max at Night, is replaced with the more descriptive "Night÷2" label.  

I have highlighted the "ft" label for TLOD Max in the prototype as I am strongly considering doing away with the Avg Descent Rate setting, which is used to calculate Alt TLOD Top, and replacing it with the same actual Alt TLOD Top setting that is used in Auto TLOD and FPS Cap modes. Average descent rate was initially chosen as MSFS 2020 was particularly sensitive to large TLOD reductions and this provided a dynamic calculation to Alt TLOD Top that aimed to minimise TLOD reductions to the TLOD step size. MSFS 2024, which most AutoFPS users are now using, is far more tolerant of large TLOD reductions that could inadvertently be triggered by a user's settings, hence IMO it is now acceptable this transition be made.

To ease the Alt TLOD Top transition, I propose to have the app automatically set the new Alt TLOD Top setting to what a user's existing current settings would have calculated this value to be for all FPS sensitivity and tolerance mode profiles, rounded up to the nearest 500 ft. Additionally, a tooltip will be provided with this new Alt TLOD Top setting that shows at a quick glance what the calculated average descent rate corresponding to this altitude will be.

Anyway, I am just spit balling these changes at this time, so nothing is set in concrete. None of them change core functionality of the app and the aim is to make the UI more intuitive as to what settings actually do, particularly for new users of the app.

Any feedback on these proposed changes would be appreciated. 

Edited November 8, 2025Nov 8 by Reset XPDR

I dig it!

can't autoupdate the app bcs it stopped deleting the older version

 

 

1 hour ago, motishow said:

can't autoupdate the app bcs it stopped deleting the older version

 

 

That looks like a manual install, not an auto update. In any case, the likely reason the installer is unable to delete the old app version is because one or more files in the app's bin directory is currently locked by another process. Try rebooting and run the installer again. If you still have the issue, reboot again, delete the folder %appdata%\MSFS_AutoFPS\bin, then run the installer again.

Nice. Looking forward to these changes!

I've said this countless times but this app is a sim changer. Even with beefy systems having traffic, apps, etc and this really fine-tunes our needs to keep performance decent at all times. I have stopped using dynamic settings as it drops the TLOD down too low (I originally have it set to 150) so I just use your app. Keep my monitor at 70hz and fps target at 66. Sensitivity is set to 3. Min is 45 for IFR and 80 for VFR. I dont change clouds or OLOD. FPS in the sim is capped at 70.

Feedback on these proposed changes seem positive so far, so I have been working on the supporting logic as well as some slight changes to what was originally proposed, namely enabling checkboxes for the Extra options which make the multiplier disappear when disabled and putting the labels for these new checkboxes after the checkbox, consistent with most other checkboxes in the app.

I am planning on revising the terminology used for TLOD limits in FPS Cap mode. Currently, the terms TLOD Base and TLOD Top are used in place of TLOD Min and TLOD Max, respectively. While most users correctly interpret TLOD Base as the effective minimum, fewer realise that TLOD Top is also a minimum — just one applied at higher altitudes. This is because both FPS Cap and Auto TLOD modes follow a fixed TLOD/altitude schedule, similar to Auto OLOD.

In contrast, TLOD Max (used in Sensitivity and Tolerance modes) represents the true upper bound that TLOD can reach if performance allows. This distinction becomes critical when TLOD Extra is involved:

• In FPS Sensitivity and Tolerance modes, TLOD Extra only affects TLOD Min, since TLOD can freely scale up to TLOD Max.

• In Auto TLOD and FPS Cap modes, TLOD Extra applies to the entire fixed schedule — meaning both TLOD Base and TLOD Top are treated as fixed minimums. The actual TLOD Max in this mode is much higher than TLOD Top, currently hardcoded to be 2× TLOD Top

As such, I propose the following terminology updates to clarify TLOD behaviour across modes:

• Sensitivity and Tolerance Modes: Rename TLOD Min and TLOD Max to TLOD Base Min and TLOD Top Max to reflect their fixed range. TLOD Base Extra will still default to disabled, with ×2 and higher multipliers available when enabled — provided that Base Min + Extra remains below Top Max.

• Auto TLOD Mode: Rename TLOD Base and TLOD Top to TLOD Base Min and TLOD Top Max. Remove TLOD Base Extra, as enabling it makes this mode functionally identical to FPS Cap Mode. 

• FPS Cap Mode: Rename TLOD Base and TLOD Top to TLOD Base Min and TLOD Top Min, clarifying both are fixed minimums. TLOD Base Extra will default to ×2, with lower and higher multipliers available — provided that Base Min + Extra remains below Top Min. Introduce a separate TLOD Top Extra multiplier to define the upper limit, up the app's TLOD limit of 1000, as defined in the common config file.

• Mountains Extra: Redesigned expanded mountains extra settings line to be consistent with the new style of TLOD and OLOD settings. 

Here's what it currently looks like:

TLOD Sensitivity (same as Tolerance) Mode, with Mountains Extra enabled to show the expanded settings line and the revised OLOD settings line (no change since recently redesigned):

Auto TLOD Mode, showing TLOD Extra no longer an option as FPS Cap provides that functionality:

FPS Cap Mode, showing the new TLOD Top Min terminology and showing the tooltip for the multiplier which shows what resultant TLOD Min or Max achievable with Extra for that multiplier:

Finally, FPS cap also has a requirement that at least one of the Extras must be enabled, otherwise you may as well be using Auto TLOD mode, so an appropriate advice message is provided if you try to disable both Extras. eg. The following screenshot is what you see if you try to uncheck TLOD Top Extra with TLOD Base Extra already disabled.

It is still a work in progress, but I am quite pleased with the redesign and I hope that others are too. If not, let me know and why.

 

 

 

Wow these changes look great......I took a little break from simulator stuff but the changes over the last month and this new stuff are amazing.

Like others have said "AUTO FPS" is a real game changer for MSFS. Amazing work you have done.

Time for me to get back into the AUTO FPS testing.

 

Great program

 So Glad you are able to keep updating it.

I have found that I have suffered from Audio Stutters/Pops/Crackles especially in large PG Areas big cities with the Fenix/PMDG 777 .

 When playing around if I tick the TLOD Top Box to 200 rather than let it get up to 500 plus that actually stops pretty much all of the Pops so I tick that on departure and arrival its interesting to see if the TLOD gets up to the 500+ range the main thread suddenly has more red spikes and then you get one big one and that creates the Audio Crackle which is really annoying. I also notice its tied with how much donwnload speed its trying to accomodate at the same time that usually goes red too..

I am using FPS Cap FSR3 @30FPS 60HZ Monitor running an AMD 7900X3D, Nvidia 4800

 

Would be interested if anyone else has found that correlation.

I have read the manual but still slightly confused what the different benefits are of the 4 Auto Methods are and if one is best or they all work well has one done a tutorial with the different settings? To help with the pops I am trying to keep the main thread from being overwhelmed. Maybe that is why you want to make these changes above?

 

Hamish

 

 

2 hours ago, Hamish100 said:

I have read the manual but still slightly confused what the different benefits are of the 4 Auto Methods are and if one is best or they all work well has one done a tutorial with the different settings? To help with the pops I am trying to keep the main thread from being overwhelmed. Maybe that is why you want to make these changes above?

I haven't made a tutorial nor have I come across any. In any case, it is pretty simple and the first bulltet point for Auto Methods pretty much sums up when to use each of them, and this will not change with the UI changes I have been recently discussing:

• Auto Method - FPS Sensitivity generally gives the best results for most users and hence is the default. Use FPS Tolerance if you experience stuttering issues. Use Auto TLOD if you want a DynamicLOD-like experience. Use FPS Cap if you use an FPS cap on your system.

2 hours ago, Hamish100 said:

I have found that I have suffered from Audio Stutters/Pops/Crackles especially in large PG Areas big cities with the Fenix/PMDG 777 .

While this was an issue for many of us a few months ago with the state of MSFS 2024 at the time, I have not read of reports of this since then with either MSFS 2020 and 2024. Every user's system is different, so it is difficult to know what is causing this issue on you and not for others. At least you have found that by limiting TLOD Top you are able to resolve it.

BTW, when you say the following, what do you mean by "Tick the TLOD Top box", since TLOD Top is a text, not a check, box?

Quote

When playing around if I tick the TLOD Top Box to 200 rather than let it get up to 500 plus that actually stops pretty much all of the Pops so I tick that on departure and arrival