1 hour ago, TomCYYZ said:

I find if I have any app interface (Including AutoFPS) open on top of MSFS2024 my FPS (I have Fixed target = 60) is cut in half with FG Inactive. When I open the interface I immediately observe FPS (Sim Value) and it temporarily shows 60 (FG Active) and quickly turns to "Orange" 30. So, I would conclude that my AutoFPS is functioning as it should. I thought this was a a known issue regarding the MSFS focus. I am using v0.5.1.0.

Yes. AutoFPS is responding as it should. What you observe it is not actually an issue specific to MSFS, rather it is how nVidia FG behaves with any game. The difference with MSFS is that we often don't run the game exclusively, often switching focus to supporting apps while flying, whereas most other games when you are in the game, you stay in the game until you quit it, making it seem like FG is active all the time when it is only so because the game always has the focus.

I couldn't tell if it was by design from the readme, but with 0.5.1.0 Auto target FG fps auto, expert options w/ FPS sensitivity, I am unable to swap from TLOD base min "fixed" selection in the drop down box. I try to select either "extra" or "free" and it doesn't change "fixed".

4 hours ago, Buggsy said:

I couldn't tell if it was by design from the readme, but with 0.5.1.0 Auto target FG fps auto, expert options w/ FPS sensitivity, I am unable to swap from TLOD base min "fixed" selection in the drop down box. I try to select either "extra" or "free" and it doesn't change "fixed".

It is by design, has always been that way and is mentioned in the last bullet point for Auto Target FPS in the Readme. In short, Auto Target FPS and TLOD Extra are mutually exclusive as the former needs a fixed TLOD when it calculates the target FPS and vice versa. Free is just an extension Extra, hence it is excluded too.

Edit: I concur the readme is not really explicit with the current implementation that include Free TLOD, so I have updated it as follows:

• Auto settings reduction and TLOD Base Extra and Free are mutually exclusive with Auto Target FPS, hence are not selectable. Fixed TLOD must be used.

Edited May 16May 16 by Reset XPDR

Just watched that without expert option I get 90FPS only, with expert options choosed I get 400FPS. I can remember I got the higher values without choosen expert modus in former times too.

Kai

#1 https://www.directupload.eu/file/d/9286/z66zzp6h_jpg.htm

#2 https://www.directupload.eu/file/d/9286/i5z6hudw_jpg.htm

9 minutes ago, Kai-Uwe Wei said:

Just watched that without expert option I get 90FPS only, with expert options choosed I get 400FPS. I can remember I got the higher values without choosen expert modus in former times too.

Kai

#1 https://www.directupload.eu/file/d/9286/z66zzp6h_jpg.htm

#2 https://www.directupload.eu/file/d/9286/i5z6hudw_jpg.htm

I think you are referring to TLOD not FPS. In any case, the TLOD you can achieve in non-expert mode is based on your default MSFS TLOD. which must be low if you are only getting 90 max, whereas in expert mode you have set TLOD max to 400, so that is what you are able to achieve. If you want higher TLOD in non-expert mode, change your default MSFS TLOD to something higher than what is currently set to either not in a flight or with AutoFPS not running.

I think you are referring to TLOD not FPS. In any case, the TLOD you can achieve in non-expert mode is based on your default MSFS TLOD. which must be low if you are only getting 90 max, whereas in expert mode you have set TLOD max to 400, so that is what you are able to achieve. If you want higher TLOD in non-expert mode, change your default MSFS TLOD to something higher than what is currently set to either not in a flight or with AutoFPS not running.

Yes, I meant TLOD, sorry for that. I'll try your advice; I had to renew my settings lately so it is possible of course that I have had higher settings before. Thank you.

Kai

I am not really able to tell from your screenshot that the issue you report is present because the settle timer still has two seconds on it, hence no automation is currently active and likely has not even started yet, and while your TLOD value is shown in orange, it does not have a down arrow next to it hence it is showing a fixed, not reducing value and 0.5.0.0 shows that to indicate that TLOD is currently limited because FG is inactive.

