18 minutes ago, Rob G said:

I'm at my wits end about something: no matter what settings I use (SIM and autoFPS), I get terrible stutters from take off until about 500-600 ft up. I use a starting TLOD of 50 and OLOD of 100. Testing in both 2D and VR. Using Crystal Light when in VR. Currently testing with DLSS set to Balanced. Frames capped in-sim at 35 and Dynamic settings turned on at 35fps.

7800X3D, RTX 4090, 64Gb of 6000 ram.

I am not using an airliner. I am doing all my flying right now in the Beachcraft Bonanza G36, cruising at about 3000 feet.

I should also add that my Community folder has nothing in it except a couple of needed utilities and Navigraph. I removed everything else for testing.

Everything seems like its doing very well, except for those takeoffs to about 600 ft. I have tried at KLAS, KJFK,and KMIA so far.

autoFPS settings: General: Fixed, NFR or VR, FPS: 35, Flight type: VFR, FPS Sensitivity, Sens 5, TLOD base min: 50@1000ft, 800@6000, Extra 1.5, TLOD Top Max: 800@6000, AutoLOD Base: 100@2000, OLOD Top: 20@10000

I akm hoping someone can tell me what to try to get takeoffs under control instead of stutter fests.

Thanks all.

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?

Edited May 8May 8 by Reset XPDR

17 hours ago, Rob G said:

I'm at my wits end about something: no matter what settings I use (SIM and autoFPS), I get terrible stutters from take off until about 500-600 ft up. I use a starting TLOD of 50 and OLOD of 100. Testing in both 2D and VR. Using Crystal Light when in VR. Currently testing with DLSS set to Balanced. Frames capped in-sim at 35 and Dynamic settings turned on at 35fps.

7800X3D, RTX 4090, 64Gb of 6000 ram.

I am not using an airliner. I am doing all my flying right now in the Beachcraft Bonanza G36, cruising at about 3000 feet.

I should also add that my Community folder has nothing in it except a couple of needed utilities and Navigraph. I removed everything else for testing.

Everything seems like its doing very well, except for those takeoffs to about 600 ft. I have tried at KLAS, KJFK,and KMIA so far.

autoFPS settings: General: Fixed, NFR or VR, FPS: 35, Flight type: VFR, FPS Sensitivity, Sens 5, TLOD base min: 50@1000ft, 800@6000, Extra 1.5, TLOD Top Max: 800@6000, AutoLOD Base: 100@2000, OLOD Top: 20@10000

I akm hoping someone can tell me what to try to get takeoffs under control instead of stutter fests.

Thanks all.

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 😄

Edited May 9May 9 by Reset XPDR

Is there a way to adjust the GPU load max down.  From google searches it seems this used to be a setting in the config file.  Autofps is working great, but I would like it to be a little less aggressive at maxing out my GPU load as it ups the TLODs.  I have already slightly adjusted the VRAM settings in the config file to do the same.  Thanks for this great program. Very happy with current performance of SU5 in VR with Quest 3 with a gpu that is becoming dated (3080ti)

Jim

5 hours ago, Jeld said:

Is there a way to adjust the GPU load max down.  From google searches it seems this used to be a setting in the config file.  Autofps is working great, but I would like it to be a little less aggressive at maxing out my GPU load as it ups the TLODs.  I have already slightly adjusted the VRAM settings in the config file to do the same.  Thanks for this great program. Very happy with current performance of SU5 in VR with Quest 3 with a gpu that is becoming dated (3080ti)

Jim

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.

Great mod!  Started flight sim on the Commodore 64 back in the '80's. I've been using farming simulator 22 for 4 years dealing with TLOD on it as well but unfortunately cannot change settings on the fly. I have it running buttery smooth finally on two settings that made all the difference (shadows from high to medium). I would love to become a tester as I really enjoy tinkering and can give feedback when I get time. I'm running the 5.0.2 version and would like to try the latest. Only stuttering I get is coming in for a landing. Only does it for a few seconds before touchdown. I try and follow everything and still learning the different Alt adjustments.  when I first tried the  simulator it started really bad on takeoff. friend your mod under Auto settings and everything's perfect except landing. let me know if there's a link I can download the latest and keep trying. appreciate it 

 

1 hour ago, Badlanz said:

Great mod!  Started flight sim on the Commodore 64 back in the '80's. I've been using farming simulator 22 for 4 years dealing with TLOD on it as well but unfortunately cannot change settings on the fly. I have it running buttery smooth finally on two settings that made all the difference (shadows from high to medium). I would love to become a tester as I really enjoy tinkering and can give feedback when I get time. I'm running the 5.0.2 version and would like to try the latest. Only stuttering I get is coming in for a landing. Only does it for a few seconds before touchdown. I try and follow everything and still learning the different Alt adjustments.  when I first tried the  simulator it started really bad on takeoff. friend your mod under Auto settings and everything's perfect except landing. let me know if there's a link I can download the latest and keep trying. appreciate it 

 

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.

If I don’t use expert settings, just basic auto, should I still open gpu-z and rtss or are they not needed? And if I use AUTO, do I still set a max framerate somewhere or just let the app decide? And what about dynamic settings?

2 hours ago, Rob G said:

If I don’t use expert settings, just basic auto, should I still open gpu-z and rtss or are they not needed? And if I use AUTO, do I still set a max framerate somewhere or just let the app decide? And what about dynamic settings?

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.

I promise I will read the lovingly crafted readme tonight. You are so awesome (and very diplomatic as well) LOL. THANK YOU. 

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.

 

Quite happy to update manually, but on my current 0.5.0.0 version I don't see an auto update option. I cloud have sworn I used to see it on other/older versions. I'll grab 0.5.1.0 and see if it reappears 😉

0.5.1.0 installed fine - with that option. I think I wasn't seeing the option because 0.5.0.0 was a test version <?>.

As ever - huge thank you for this incredible addon.

Edited May 13May 13 by Adamski_NZ

3 hours ago, Adamski_NZ said:

Quite happy to update manually, but on my current 0.5.0.0 version I don't see an auto update option. I cloud have sworn I used to see it on other/older versions. I'll grab 0.5.1.0 and see if it reappears 😉

0.5.1.0 installed fine - with that option. I think I wasn't seeing the option because 0.5.0.0 was a test version <?>.

As ever - huge thank you for this incredible addon.

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.

Edited May 13May 13 by Reset XPDR

How do I prevent AutoFps from descreasing TLOD when MSFS is not focused and therefore FG is not working? 

AutoFps detects 36 FPS (native, without FG) and descreases TLOD whereas performance is good and its only FG not being active in this moment.

FG inactive is correctly detected but TLOD is still beeing decreased.

Thank you!

12 hours ago, CallsignBA said:

How do I prevent AutoFps from descreasing TLOD when MSFS is not focused and therefore FG is not working? 

AutoFps detects 36 FPS (native, without FG) and descreases TLOD whereas performance is good and its only FG not being active in this moment.

FG inactive is correctly detected but TLOD is still beeing decreased.

Thank you!

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.

Edited May 14May 14 by Reset XPDR

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.

Edited May 14May 14 by TomCYYZ