2 minutes ago, TomCYYZ said:

Thanks for the fast reply! I will try running FPS Cap with your suggestions. With regard to the FPS decrease I did a little googling and was wondering if this could be a contributing factor as well: 

Frame Generation Inactivity: When MSFS loses "true" window focus (e.g., when interacting with menu overlays or using an external application), MSFS Frame Generation (FG) often shuts down, reducing FPS by half or more.

Yes, this is what I am saying. In fact, with MSFS I can guarantee that the FG multiplier gets removed when the MSFS window loses focus. Even the in-game FPS view shows this.

On 3/31/2026 at 9:01 PM, Reset XPDR said:

 

hi again, i think the calculation for this warning might be wrong (screenshot below). 42*4 is less than 100*2

i'm still not quite where i'd like to be with the app, which would be: single set+forget config where my TLOD is set between my ideal min for heavy cities (~30 TLOD), and my ideal max for all other scenarios (~165 TLOD), regardless of altitude, based on delta from target FPS.

The current extra multipliers are a bit limiting as i'd need a mult of ~5.5x to achieve that range, so supporting other mults might help me with one part, and i assume if i set base min*extra to be the same as top min * extra, then i should achieve the "regardless of altitude" part too

also not sure if its intentional for the performance optimiser to be quite hidden in the UI? It took me a while to find

 

1 hour ago, cjk28 said:

hi again, i think the calculation for this warning might be wrong (screenshot below). 42*4 is less than 100*2

The warning is correct. It is not TLOD Total being compared, it is TLOD Extra, and in this case 42*3=126 is larger than 100*1=100. Reducing the Base multiplier to 3 as the warning advises, now gives 42*2=84 which is now less. 

1 hour ago, cjk28 said:

i'm still not quite where i'd like to be with the app, which would be: single set+forget config where my TLOD is set between my ideal min for heavy cities (~30 TLOD), and my ideal max for all other scenarios (~165 TLOD), regardless of altitude, based on delta from target FPS.

The current extra multipliers are a bit limiting as i'd need a mult of ~5.5x to achieve that range, so supporting other mults might help me with one part, and i assume if i set base min*extra to be the same as top min * extra, then i should achieve the "regardless of altitude" part too

When the app was originally made for MSFS 2020 it did allow free ranging TLOD at any altitude and the overwhelming feedback from users, and my own observations, was that this was a bad idea as changing TLOD at low altitude often led to severe stuttering and FPS variations. I do not intend revisiting this. 

1 hour ago, cjk28 said:

also not sure if its intentional for the performance optimiser to be quite hidden in the UI? It took me a while to find

The performance optimiser is the first control on the UI, so pretty obvious IMO. If you mean the sub controls for this feature, then yes they intentionally only show when you hover your mouse over the option checkbox, so I don't annoy users with controls they don't currently care about.

@Reset XPDR everithing is working great. Do you suggest that I download the latest version?

v0.4.6.6 is my current version.

2 hours ago, Reset XPDR said:

The warning is correct. It is not TLOD Total being compared, it is TLOD Extra, and in this case 42*3=126 is larger than 100*1=100. Reducing the Base multiplier to 3 as the warning advises, now gives 42*2=84 which is now less. 

 

hm i get the error here changing base extra from 3x to 4x, so still seems wrong to me

6 hours ago, cjk28 said:

hm i get the error here changing base extra from 3x to 4x, so still seems wrong to me

42*(4-1)=126 > 200*(1.5-1)=100, so the math is correct. Again, it is comparing Extra not Total TLOD ie. You must subtract the original TLOD.

In fact, here is the actual code:

 

float baseExtra = MinTLOD[activeProfile] * (MinTLODExtraCapMult[activeProfile] - 1);
float topExtra = MaxTLOD[activeProfile] * (MaxTLODExtraCapMult[activeProfile] - 1);