Nonethless, I have tried to recreate your issue with 0.5.0.0 and your specific settings and, after letting FPS settle and allowing TLOD to climb to its maximum level with MSFS having the focus, I cannot get TLOD to reduce when clicking away from the MSFS window eg.

It could possibly be the type of FG you are using, because when configuring the app with your settings I note that you are using manual FG X2 and not Auto, which detects MSFS-set FG. What FG are you using and exactly where are you setting it?

BTW, you are using Fixed Target FPS, which has been significantly improved in the just-released 0.5.1.0 update, so I strongly suggest you update to that version. It will also be the baseline version to which I will be making any fixes should I be able to recreate your issue.

Once you have updated to 0.5.1.0, try it again, start a flight, let the settle timer finish, let TLOD increase as high as it will go for your current altitude, click away from MSFS and it you see TLOD decreasing (ie. not just orange but the number decreasing and a down arrow to the right of it), take a screenshot and post that here.

Also, could you go into your associated log file, located in %appdata%\MSFS_AutoFPS\log, and post the snippet of where you did this. eg. here is my snippet showing TLOD increasing up to 300 at cruise with FG active (2X shows), then staying at 300 when FG is inactive (1X shows), then back again to FG being active and still holding TLOD at 300 ie. I do not see TLOD decrease when MSFS loses focus:

2026-05-14 08:30:51.356 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS TLOD:68 TLODRng:68-300 Mtns+:0 OLOD:20 AGL:37357 FPM:478 GPU:53% VRAM:67%

2026-05-14 08:31:01.503 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 42 TLOD:108 TLODRng:108-300 Mtns+:0 OLOD:20 AGL:37421 FPM:318 GPU:54% VRAM:67%

2026-05-14 08:31:10.636 [DBG] [ LODController:DetectFixedFPS ] Fixed FPS detected at 72 FPS

2026-05-14 08:31:11.649 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 66 TLOD:148 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37460 FPM:175 GPU:54% VRAM:67%

2026-05-14 08:31:21.826 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 66 TLOD:188 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37475 FPM:27 GPU:53% VRAM:67%

2026-05-14 08:31:31.986 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 66 TLOD:205 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37464 FPM:-130 GPU:55% VRAM:63%

2026-05-14 08:31:42.159 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 66 TLOD:225 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37425 FPM:-298 GPU:57% VRAM:63%

2026-05-14 08:31:52.318 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 66 TLOD:245 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37355 FPM:-503 GPU:56% VRAM:63%

2026-05-14 08:32:02.491 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 66 TLOD:265 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37290 FPM:-114 GPU:56% VRAM:63%

2026-05-14 08:32:12.658 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 66 TLOD:285 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37384 FPM:960 GPU:58% VRAM:64%

2026-05-14 08:32:22.827 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 66 TLOD:300 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37588 FPM:1209 GPU:53% VRAM:64%

2026-05-14 08:32:32.970 [INF] [ LODController:UpdateVariables ] Mode:Man FG 1X FPS:36 Pri:FPS+ 66 TLOD:300 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37724 FPM:416 GPU:44% VRAM:64%

2026-05-14 08:32:43.150 [INF] [ LODController:UpdateVariables ] Mode:Man FG 1X FPS:36 Pri:FPS+ 66 TLOD:300 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37684 FPM:-642 GPU:44% VRAM:64%

2026-05-14 08:32:53.299 [INF] [ LODController:UpdateVariables ] Mode:Man FG 1X FPS:36 Pri:FPS+ 66 TLOD:300 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37521 FPM:-1044 GPU:38% VRAM:64%

2026-05-14 08:33:03.443 [INF] [ LODController:UpdateVariables ] Mode:Man FG 1X FPS:36 Pri:FPS+ 66 TLOD:300 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37391 FPM:-467 GPU:39% VRAM:64%

2026-05-14 08:33:13.588 [INF] [ LODController:UpdateVariables ] Mode:Man FG 1X FPS:36 Pri:FPS+ 66 TLOD:300 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37413 FPM:522 GPU:40% VRAM:64%

