What settings do I need to do for the app not to change the TLD when flying close to moutains, but have it change when landing at an airport when close the the ground. I have  my min sert to 50 and max 200 want to leave it at 200 when flying close to moutains like when deceending into KJAC, I notice that my TLD was droping to around 50

5 hours ago, Bill A said:

What settings do I need to do for the app not to change the TLD when flying close to moutains, but have it change when landing at an airport when close the the ground. I have  my min sert to 50 and max 200 want to leave it at 200 when flying close to mountains like when decending into KJAC, I notice that my TLD was droping to around 50

I am new to Auto FPS, but it would seem your problem is that close to mountains IS close to ground! 
My understanding is the TLOD Base value of 50 happens when you are below your Alt TLOD Base value, so if currently that latter setting is say 1000ft, you could lower that value (min for the setting is 100ft) so you would have a TLOD greater than 50 when closer that 1000ft to mountains. You could also raise the TLOD Base value above 50. 

Another possibility to do what you are asking would be to have the app detect, in addition to altitude AGL, that the plane is also close to landing, e.g., the gear is down, or flaps are at their max setting, or power is reduced, etc, before lowering the TLOD detail below some value. But I'm getting above my pay grade now! 

I expect other more experienced Auto FPS users here will likely have some good suggestions.

Al

Edited June 6, 20251 yr by ark

See the new test version. Will likely try this on Tuesday. However, I have never been able to get RTSS to find the msfs 2024 exe file. It says I am not authorized. New administration etc. I am the admin hahaha

3 minutes ago, Sonosusto said:

See the new test version. Will likely try this on Tuesday. However, I have never been able to get RTSS to find the msfs 2024 exe file. It says I am not authorized. New administration etc. I am the admin hahaha

The RTSS FPS source is optional, so not the end of the world if you can't get it working. It does seem to provide more consistent FPS data than MSFS does via Simconnect and, apart from LSFG, gives correctly scaled frame generation FPS natively, so it actually simplifies the code.

Schould RTSS running in the background?

6 hours ago, Sonosusto said:

See the new test version. Will likely try this on Tuesday. However, I have never been able to get RTSS to find the msfs 2024 exe file. It says I am not authorized. New administration etc. I am the admin hahaha

Open RTSS, Run MS2024, go RTSS and use CTRL together with the ADD button on the bottom of RTSS, it should find FlightSimulator2024.exe 

3 hours ago, mobiel said:

Schould RTSS running in the background?

Yes. Instructions for activating this feature are contained in the 0.4.5.0-test release notes.

Edited June 9, 2025Jun 9 by Reset XPDR

I have a feature suggestion: as AutoFPS can reduces settings and control framerates, could it get an "Away" mode, reducing graphics settings to the minimum and capping framerates so as to minimized CPU and GPU power consumption and heat dissipation?

That would come in handy during summer months when doing long range flights... while away from the computer.

58 minutes ago, iborg1979 said:

I have a feature suggestion: as AutoFPS can reduces settings and control framerates, could it get an "Away" mode, reducing graphics settings to the minimum and capping framerates so as to minimized CPU and GPU power consumption and heat dissipation?

Could this not be accomplished by creating a profile for that? 

14 hours ago, iborg1979 said:

I have a feature suggestion: as AutoFPS can reduces settings and control framerates, could it get an "Away" mode, reducing graphics settings to the minimum and capping framerates so as to minimized CPU and GPU power consumption and heat dissipation?

That would come in handy during summer months when doing long range flights... while away from the computer.

As @TomPisuggests, you can already do all of what you are asking for, except setting an actual system FPS cap (because AutoFPS can't set that), by setting up another profile with full settings reduction enabled and a target FPS well above what you normally get so that settings reduction kicks in.

Alternatively, for everything you ask for, you can do what I do and just use MSI Afterburner with RTSS, setting it up so that a hotkey triggers a low FPS cap and use your existing AutoFPS profile that has settings reduction enabled.

eg. Here's my setup with my system sitting at the target FPS of 60 in FPS cap mode, so everything is running normally:

Then I simply hit the RTSS framerate limit hotkey (CTRL SHIFT 8 in my case) to cap the system FPS to 20, wait about 1 minute for all settings reduction to kick in then this is what I get:

As you can see, GPU power has more than halved by doing this.

As I have now integrated RTSS FPS readings into the latest AutoFPS test version, I will see if I can also control its deployment of the RTSS framerate limiter but IMO it is just as simple to use the hotkey for when you know you will be in cruise for a while and turn it back up when you start descending again.

MSFS_AutoFPS version 0.4.5.0 has just been formally released and is available for download here. Thanks to those who participated in the test phase of this release, particularly the regular testers over on github.

Executive Summary

This update enhances FPS averaging, introduces RTSS as an alternative FPS source, improves UI clarity, expands detailed logging, and refines general functionality for a smoother and more adaptive experience.

Summary of Changes

• FPS Averaging: Now a true X-second average (default 5s, configurable).
• RTSS Integration: Alternative and more accurate FPS source, auto-reverts to MSFS FPS when RTSS isn’t installed and running.
• UI Improvements: Expert Panel starts collapsed on auto update, more descriptive tooltips for novice settings, reduced TLOD/OLOD min altitude values.
• Enhanced Logging: More detailed FPS logging with configurable duration, improved event tracking.
• General Updates: Graphics mode persists across launches, refined auto-update logic, FPS tolerance loosened for view transitions.

Please review the updated readme here, which provides a detailed description of the app, installation, features and settings, before asking any questions or raising any issues about the app.

Hmm... after the update the UI is no longer displayed. The program is running as always but when I click on the Tray Icon and it goes to the Taskbar the window remains hidden.

1 hour ago, Farlis said:

Hmm... after the update the UI is no longer displayed. The program is running as always but when I click on the Tray Icon and it goes to the Taskbar the window remains hidden.

Try quitting the app then restarting within 10 seconds, which should reset the app's window position.

If that doesn't work, try pressing shift while right clicking on the app icon in the taskbar then select Move. You should then be able to use your left and up arrow keys to relocate your app window back in the visible area.

Failing that you could rerun the installer and perform a clean install which will reset the window position, however you will lose any profiles you have previously set up.

Alternatively, if you are feeling particularly adventurous, you could edit %appdata%\MSFS_AutoFPS\MSFS_AutoFPS.config and change both the windowTop and windowLeft values to 50, which the default, then save and rerun the app. This will preserve your other existing settings.

I will look at making this easier to do in the next app version, perhaps with a Reset Window Position Only" option for the installer. 

Edited June 13, 2025Jun 13 by Reset XPDR

I ended up having to do a complete re-install. 

2 minutes ago, Farlis said:

I ended up having to do a complete re-install. 

The update did not change anything relating to window positioning or the saving thereof, so your updated app window should have appeared where you last left it. In any case, I'm glad you got it working again, even if you did end up having to go nuclear on it.