Latest version, MSFS24.

4 hours ago, Speedbird 217 said:

Not sure if this is an issue or by design but when I run with FPS Tolerance mode everything is good when I keep the AutoFPS window on top. The moment I minimise it or bring the sim to the front it seems to stop updating the LOD.

For example, I had TLOD on 100 on the ground and was climbing out. When I checked the AutoFPS window at around 8,000 AGL it was still showing LOD 100 but once in focus started to show the incremental steps of raising the LOD. I let it get to around 240 and refocused the sim. Climbed to cruise and opened AutoFPS and it was still on 240 but with the focus on it I could now see it climb slowly to 400. Worth noting that it doesn’t just jump up from 240 to 400 but still shows it going up in increments. That to me suggests there’s an issue?

Any ideas or am I doing something wrong?

Realistically, you get your settings dialed in and dont click on other things in a separate monitor or app. Try to use in-sim stuff instead. 

Example, settings to your liking then use the toolbar in the same for everything else (gsx, beyond atc, navigraph etc) from the drop down. Its a limitation of the sim and app. Similar issues happen to me with other games, simulators using a second monitor. 

 

12 minutes ago, Sonosusto said:

Realistically, you get your settings dialed in and dont click on other things in a separate monitor or app. Try to use in-sim stuff instead. 

Example, settings to your liking then use the toolbar in the same for everything else (gsx, beyond atc, navigraph etc) from the drop down. Its a limitation of the sim and app. Similar issues happen to me with other games, simulators using a second monitor. 

 

Thanks! Yeah, I only use one screen and don’t generally switch to other windows frequently. I tested it some more and when I landed it correctly showed TLOD 100 when I parked up at the gate.
It just seems more “real time” when I have the AutoFPS window on top and whenever I switch to it there’s a lot of activity and it looks like it’s catching up, so I’m not quite sure it’s working as intended.

29 minutes ago, Sonosusto said:

Realistically, you get your settings dialed in and dont click on other things in a separate monitor or app. Try to use in-sim stuff instead. 

Example, settings to your liking then use the toolbar in the same for everything else (gsx, beyond atc, navigraph etc) from the drop down. Its a limitation of the sim and app. Similar issues happen to me with other games, simulators using a second monitor. 

 