2026-05-14 08:33:23.734 [INF] [ LODController:UpdateVariables ] Mode:Man FG 1X FPS:36 Pri:FPS+ 66 TLOD:300 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37561 FPM:997 GPU:39% VRAM:64%

2026-05-14 08:33:33.910 [INF] [ LODController:UpdateVariables ] Mode:Man FG 1X FPS:36 Pri:FPS+ 66 TLOD:300 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37700 FPM:592 GPU:39% VRAM:64%

2026-05-14 08:33:42.070 [INF] [ ServiceController:ResetAverageFP ] Average FPS reset to initial state

2026-05-14 08:33:51.210 [INF] [ LODController:UpdateVariables ] Mode:Man FG 2X FPS:72 Pri:FPS+ 66 TLOD:300 TLODRng:132-300 Mtns+:0 OLOD:20 AGL:37644 FPM:-720 GPU:54% VRAM:64%

Edit: Here is that data shown graphically to make it clearer what I observed:

If you are unable to locate such a snippet, just PM me the entire contents of your log file and I will look for it.

Thank you for your answer! I updated and changed the setting because the type of FG was configured wrongly indeed.
It looks like this now:
https://www.directupload.eu/file/d/9290/r95j4mq2_png.htm (Am I dumb, I cant add pictures anymore?? )

Unfortunately, it is still decreasing. In this example it used to be 300, already decreased to 240. When I click into MSFS2024, its climbing up to 300 in no time.

I can add the log later but I am still in the flight.

Edited May 20May 20 by CallsignBA

Thank you for your answer! I updated and changed the setting because the type of FG was configured wrongly indeed.
It looks like this now:
https://www.directupload.eu/file/d/9290/r95j4mq2_png.htm (Am I dumb, I cant add pictures anymore?? )

Unfortunately, it is still decreasing. In this example it used to be 300, already decreased to 240. When I click into MSFS2024, its climbing up to 300 in no time.

I can add the log later but I am still in the flight.

Your new screenshot still shows the app is set to FG 2X. Set it to Auto, then after loading into a flight, take a screenshot to show that you have correctly configured it.

Also, you haven't told me what FG are you using and exactly where are you setting it. Please advise.

Re:

Unfortunately, it is still decreasing. In this example it used to be 300, already decreased to 240. When I click into MSFS2024, its climbing up to 300 in no time.

When FG is inactive, TLOD can still decrease (but not increase, as the FG inactive GPU load is not the same as the FG active load) if you are not achieving the NFR of the target FG FPS you have set. In your case, you have set 72 FPS for the target FG FPS, in which case 36 is the NFR of that when FG is inactive so if you get less than 36 FPS then your TLOD will drop. Is this what is happening?

The only real way I can tell what is going on is by looking at your log. If you can extract a small snippet like I did above then you can post here, otherwise send me the contents of the whole log in a PM so as not to clutter up this discussion. BTW, you don't have to wait until you have finished a flight to extract the snippet. It is only an unlocked text file so you can do it while the app and your flight is running.

Edited May 21May 21 by Reset XPDR

Hi ,

Running 9800X3D + RTX 5080 16GB + 64GB DDR5 running MSFS 2024 on a 43" 4K 60Hz monitor.

These are my current AutoFPS settings:

(Attach both screenshots here: AutoFPS window + performance overlay)

I’m mostly flying heavy airliners (Fenix and iniBuilds).

Question: Do these AutoFPS settings look correct? Is there anything weird or that I should change to improve performance / VRAM usage?

Thanks in advance!

ImgBB

IMG 4877 hosted at ImgBB

Imagen IMG 4877 alojada en ImgBB

ImgBB

IMG 4878 hosted at ImgBB

Imagen IMG 4878 alojada en ImgBB

Edited May 25May 25 by juaness

4 hours ago, juaness said:

Hi ,

Running 9800X3D + RTX 5080 16GB + 64GB DDR5 running MSFS 2024 on a 43" 4K 60Hz monitor.

These are my current AutoFPS settings:

