On 5/18/2025 at 4:48 PM, Reset XPDR said:

What does the app status line say the graphics mode is when MSFS doesn't have the focus?

If it says PC, you are likely not using FG, or are using a version of FG that the app can't detect. If the latter, what FG are you using? 

If it says FG Inactive, then the app shouldn't be changing TLOD because FG is inactive when MSFS does not have the focus.

If you are still having an issue, direct message me the contents of an associated flight segement from your log file, located in %appdata%\MSFS_AutoFPS\log, and I will take a look and tell you what is really going on.

 

When I fly in the simulator, the FG is detected, and it is shown on the AUTOFPS. However, when I switch windows and FG is paused, the target fps then is dropped, so the app begins taking down the TLOD to the min making everything blurry when I return to the sim. Prior versions I remember seeing a "PAUSED" when ever the sim wasn't in focus. I will send you the logs as well. 

I just got a new 9800X3D AMD card and RTX 5090, but with these enhanced system specs....I'm struggling to find my best settings at ultra and the best way to use AutoFPS. Any tips on this?

I'm struggling to understand why on the ground, my gpu use hovers around only 65% or so.  It's causing my ground fps to tank into the high 20's, low 30's.  I notice in dev mode fps it says I'm limited by "rdr thread" whatever that is.  Not Main Thread.

As soon as I'm ~2000 ft agl...it gpu use shoots up to basically full load, and I'm able to achieve my 45 fps.

I haven't really messed with anything from the default app settings.  I'm running in VR Target with FPS Cap Auto Method using VFR Flight Type.

I'm running an RTX 5080 with a 5800x3d & 64 GB Ram.

Edited May 20, 20251 yr by FakeWayne

 

4 hours ago, FakeWayne said:

I'm struggling to understand why on the ground, my gpu use hovers around only 65% or so.  It's causing my ground fps to tank into the high 20's, low 30's.  I notice in dev mode fps it says I'm limited by "rdr thread" whatever that is.  Not Main Thread.

As soon as I'm ~2000 ft agl...it gpu use shoots up to basically full load, and I'm able to achieve my 45 fps.

I haven't really messed with anything from the default app settings.  I'm running in VR Target with FPS Cap Auto Method using VFR Flight Type.

I'm running an RTX 5080 with a 5800x3d & 64 GB Ram.

6 hours ago, CitationX said:

I just got a new 9800X3D AMD card and RTX 5090, but with these enhanced system specs....I'm struggling to find my best settings at ultra and the best way to use AutoFPS. Any tips on this?

Others here may be able to offer help, but I don't provide individual settings advice as it is too system and user expectation dependent, so I suggest you both read the first entry in the FAQ and take it from there.

Edited May 20, 20251 yr by Reset XPDR

Is there a cfg file or something I can change to make the app minimize to system tray when clicking the close button? For some reason it has stopped doing this in some update and now its just completely closing with that button.
 

Or do I need to uninstall and reinstall?

There is a "-" at the top of the window, near the "x" button that will minimize without closing.  If you hover over the buttons, it should say "minimize" and "close".  If this isn't there, then maybe something is corrupt with your install.

2 hours ago, FlyData said:

There is a "-" at the top of the window, near the "x" button that will minimize without closing.  If you hover over the buttons, it should say "minimize" and "close".  If this isn't there, then maybe something is corrupt with your install.

And this minimises to the system tray rather than just minimising the window?

4 hours ago, abennett said:

Is there a cfg file or something I can change to make the app minimize to system tray when clicking the close button?

From the readme:

• With the default install option, the app's icon more intuitively resides on the task bar when the app is running, not in the system tray overflow where it has been located in previous versions. Exit by clicking on the app window's close button and providing user confirmation when prompted.
• If installed with the close app to system tray option, the app will remain running in the system tray until the user right clicks and selects Exit or the app auto exits when MSFS closes.

In short, reinstall and select the "close app to system tray" option.

I've tried to keep up with all the discussion here as I have been a avid user of the app since the early days.  I don't think this question has been asked but if so - please point me to a date or page number.

Flying into a KMYF (VBCorp add on) in any aircraft - I see a steady 60 FPS with the app controlling the TLOD and OLOD nicely.  At 500' AGL and less than a mile from the runway - 60 FPS with no variance.  VRAM is at 10.6 GB out of 12 GB.  AT 100' just a second before crossing the end of the runway - same 60 FPS/10.6GB in use.

Two second later as I cross the threshold at 65 knots and 50' the FPS drops to 5 but the memory usage does not change.  The FPS then stays at less than 5 as the app tries to catch up by lowering OLOD and TLOD. By the time I stop the plane the app has lowered OLOD to 75 but the FPS remains at 5 or less.

In a previous life I was a systems engineer (programmer) for a large refinery, the first in the world built to be computer controlled, so do understand a bit about process control/real time programming. 

I do not see how you can anticipate the FPS delta/change in operating conditions when it is nominal with no variance and then totally out of control one second later with nothing to indicate the pending changes.

Is there something I can do with AutoFPS to manage this sudden change in FPS?  The VRAM usage does not seem to predict the onset of the problem.  Do I just need to set the LODs to be less than 50 at any AGL below 100?  That would ruin the beautiful scenery/buildings that all the add on airports can deliver.

This sudden drop in FPS at the threshold occurs at almost every addon airport with any aircraft, Asobo, MS, or third party.

 

 

40 minutes ago, TacomaSailor said:

