Reset XPDR

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.

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.

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.

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: 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.

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.

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.

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 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.

The update options are only present until you start your first flight session, and has been that way since the app was created. If you start the app while in a flight already, that upgrade window can be less than 30 seconds before it locks on to your flight, so the best way to see those updates is to not be in a flight when you start the app. Better yet, if you choose Prompted or Silent Updates then the app will auto update within seconds of starting without you having to ever worry about catching it.

MSFS_AutoFPS v0.5.1.0 has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase. TL;DR - Fixed Target FPS automation is better + some other fixes/improvements. This release delivers major upgrades to Fixed Target FPS TLOD automation, with redesigned increase and decrease paths, smoother trend and peak handling, and a significantly improved reduction model that reacts more cleanly and consistently to FPS changes. It also provides comprehensive fixes to restore correct VRAM+ reduction behaviour, changes TLOD‑Halved‑at‑Night to no longer limit the lower TLOD range, uses a darker orange for changing sim values to improve readability and updates the installer to improve robustness and user experience.

RTSS is only an alternative FPS source, and lately has not been very reliable, so you definitely don't need that one. GPU-Z is optional if you want protection for when VRAM is going to overflow. Auto Target FPS will detect whether you have an FPS cap set somewhere or not and will configure accordingly, so no real need to worry about that. The basic rule for using Dynamic Settings with AutoFPS is to set it 5-10 FPS below what your system normally achieves in poor performance conditions ie. it acts as a safety net if AutoFPS reductions alone are not enough stem a big performance drop. As always, the lovingly-crafted Readme covers all this is much more detail, so I suggest you read that too.

You can easily join any test program that is running by simply selecting Test+ as the upgrade channel option when you start the app, where you will either be notified or auto upgraded to the latest version depending on which upgrade option you have chosen to the left of it. While you can post your feedback on test versions here, it is preferable that you do so over in the discussion section for the respective test release over on github, so as not to clutter up this discussion thread that is mainly about formal releases. The link to the discussion for the 0.5.0.1 test version is here.

GPUs are designed to run continuously at max load in games with no ill effect, and your Quest 3 is quite happy to gobble the results of that up to give you the best visuals possible, so I wouldn't be too worried about it. If you really want to reduce it, I suggest you set an FPS cap slightly lower than what your system generally achieves, which will give your GPU some breathing room between frames. From an AutoFPS perspective, if it is high TLODs causing the high GPU loads, then reduce your TLOD Min and Max as appropriate.

I responded to this yesterday but it seems to have disappeared. In any case, I basically said that with the settings you are using, AutoFPS should not be changing any settings between the start of your takeoff roll and getting to Alt TLOD Base, as it has a critical flight phase settings lockout active at this time, so AutoFPS is likely not the cause. The exception to this is if you are using AutoFPS's MSFS peformance optimiser feature, which can cause performance/stuttering issues on some systems (and now comes with a warning message about this possibility when you first enable or renable the feature). If so, try turning that feature off and see if it resolves it. If that isn't it, try a flight without AutoFPS running and TLOD set manually in MSFS to 50. If it still stutters as before, then AutoFPS is definitely not the droid you are looking for and you will need to look for something else on your system causing this. Edit: LOL, just as I post this my original response reappears here. Oh well, you now have two responses you can choose from 😄

With the AutoFPS settings you state, the app should not be increasing any MSFS setting from the start of your takeoff roll until your TLOD Base Min of 1000ft as the critical flight phase logic lock is active at this time, so it is unlikely that AutoFPS is the cause of stutters within that time segment. The only allowable change during this phase is a TLOD drop if performance is particularly bad, but at only TLOD 50 with your decent hardware spec you should not be experiencing that. Are you using the MSFS performance optimiser option in AutoFPS and, if so, have you tried disabling it? If that is not it, what happens it you do not run AutoFPS and manually set TLOD 50 or 75 for takeoff?

Just run the installer and click on the Update button without changing anything else and your current settings will be preserved. It will only reset your existing settings if you select the Reset Configs option, so make sure that one remains unchecked. This app supports both MSFS 2020 and 2024, keeps separate settings for each and auto switches based on what MSFS version you currently have running.