(Attach both screenshots here: AutoFPS window + performance overlay)

I’m mostly flying heavy airliners (Fenix and iniBuilds).

Question: Do these AutoFPS settings look correct? Is there anything weird or that I should change to improve performance / VRAM usage?

Thanks in advance!

ImgBB

IMG 4877 hosted at ImgBB

Imagen IMG 4877 alojada en ImgBB

ImgBB

IMG 4878 hosted at ImgBB

Imagen IMG 4878 alojada en ImgBB

Your AutoFPS settings look fine to me. The only thing I would suggest is running GPU-Z as a companion app, so that GPU load and VRAM usage is reported to the app, then enable VRAM+ in the app to protect you from potential VRAM overflows. Instructions for where to download and how to configure GPU-Z correctly to work with the app are contained within the readme.

Edited May 25May 25 by Reset XPDR

On 12/5/2025 at 9:57 PM, Reset XPDR said:

It is not a silly question as dynamic settings is a bit of a tricky one to get working with AutoFPS if you are not using an FPS cap.

The reason it is so tricky is that in my limited testing without a frame rate limit, if you set dynamic setting the same as your target FPS then dynamic tends to activate at a frame rate even higher than what you have set it to for some strange reason. This is why I suggest you set dynamic setting at least 10 FPS lower than your target FPS (and it does need to be the native equivalent of your target FPS because that's how MSFS is configured).

For example, here I have my FPS uncapped, with FSR3 getting around 110 FPS, so 55 FPS native, and dynamic setting set to 55 to line up with native FPS. As you can see, even though I am achieving the required 55 FPS native, dynamic setting feels the need to start activating, which IMO is too pessimistic:

 

If I change to using an FPS cap by setting max frame rate in MSFS to 60, then set dynamic settings to 60 and target FSR3 FPS to 120, ie everything to 60 FPS native, dynamic settings now behaves itself.

 

For your particular configuration, I would try using an FPS cap setup and set max frame rate in MSFS to 30, dynamic settings to 30 and target FSR3 FPS to 60 and, very importantly, use FPS cap mode in AutoFPS (which has been designed to work with an FPS cap).

Hello

sorry to bump on old post would you still recommend these settings with su5 ??

im still running at 120 hertz and half refresh rate etc etc

Hi Reset Xpdr

during approach i was playing with some settings and during that ms24 crash

10 hours ago, grandfred29 said:

Hi Reset Xpdr

during approach i was playing with some settings and during that ms24 crash

Notwithstanding that MSFS is quite happy to CTD all of its own accord and is therefore the most likely explanation.

I see from the associated log you sent me via PM that you were changing a few AutoFPS TLOD Base and Top settings just before the CTD, the last of which was selecting Fixed as the TLOD Base option about 10 seconds before the CTD. These changes should have done nothing more than vary TLOD in MSFS, which the app does all the time anyway, so should not have been the cause of the CTD.

I ran a test with your settings and attempted to recreate your final settings change sequence and was not able to trigger a CTD, despite changing AutoFPS settings repeatedly for a couple of minutes, so I do still think it is just coincidence that a CTD happened for you.

FYI, I note that the last setting you tried to change was the TLOD Base option, which can only ever be set to Fixed when using Auto Target FPS, as at least one parameter must be fixed to vary the other. In the next version of the app, likely to be released as a test version when the SU6 beta makes an appearance, the TLOD Base option will be removed from the UI when you are using Auto Target FPS as Fixed TLOD Base is forced anyway. eg.

Edited May 31May 31 by Reset XPDR
New information

12 hours ago, fluffyflops said:

Hello

sorry to bump on old post would you still recommend these settings with su5 ??

im still running at 120 hertz and half refresh rate etc etc

A slight change to my recommended settings when using AutoFPS 0.5.1.0, not because of SU5 but because of recent changes to AutoFPS:

For your particular configuration, I would try using an FPS cap setup and set max frame rate in MSFS to 30, dynamic settings to 30 and Fixed Target FSR3 FPS to 60 in FPS Sensitivity mode.