Jerryyyyy

Good test. I am running a measly 3070ti but with a AMD 7950X. I can only run 100 TLOD & OLOD at typical airport without stutter. TLOD at 200 would be the kiss of death and this in clearly GPU and VRAM limited not the CPU. The aircraft makes a difference with the C-172 using 1 GB less VRAM than the B-787. With only 8GB, 1 GB is a big deal.... hence my interest in auto_fps. Looking to replace the GPU with a 5080 but not sure if even that will cut it.

HI, Just did some testing switch back to Auto TLOD from FPS Cap and the bottom line is it worked better for my Reno/SFO B787 evolution. I unchecked the + TLOD Base and set it to 100 and checked the Top and set it to 300. It went back and forth to TLOD 100 on both Reno and SFO runways and minimal stutter seemed to choose a good FPS at minimum of 50-60... will have to check log. Over the mountain to SFO TLOD went up to 500 then back down. IMHO this was working better than FPS Cap in my hands. Will send log via email.... did two flights.

Great. One change at a time. I'll volunteer to test the Beta this time and can run it through its paces. You have done a real service with this software, hope they find a place for it.

I see that it is added, but seems to be added at times on take off and on landing, when it seems to me the Base parameters should trump the add ons. I tried a decrement of 20 and that helped to get down from 500 to 100 faster but it does not necessarily make it on landing and I get stutters because the TLOD is higher that my card can handle in the complex airport environs. TLOD 300 is fine at 1000' but not at 100'. Think the principle is good may just need to see why the on the ground settings do not trump the increments... maybe increments should only be operational above a certain AGL.... and once incremented need to be able to get down fast... IMHO.

Well I am running another evolution and indeed the flight started at 300 not the 100 base TLOD and it went right up to 500 despite TLOD Top at 300, I unchecked Hr+ and restarted MSFS_AutoFPS and it still went to 500. Will see how the landing sequence goes. Seems to me an issue of initializing variables, which maybe get reset somehow later in the evolution of the running of the program.

I know how complicated this can be with many moving targets. I have a quiet Sunday and will see how it goes for a few more flights. I see the flight as I was trained in different flight segments: Takeoff; Climb-out; Cruise; Descent; Landing; and Roll-Out. I think you can set a minimum FPS that should apply to all but the TLOD seems to require rules depending up prior values or to be set individually for each flight segment... which would then require you to determine what segment you are in... I am not sure if the log was on any help, but it was to me to follow the fine changes. I'll try another flight as it is quiet here and see how it evolves. Seems there are also differences in MSFS 2024 starting fresh or restarting.... maybe my setting adjustments will be enough for government work.

Hi, I too have moved from AutoTLOD to FPS Cap and the settings seem very sensitive. This Sunday AM I flew three flights from Reno NV to SFO to fine tune settings. This is my home turf so I know what the visuals should look like. I have a 3070Ti and a Ryzen 7950. I started with FPS set at 40 and got stutters on the Runway in Reno and for some reason TLOD went to 300. Normally is 100 on runway. At cruise the FPS was fine and the TLOD went up to 500. Problem was descent and landing the 500TLOD did not dissipate and was near 300 on landing with stutters. Took me two iterations but I increased the FPS set to 50 thinking this might not allow me to go to the excessive 500 TLOD at cruise. I also increased the LOD step to 10 then 15 without problems so get a faster drop on landing. I also decreased the Alt TLOS Base to 100 as I had not seen stutters at low altitudes and this game me a longer time to get to a tolerable 100 TLOD on landing to avoid stutters. Anyway, these machinations seemed to work with an N of 1 flight. I am sending our Fearless Leader the log. Best wishes and I enjoy fine tuning this. I should do the Betas....

Is the FG issue also seen in 4.4.5 as I set the Target to 40 and it runs at 80+ Nice that it runs at 80+ but would like to increase the detail... Yup if I change the target to 20 it runs at 40-50... this is actually a nice surprise....

Thanks, what you say about the lock now makes perfect sense. I went back to Reno and could see the lock interacting with the VRAM and the detail of the image. I had cranked things up a touch and that was enough to break the VRAM bank for my 3070ti. It seems to be pretty good now that I have backed off a touch.. can get away with low settings on Aircraft, traffic but wanted medium on buildings... one aircraft moving into the scene was enough to crank up the VRAM over the threshold.... AT SFO the landing was smooth and the TLOD eventually stabilized at 80 at 500' which is the limit I set. I notice that on the runway it went to 25 and then slowly recovered. The FPS ran between 70-100 was set to 60. All in all this is probably optimal for my poor old graphics card. I could fine tune it but your defaults on VRAM seem to be fine... kinda circulates around 96% on the runway... watched it for a bit. I think the airports plays a big roles here... how well it is rendered... Reno a small airport runs slower in effect than SFO a huge place... but probably carefully optimized by MS/ASCOBO because of its popularity... the community paid version runs slow with lots more details....