I use two monitors, with Navigraph charts on the second monitor, and do go back and forth between monitors when flying. Although minimized, AutoFPS runs on the main (sim's) monitor. From what I have read here, it seems AutoFPS is only active (working) when the sim monitor has the focus. Is my understanding correct? 

Thx,
Al

Edited July 29, 2025Jul 29 by ark

1 hour ago, ark said:

I use two monitors, with Navigraph charts on the second monitor, and do go back and forth between monitors when flying. Although minimized, AutoFPS runs on the main (sim's) monitor. From what I have read here, it seems AutoFPS is only active (working) when the sim monitor has the focus. Is my understanding correct? 

Thx,
Al

I know that's the case when using frame generation... as frame generation only works when the sim window has focus. Not sure if you're not using FG.

Just tried again - didn’t touch the AutoFPS window until I reached cruise. Still showed TLOD 100 at that point but immediately started jumping through increments towards 400 when in focus. Something isn’t right.

I have FG enabled in MSFS24. AutoFPS settings are:

• Target FG FPS 60
• Auto Method - FPS Tolerance
• Var 5%
• TLOD Min [+] 100
• TLOD Max 400
• At TLOD Base 1000ft
• Avg Descent 2000fpm
• Hide OLOD
• Vram off

4 hours ago, ark said:

I use two monitors, with Navigraph charts on the second monitor, and do go back and forth between monitors when flying. Although minimized, AutoFPS runs on the main (sim's) monitor. From what I have read here, it seems AutoFPS is only active (working) when the sim monitor has the focus. Is my understanding correct? 

Thx,
Al

Yes i’m experiencing same way with FG. I wish it would keep the TLOD same when i minimized/unfocused.

9 hours ago, Speedbird 217 said:

Not sure if this is an issue or by design but when I run with FPS Tolerance mode everything is good when I keep the AutoFPS window on top. The moment I minimise it or bring the sim to the front it seems to stop updating the LOD.

For example, I had TLOD on 100 on the ground and was climbing out. When I checked the AutoFPS window at around 8,000 AGL it was still showing LOD 100 but once in focus started to show the incremental steps of raising the LOD. I let it get to around 240 and refocused the sim. Climbed to cruise and opened AutoFPS and it was still on 240 but with the focus on it I could now see it climb slowly to 400. Worth noting that it doesn’t just jump up from 240 to 400 but still shows it going up in increments. That to me suggests there’s an issue?

Any ideas or am I doing something wrong?

Are you running the latest app version 0.4.5.2? If not, update to that and try it again.

I just tried your scenario in both MSFS 2020 and 2024, using either the normal install or the minimise to system tray option, even switching between NFR and FG and the result is the same in all cases - TLOD changes as expected regardless of whether the app has the focus, is minimised, is sent to the system tray or is behind the MSFS window.

If you are still having this issue when using 0.4.5.2, personal message me the copy and pasted contents of your latest log file (you cant' just attach the file here unfortunately), located in %appdata%\MSFS_AutoFPS\log, associated with it happening and I will take a look.

5 hours ago, ark said:

I use two monitors, with Navigraph charts on the second monitor, and do go back and forth between monitors when flying. Although minimized, AutoFPS runs on the main (sim's) monitor. From what I have read here, it seems AutoFPS is only active (working) when the sim monitor has the focus. Is my understanding correct? 

Thx,
Al

 

1 hour ago, Sangello said:

Yes i’m experiencing same way with FG. I wish it would keep the TLOD same when i minimized/unfocused.

Since there are a few of you experiencing this issue, which I am not able to replicate at this time, it would be helpful if you personal message me the copy and pasted contents of your latest log file (you cant' just attach the file here unfortunately), located in %appdata%\MSFS_AutoFPS\log, associated with it happening and I will take a look.  Any additional commentary you can provide will also be helpful.

I think I have found an issue, which is hopefully THE issue causing TLOD to reduce when MSFS is not focused and FG is in use. It seems to only occur when RTSS is the FPS source - using MSFS as the FPS source has it behaving correctly.

For those experiencing the TLOD reducing or not changing issue issue, can you please advise whether you are using MSFS or RTSS as the FPS data source. The symbols look like this for MSFS and RTSS respectively:

 

I have now fixed the issue I identified in the post above in the latest 0.4.5.3-test build available here, which hopefully resolves the issue others have been experiencing when using FG or MFG and RTSS as the FPS source with 0.4.5.2 (back as far as 0.4.5.0 for that matter). Please give it a try if you were having that issue and let me know if it is now resolved.

The issue was occurring because MSFS via simconnect only ever provides the NFR, not the actual FG, FPS when FG is in use whereas RTSS always provide the actual FPS for FG active or inactive. This was confusing the automation code and causing the app to think that when FG was inactive that the FPS was well below the target FPS and hence was causing TLOD to reduce to minimum. It has now been fixed to scale up the FG inactive FPS so that RTSS behaves like MSFS FPS source does.

As for the question being asked of when AutoFPS is active, for the most part it is active all the time when in a flight session is active and not paused or in a settings menu, regardless of whether the app is minimised, hidden, obscured or on top. The only exception is with FG in that some feature like auto target FPS calibration and auto settings reduction are inactive when FG is inactive, because the FPS being read is not representative of what you will actually see in game because it is usually not exactly half of the FG active FPS reading you are getting, but otherwise TLOD automation should continue functioning. Again, if not show me in a log file where and I will take a look.

 

 

 

 

 

i use fps cap in the cfg file

and i still have the same issue.

not a big issue as the app works just fine. just when clicking on separate monitor

28 minutes ago, Sonosusto said:

and i still have the same issue.

not a big issue as the app works just fine. just when clicking on separate monitor

By same issue do you mean TLOD reduces when MSFS is not focused and you are using FG with RTSS as the FPS source or something else? If yes, have you tried the latest 0.4.5.3-test version? If not, exactly what is the issue?

Hi, having an issue with this wonderful little app that has kept my rig alive for longer than I ever thougt.

Currently, running latest AutoFPS version, MSFS2020 SU16 beta (1.39.9.0), even if I think this problem was happening before already. My computer takes a big hit with clouds, especially with overcast. Therefore, I am very interested to use the option to decrease cloud quality, triggered by GPU load (don't want to use TLOD trigger as the drop in FPS seems to be due to cloud mainly, even with the lowest TLOD I still have a drop in FPS). Anyway, with GPU-Z installed, and clouds in ultra at the start, it seems that AutoFPS never decreases cloud quality, no matter the GPU load or the FPS. I set a scenario with plenty of clouds and the GPU load skyrockets, but clouds stay at ultra. I played with the % load for activation and it does not change anything. Even above 98%, no change, clouds stay in ultra. 

I attached 2 screenshots. Any idea what I may be doing wrong? I read the instructions but did not find any solution.