Wow, that is quite an old app version, which likely has outdated url code. I suggest you switch to 0.5.0.0 manually per the link I gave you.

Thanks for letting me know. I will look into it. Any chance you can PM me the contentls of your associated log file, located in %appdata%\MSFS_AutoFPS\log, which will make it easier to find what the issue is. What Extra mode are you using BTW? Fixed, Extra or Free? Also are you using Start Max or not (implied no if you are starting from TLOD Base Min)? Anything you can provide that will allow me to recreate will help me find and fix it quicker. FYI, there is a fix in the upcoming Test3 that addresses a very specific stuck TLOD situation when TLOD is on its way down, not up, so probably not related. Edit: I just tried to recreate this issue using Test2, trying Fixed, Extra and Free, and as long as you are above Alt TLOD Base, achieving your system fixed FPS and your target FPS matches it, then TLOD always increases. The only way I can get TLOD to not increase is if your current FPS never gets to at least match your target FPS, but the app will eventually warn you of this by making the target FPS text box background go orange like this: Edit2: Another user just provided me a log showing they encountered the stuck TLOD situation with Fixed Target FPS with Test2. As it very well could be the issue you have been encountering, I have gone ahead and released Test3 so I suggest you update to it and let me know if it still happens or not.

You are probably using a much older app version, which may not use the current update url generating code. Out of curiousity, what app version are you running and to what specific app version is it trying to update you to? Regardless, you can always manually update to the latest app version by downloading from here at the bottom of the page and running the installer.

It was in versions prior to 0.5.0.0 and did the following: LOS-C Line of Sight Correction: Adjusts TLOD between Alt TLOD Base and Top such that the viewing distance grows quickly at lower altitudes but more slowly at higher altitudes. Provides a more realistic experience of horizon expansion as altitude increases, rather than the linear increase when disabled, following a square root curve. Disabled by default, as the larger TLOD changes it makes at lower altitudes may cause FPS drops and stutters on some systems. It was removed because it was rarely used, caused the issue mentioned in the last dot point and unnecessarily complicated some of the automation calculations.

The same AutoFPS settings in 0.5.0.0 should deliver the same experience as 0.4.6.4 did, as I did not really touch existing functionality when creating 0.5.0.0, so it is most likely that the change from SU4 to SU5 is giving you this diminished experience. The easiest way to tell if AutoFPS is the culprit is to note what TLOD and OLOD AutoFPS has set in a poor performance scenario, quit AutoFPS then set those exact values in MSFS settings. If the result is the same, MSFS behaviour is the issue.

I am really glad to hear it is running that smoothly for you. The recent tweaks in AutoFPS help with the stability side, but the big jump you are seeing on the ground is probably thanks to SU5. MSFS 2024 is simply much more tolerant of TLOD changes close to the ground now, so AutoFPS benefits from that rather than being the main reason for it.

Have you tried disabling the MSFS Performance Optimiser feature of AutoFPS? It does not always deliver better performance and in some cases it can be worse. If the latter, stop using it. The app now warns you about this the first time you enable or reenable the feature from now on, but not if you are already using it. Re Dynamic Settings versus AutoFPS, per the Readme FAQ, they manage TLOD quite differently and, if configured correctly, they are actually complimentary. I use Dynamic Settings with AutoFPS all the time and nothing I have seen changes that assessment, including with SU5.

DynamicLOD_ResetEdition 0.5.8 has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase. This release introduces a new Update Channel system, improves MSFS Performance Optimisation warnings and UI clarity, enhances camera‑state and flight‑session handling for greater stability, strengthens UserCfg.opt backup/restore reliability, and updates MSFS 2024 memory offsets and module bases for the SU5→SU6 beta rebaseline.

MSFS_AutoFPS v0.5.0.0 has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase. This major release introduces a new Fixed Target FPS system and FreeTLOD in FPS Sensitivity and Tolerance modes, delivers major improvements to Fixed FPS detection, TLOD/LOD logic, cloud automation and UI behaviour, enhances non‑expert and Auto Target FPS handling, simplifies the non‑expert UI, rebaselines to MSFS 2024 SU5 and prepares for SU6 beta, and includes targeted update, stability, logging, configuration and session‑management improvements across the app.