if (baseExtra > topExtra)
   {
   string messageBoxText = "TLOD Base Extra cannot exceed TLOD Top Extra. ";
   ...

 

 

 

Edited April 9Apr 9 by Reset XPDR

8 hours ago, CFIJose said:

@Reset XPDR everithing is working great. Do you suggest that I download the latest version?

v0.4.6.6 is my current version.

I generally recommend that users always update to the latest release version. because even though older app versions may still be compatible with MSFS I have potentially made improvements or fixed bugs you are not aware of associated with the features you currently use. With auto updates, I have made the update process as automated an non-intrusive as possible, so it is very easy to stay up to date. 

15 hours ago, cjk28 said:

I'm still not quite where i'd like to be with the app, which would be: single set+forget config where my TLOD is set between my ideal min for heavy cities (~30 TLOD), and my ideal max for all other scenarios (~165 TLOD), regardless of altitude, based on delta from target FPS.

I've had a rethink on this. I believe I can come up with a way to give you what you want without too much tweaking of the code and am working on that now as I have a bit of spare time. As with other one-off changes like this, it will likely be activated by you putting a phrase in your profile name eg. "FreeTLOD" that the app will look for and configure accordingly rather than an explicit control on an already-busy UI. I will get FPS Cap mode working with this first, as that is really what you should be using with 40 FPS cap for VR as you want to stay as close to that cap as possible.

Edited April 10Apr 10 by Reset XPDR

Lol, I should have gone with my Spidey senses - I've had to have a rethink on my rethink. What initially looked like "without much tweaking" very quickly escalated into having to make many small changes in a lot of places, some of which have side effects with existing functionality, especially when switching back to it. I do not want to jeopardise existing functionality in any way so unfortunately I am going to have to back out of my offer to try and implement an altitude independent TLOD mode.

 

 

I have noticed in recent days that my graphic settings keep being changed by AutoFPS.

I have checked the settings and I can't figure it out. Everything was previously just left with expert unticked and the settings are being changed/nuked. I ticked Auto Reduce and unchecked all settings but corrections are still being applied to everything? Basically I don't want the clouds etc to be changed, just TLOD.

It's slightly annoying as the clouds especially now look awful as the app is nuking my settings. I could set the FPS target higher maybe but then surely the tool loses its point? For some reason it is just nuking everything repeatedly.

Maybe I'm doing something wrong or something is broken?

Edited April 10Apr 10 by G MIDY

13 minutes ago, G MIDY said:

I have noticed in recent days that my graphic settings keep being changed by AutoFPS.

I have checked the settings and I can't figure it out. Everything was previously just left with expert unticked and the settings are being changed/nuked. I ticked Auto Reduce and unchecked all settings but corrections are still being applied to everything? Basically I don't want the clouds etc to be changed, just TLOD.

It's slightly annoying as the clouds especially now look awful as the app is nuking my settings. I could set the FPS target higher maybe but then surely the tool loses its point? For some reason it is just nuking everything repeatedly.

Maybe I'm doing something wrong or something is broken?

Okay I fixed this (I think).

I needed to kill the app, change MSFS graphics settings, close MSFS and then run everything again with AutoFPS.

I should maybe read the popup better!

Edited April 10Apr 10 by G MIDY

8 minutes ago, G MIDY said:

I have noticed in recent days that my graphic settings keep being changed by AutoFPS.

I have checked the settings and I can't figure it out. Everything was previously just left with expert unticked and the settings were being changed. I ticked Auto Reduce and unchecked all settings but corrections are still being applied to everything?

It's slightly annoying as the clouds especially now look awful and I can't get it to stop unless I just don't run the app. I could set the FPS target higher maybe but then surely the tool loses its point? For some reason it is just nuking everything repeatedly.

Maybe I'm doing something wrong or something is broken?

Are you following the advice in the message box? Do not try to change MSFS graphics settings while in a flight session otherwise the app will change them back to what they were when the flight first loaded or what it thinks they should be from what it has changed. 

If you are only changing your settings when in the main MSFS menu and still experiencing settings being changed permanently, PM me your associated log file, located in %appdata%\MSFS_AutoFPS\log, and I will take a look.

1 minute ago, G MIDY said:

Okay I fixed this (I think).

I needed to kill the app, change MSFS graphics settings, close MSFS and then run everything again with AutoFPS.

I should maybe read the popup better!

Yes, that is correct except you don't actually have to kill the app. Just don't be in a flight session if you want to change settings the app may potentially manage. You can be in the flight or main menu and change them with the app running, just not in an actual flight.

@cjk28, and anyone else for that matter, if you are interested in seeing what free ranging TLOD in FPS cap works like in the now discarded 0.4.6.8 experimental version I was working on yesterday, rather than just throw it out you can try it out here, which is not on the usual auto update path. It works in this new mode but, as I state in the description, it has an awkward UI implementation that I did not wish to continue with. Normal use of the app should still work, but no guarantees. It is simple enough to revert to 0.4.6.7 by downloading and installing from here. If you do stick with it, when I release newer versions of 0.4.6.8 it should allow auto updating to them but again if not just go back to 0.4.6.7 and go from there.

Instructions to set up are:

Added FreeTLOD option:

• Enabled when "FreeTLOD" is contained within the Flight Type profile name in FPS Cap automation mode.
• Forces Start Max when "Max" is also contained within the Flight Type profile name.
• Allows TLOD multipliers up to 8x.
• Ignores altitude constraints, short circuits minimum TLOD increase time requirements, and allows TLOD to freely range between TLOD Top Min and TLOD Top Max (TLOD Top Min x multiplier).

Also note that the TLOD Min Altitude setting has no effect. In this mode altitude is effectively set to 100,000ft regardless of what MSFS says it actually is.

I tried it for a little while around KLAX and found that when landing from the West there were lots of undesireable stutters and pauses as TLOD marched down on final approach, which was why TLOD Base Min at a set altitude before landing was created, but in remote areas it probably works OK. Anyway, let me know what you think if you try it.

 

There have been a couple of downloads of the experimental version, so if you are one of them let me know what you thought of free ranging TLOD. I used it in this mode for a couple of hours in MSFS 2024 doing a VFR flight around Japan yesterday and it was actually pretty good, despite there being a lot of photogrammetry in the area, with not too many stutters from TLOD changing at low altitude and on the ground. MSFS 2024 is a lot more tolerant of rapidly changing TLOD than MSFS 2020 is, especially given that dynamic settings does this as a matter of course, so major stuttering may no longer be an issue like it was with MSFS 2020 a few years ago.  

Since I have now started the 0.4.6.8 test program properly, with the release of 0.4.6.8-test1 just now, I will take down the experimental version as the new test version takes the app in a different direction with trialing Auto FPS Cap detection in FPS Sensitivity mode, possibly doing away with the existing FPS Cap mode if it works well enough which may also lead to a free ranging TLOD option, and I don't want to cause any confusion of where this is now heading.

Edited April 12Apr 12 by Reset XPDR