I continue to fine tune my setting and wanted to do a little sanity check here... very happy with the software and a shame cannot be mentioned in the MSFS Forum as there are tons of people there that could benefit... I am getting better results with a minimal care than many are with high end cards. My current settings are: General: Target FG Active FPS 60 Shows: FG Active | ATLOD Day 80-400 Expert Options: Auto TLOD LOD Step 5 TLOD Base (checked) 80 TLOD Top + (unchecked) 400 - (checked) Alt TLOD Base 500 alt TLOD Top 5000 (checked) decrease Cloud Density 98/90 (checked) Auto OLOD OLD @ Base 100 OLOD @ Top 20 Alt OLOD Base 2000 Alt OLOD Top 10000 I test this on a flight between Reno and San Francisco using LNAV and VNAV and shoot a coupled approach so data are very good. I run at 120 to 70 FPS with the 70 being on the runway in Reno or SFO.... this I like as it gives me a lot of headroom and a smooth immersive experience, however, the detail is low. At altitude in cruise the TLOD goes up to 400 and the OLOD down to 20 and the view is fine. I would like to crank up the detail a bit to optimize the image. I think I will try first to Increase the TLOD Base to 100. I have most of the objects turned off except the airplanes at low. I do not understand why it shows TLOD orange at 25 with a lock on the runway at takeoff with a FPS of 102? I would think it should show higher than that? Anyway, fine product and like to master the details. Jerry Y PS Tried to change the TLOD to 100 and got stutters on the runways both at Reno and SFO, so this look like the limit of my system. Backedoff to 80 and no stutters. PPS I noticed also that at altitude my TLOD has gone all the way up to 750, which seems overkill. PPPS And I cannot seem to change the Clound Cover Quality Recover value, which seems fixed at 80.. change and it goes back... 90 might work best for me.

Yes, I confirmed GPU-Z is running fine. I see it in the app and it says: FGActive ATLOD Day 70-100 GPU 98% (varies) VRAM+ 93% (varies) AutoMeth Auto TLOD LOD Step 5 LOD Base + (unchecked) 70 LOD Top + (unchecked) - (checked) Running at 60-120 FPS mostly at 100 and 60 landing at JFK or SFO... comments appreciated. Great work! MS should hire you... their developer talk was pretty lame... seemed to give up on how to control VRAM usage.

Hi, Seems to be working fine and I sent the latest log via message since I had had trouble in the past. I noticed this in the log: GPU-Z companion app not running... reading the documentation does this have to be started manually and its config file edited? I see talk of many updates. Is this because of some of the updates? Running 2.62.0. Anyway started it manually and ran another flight and the results are excellent. Will send the revised log. Nice work! My only problem is my FPS is running too high! 🙂 Need to get the details up, but that will be fun!

On the stutter fest on landing that is when the runway takes up the largest percent of the screen... in an ever increasing proportion. If this is texture mapped, which I guess it must be, you are throwing an increasing amount of texture at the GPU. In this case I think the best countermeasures in MSFS 2024 is the limit the detail of the textures (you hardly notice them on the runways). Anyway, has been food for thought. PS Have been checking settings and have a nice ILS set up leaving San Jose and landing San Francisco... running autoFPS on the ILS under autopilot gives a fair test of different settings.