I've tried to keep up with all the discussion here as I have been a avid user of the app since the early days.  I don't think this question has been asked but if so - please point me to a date or page number.

Flying into a KMYF (VBCorp add on) in any aircraft - I see a steady 60 FPS with the app controlling the TLOD and OLOD nicely.  At 500' AGL and less than a mile from the runway - 60 FPS with no variance.  VRAM is at 10.6 GB out of 12 GB.  AT 100' just a second before crossing the end of the runway - same 60 FPS/10.6GB in use.

Two second later as I cross the threshold at 65 knots and 50' the FPS drops to 5 but the memory usage does not change.  The FPS then stays at less than 5 as the app tries to catch up by lowering OLOD and TLOD. By the time I stop the plane the app has lowered OLOD to 75 but the FPS remains at 5 or less.

In a previous life I was a systems engineer (programmer) for a large refinery, the first in the world built to be computer controlled, so do understand a bit about process control/real time programming. 

I do not see how you can anticipate the FPS delta/change in operating conditions when it is nominal with no variance and then totally out of control one second later with nothing to indicate the pending changes.

Is there something I can do with AutoFPS to manage this sudden change in FPS?  The VRAM usage does not seem to predict the onset of the problem.  Do I just need to set the LODs to be less than 50 at any AGL below 100?  That would ruin the beautiful scenery/buildings that all the add on airports can deliver.

This sudden drop in FPS at the threshold occurs at almost every addon airport with any aircraft, Asobo, MS, or third party.

 

 

Implicit from you mentioning settings reduction is that you are referring to MSFS 2024. Unfortunately, as of SU2, and even with SU3 beta, this behaviour seems to be quite common, regardless of whether using AutoFPS or not. The only thing that seems to keep the FPS-stealing-on-landing beast on at bay is by having a relatively low TLOD Min/Base of 50 or less, regardless of how much headroom your system seems to have with a higher TLOD setting. Hopefully MS/Asobo addresses this soon in the SU3 beta, because it is otherwise becoming quite farcical.

Edited May 20, 20251 yr by Reset XPDR

@TacomaSailorYep if on 2024 it is a regression introduced in the final few betas of SU2. It was reported of course, but totally ignored as usual, and now we will have this for months if it is even fixed by SU3, which as of the first beta, it isn't.

 

Stupid question as I am not at my rig and dont want to go through 200 pages of thread: what does the switch "IFR / VFR" do? Making it possible to use two different presets? Or tuning all "auto" features accordingly, because e.g. VFR means reduced climb or descend rates?

57 minutes ago, AnkH said:

Stupid question as I am not at my rig and dont want to go through 200 pages of thread: what does the switch "IFR / VFR" do? Making it possible to use two different presets? Or tuning all "auto" features accordingly, because e.g. VFR means reduced climb or descend rates?

From the README.md file:

"- A choice between VFR (GA) and IFR (Airliner) flight types, which defaults to settings suitable to each flight type and in Expert mode is fully customisable with four additional profiles available."

8 hours ago, Twenty6 said:

From the README.md file:

"- A choice between VFR (GA) and IFR (Airliner) flight types, which defaults to settings suitable to each flight type and in Expert mode is fully customisable with four additional profiles available."

Also from the readme:

• Flight type - VFR or IFR (any mode), and four additional user profiles (Expert mode)
  • Non-Expert mode:
    • VFR will use higher minimum and maximum TLODs and a lower TLOD base altitude than IFR.
    • Accounts for the greater performance expectation that GA flights in rural areas will have.
  • Expert mode:
    • Defaults to similar settings differences as Non-Expert mode for VFR and IFR.
    • user1 through user4 profiles are initially based on the IFR profile.

There's much more in the Expert Settings option section, including what every setting difference there is between VFR and IFR in Non-Expert Mode.

Edited May 21, 20251 yr by Reset XPDR

On 5/20/2025 at 6:36 PM, Reset XPDR said:

Implicit from you mentioning settings reduction is that you are referring to MSFS 2024. Unfortunately, as of SU2, and even with SU3 beta, this behaviour seems to be quite common, regardless of whether using AutoFPS or not. The only thing that seems to keep the FPS-stealing-on-landing beast on at bay is by having a relatively low TLOD Min/Base of 50 or less, regardless of how much headroom your system seems to have with a higher TLOD setting. Hopefully MS/Asobo addresses this soon in the SU3 beta, because it is otherwise becoming quite farcical.

I tried something novel for an old programmer - let the xpert deal with it!

I quit using expert options.  I selected Target:PC / FPS:50 / On Top / Flight Type:VFR and you provided amazing results!

All my busy test approaches stay at 60 FPS (30 limit in Sim and nVidia FG) with just the quickest hiccup over the threshold, (very occasional and quite brief and only down to 30 or so) but by the time the wheels touch down I am back to 60 FPS.

And... the LODs both stay above 150 all the time. 

I tried to "trick" or overpower your anticipation by crossing the threshold at 50' and 200 knots with the wheels up (a flyby) but the FPS stayed right at 60.

I don't quite understand because I thought I had set both LODs to a minimum of 150 when I was having problems.

Can't tell you how much I appreciate your work and how clever you must be.  I've been trying to figure out how you came to this procedure - must have been a lot of tedious experimenting.

Thank You again

AutoFPS 0.4.4.9

2024 Beta 1.5.2.0

Win 11 23H2

Edited May 21, 20251 yr by TacomaSailor