Yes meant TLOD... the 787 is descenting at about 900' FPM Maybe this is the solution: "disable TLOD Min + and your TLOD will go to TLOD Min by Alt TLOD Min." log says a lot... I was running wonderfully at >100 FPS and TLOD of 200 just until right above runway (which is maximum load do to texture) and then got a couple stutters as it tried to adjust but think the changes came too fast for it to adjust: 2025-02-02 15:38:21.594 [INF] [ LODController:UpdateVariables ] FPS:113 FGAct:True Pri:FPS+ 146 Night:False TLOD:200 TLODRng:196-200 Mtns+:0 OLOD:100 AGL:1035 FPM:-829 Clouds:Ultra 2025-02-02 15:38:32.787 [INF] [ LODController:UpdateVariables ] FPS:107 FGAct:True Pri:FPS+ 146 Night:False TLOD:200 TLODRng:196-200 Mtns+:0 OLOD:100 AGL:881 FPM:-837 Clouds:Ultra 2025-02-02 15:38:43.939 [INF] [ LODController:UpdateVariables ] FPS:110 FGAct:True Pri:FPS+ 146 Night:False TLOD:200 TLODRng:196-200 Mtns+:0 OLOD:100 AGL:727 FPM:-830 Clouds:Ultra 2025-02-02 15:38:55.230 [INF] [ LODController:UpdateVariables ] FPS:109 FGAct:True Pri:FPS+ 146 Night:False TLOD:200 TLODRng:196-200 Mtns+:0 OLOD:100 AGL:570 FPM:-826 Clouds:Ultra 2025-02-02 15:39:06.559 [INF] [ LODController:UpdateVariables ] FPS:108 FGAct:True Pri:FPS+ 146 Night:False TLOD:200 TLODRng:196-200 Mtns+:0 OLOD:100 AGL:414 FPM:-825 Clouds:Ultra 2025-02-02 15:39:17.706 [INF] [ LODController:UpdateVariables ] FPS:100 FGAct:True Pri:FPS+ 146 Night:False TLOD:200 TLODRng:196-200 Mtns+:0 OLOD:100 AGL:261 FPM:-824 Clouds:Ultra 2025-02-02 15:39:29.067 [INF] [ LODController:UpdateVariables ] FPS:78 FGAct:True Pri:TLOD+ 146 Night:False TLOD:197 TLODRng:196-200 Mtns+:0 OLOD:100 AGL:95 FPM:-815 Clouds:Ultra 2025-02-02 15:39:36.142 [INF] [ LODController:RunTick ] TLOD Min + auto-reduced to 110 2025-02-02 15:39:50.698 [INF] [ LODController:RunTick ] TLOD Min + auto-reduced to 80 2025-02-02 15:40:14.444 [INF] [ LODController:UpdateVariables ] FPS:65 FGAct:True Pri:TLOD+ 80 Night:False TLOD:130 TLODRng:130 Mtns+:0 OLOD:100 AGL:15 FPM:-1 Clouds:Ultra 2025-02-02 15:43:29.546 [INF] [ MainWindow:LoadSettings ] Expert:True Mode:FG ATgtFPS:False FltType:IFR TgtFPS:60 TLODMethod:Sens Tol:1 TMin:50 TMin+:true TMax:200 TMax+:True MtnAltMin:5000 TLODMaxExtra:200 TMax-:True TLODBAlt:100 MaxDesRate 2000 CustomOLOD:True OLODB:100 OLODT:20 OLODBAlt:2000 OLODTAlt:10000 CloudQ:True CloudQMethod:TLOD CRecovT:100 CRecov+:False Pause:False Vh:96% Vr:98% Will try to see if I can message the full log... thanks... seems almost perfect!

Hi, I have been doing a lot of tuning of MSFS 2024 with my 3070ti and basically I have it running at 100+FPS in the air at cruise and down to 60 on complex runways such as SFO. I got it to behave by fixing the OLOD and TLOD to 100 and setting the texture resolution to low. It looks OK. 2025-01-31 19_39_47-MSFS 2024 Settings Flight Simulator.xlsx - Excel.jpg If I run MSFS 2024 it will start out at OLOD of 100 but quickly ramp up to 200+ which may be OK for takeoff on a simple runway and at cruise where OLOD will go to 400 but on descent and landing the OLD does not decline/reduce fast enough to get it down to 100 for the landing... which stutters when it is like 150 or so. I have included screen shots, but they are a bit of a pain to load... and I am wondering if there is a way to use the expert settings to ensure that I am down to an OLOD of 100 on landing?????? https://1drv.ms/i/s!Aqm40iCIkDljgYv4YpSeNsWYgUyC138?e=9nbtge I like having the maximum OLOD at cruise and it is nice that Autofps moves the OLOD up when I have excess FPS, just does not move it down fast enough when the situation gets marginal. The 3071 ti is very happy at 5.5 GB VRAM; ok at 6.0 but stutters at 6.5..... Appreciate any help, understand this is a bit on the edge.... but maybe you can offer some help on tweaking the settings??? Jerry Y

Thanks, Glancing at the huge number of posts here I guessed I was overthinking the problem and decided to fly my milk run from Reno to SFO in the non-expert model with defaults. Well, of course the results were better FPS including 40 on landing. I could see the trade off was the TLOD was lower and ended up at 100, which is pretty poor but does not stutter. I guess if I reset the Expert Mode it will start with these settings and maybe I can try moving up the TLOD. Just as a historical FYI I wrote a lot of flight simulator code 15+ years ago and this is what it looked like in those days: https://web.stanford.edu/~yesavage/AIR.html Jerry Y

Hello, My first post. Am happy with AutoFPS which has saved me and my 3070ti in MSFS 2024... it can run. I have been tweeking the settings and if I can ask for a basic sanity check on these settings for a B-787 going into SFO. If possible I have the approach at about 60FPS and the landing at about 25 FPS. https://1drv.ms/i/s!Aqm40iCIkDljgYu0SNYjt4p3fFJv4_0?e=C5HPVI https://1drv.ms/i/s!Aqm40iCIkDljgYu0R4UgUAIkop-1Cs4?e=Y4iHzG Above are OneDrive images. Seems pretty complex to add images. I guess if this fauls maybe Google. JY