3 hours ago, kayjay1c6b said:

1. **Average FPS Calculation Time**:  

   I reduced the average FPS calculation time from 5 seconds to 1 second. This makes the app more responsive to changes, and I observed a significant improvement in performance. This adjustment was initially tested in Flight Sim 2020 before the 2024 release, and it had a very positive impact.  

Ironically, AutoFPS actually started out a year ago with 1 second FPS averaging but it was way too responsive, especially with frame generation and MSFS 2020's habit of stuttering on scenery loading at times, so 5 seconds was settled on being a suitable compromise and verified by many testers. A 1 second average might be OK with MSFS 2024 with its smoother overall performance, and that is something I will consider and test, but IMO nothing significant has changed with MSFS 2020's behaviour to warrant changing an age old proven 5 second average.

3 hours ago, kayjay1c6b said:

2. **Dynamic TLOD Adjustment Based on FPS Drops**:  

   I modified the FPS mode, which originally relied on altitude, to include logic that monitors FPS drops. If a drop is detected, the app dynamically lowers the TLOD. This makes the system more adaptive compared to the static altitude-based approach.  

AutoFPS already did this if the user followed the readme advice in expert settings on using Auto TLOD and setting conservative TLOD Base and Top then using TLOD Base + with a user defined FPS cap to give extra TLOD when performance overhead is available. Recently I have introduced FPS Cap to make this specific configuration of Auto TLOD easier to set, but otherwise this feature has existed since Oct 24.

 

3 hours ago, kayjay1c6b said:

3. **TLOD Adjustment Based on Aircraft Performance**:  

   I added functionality to adjust the minimum and maximum TLOD values based on the aircraft’s performance. Since performance varies significantly between different planes, this change ensures better optimization for each aircraft type.

This idea has merit so if you are happy to share the source code for it with me I will take a look at it.

3 hours ago, kayjay1c6b said:

4. **Half of Minimum TLOD for Performance Stability**:  

   The "half of the minimum TLOD" setting works as follows: if there are no FPS drops, the TLOD remains at the user-set level. However, if FPS drops occur, the app is allowed to reduce the TLOD to half of the set value. This helps maintain performance stability, especially for users who may have set their TLOD too high initially. 

This is the same as point 2. Rather than mask users setting TLODs too high, they should simply set them more conservatively in the first place, per the detailed readme instructions for a mode only available under expert settings (ie. the user should have a reasonable idea of the consequences of what settings they are making).

3 hours ago, kayjay1c6b said:

5. **Ground-Level TLOD Adjustment**:  

   I enabled the reduction to half of the TLOD to occur on the ground. This improves performance at complex airports and with complex planes, where ground-level visibility is limited and high TLOD values are unnecessary. 

Again, same as point 2.

Edited February 2, 20251 yr by Reset XPDR

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

4 hours ago, Jerryyyyy said:

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

You are saying OLOD a lot but I think you mean TLOD. In any case, if your TLOD is not reaching TLOD Min by Alt TLOD min then your Avg Descent Rate setting is not high enough for how you are descending. The readme details this setting here:

• Avg Descent Rate- Used in combination with FPS sensitivity to determine the altitude band in which TLOD will be interpolated between TLOD Min at the Alt TLOD base starting point and the lower of TLOD Max and the maximum TLOD your system can achieve while achieving at least your desired FPS target at a calculated top altitude. (200fpm - 10000fpm allowable)
  • This band ensures that, if you descend at your set Avg Descent Rate or less, that the app can decrement TLOD from TLOD Max to TLOD Min by the Alt TLOD Base without exceeding the LOD Step rate associated with the FPS sensitivity level you have set.

From your screenshot, your Avg Descent Rate is set to 2000 fpm which should be plenty for what looks like the 787 that you have in that screenshot. What rate are you descending at?

I also note that you are using TLOD Min +, which will keep the TLOD higher than TLOD Min on landing if you have the performance headroom. If this is not suitable, just disable TLOD Min + and your TLOD will go to TLOD Min by Alt TLOD Min.

Message me your log file if you still have the issue and I will tell you exactly what the issue is.

Edited February 2, 20251 yr by Reset XPDR

52 minutes ago, Reset XPDR said:

You are saying OLOD a lot but I think you mean TLOD. In any case, if your TLOD is not reaching TLOD Min by Alt TLOD min then your Avg Descent Rate setting is not high enough for how you are descending. The readme details this setting here:

• Avg Descent Rate- Used in combination with FPS sensitivity to determine the altitude band in which TLOD will be interpolated between TLOD Min at the Alt TLOD base starting point and the lower of TLOD Max and the maximum TLOD your system can achieve while achieving at least your desired FPS target at a calculated top altitude. (200fpm - 10000fpm allowable)
  • This band ensures that, if you descend at your set Avg Descent Rate or less, that the app can decrement TLOD from TLOD Max to TLOD Min by the Alt TLOD Base without exceeding the LOD Step rate associated with the FPS sensitivity level you have set.

From your screenshot, your Avg Descent Rate is set to 2000 fpm which should be plenty for what looks like the 787 that you have in that screenshot. What rate are you descending at?

I also note that you are using TLOD Min +, which will keep the TLOD higher than TLOD Min on landing if you have the performance headroom. If this is not suitable, just disable TLOD Min + and your TLOD will go to TLOD Min by Alt TLOD Min.

Message me your log file if you still have the issue and I will tell you exactly what the issue is.

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!

58 minutes ago, Jerryyyyy said:

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!

As mentioned in my message to you, and for the benefit of others, "TLODBAlt:100" is the likely reason for your flight stuttering on final appoach as this is way too low for IFR into busy airports. Set it back to the default 1000 ft and you should be able to use TLOD Min + again.

On 2/1/2025 at 7:53 PM, LIML2020 said:

The app cannot check Vram usage;  GPU-Z don't recognize my rtx 5080 

Good news. A new GPU-Z version has come out today supporting 5000 series GPUs, available here, so you should be up and running with VRAM+ now.

Love the app. Working great. Though, latest beta I too am getting stutters near major airports that weren't happening as often. Probably more to do with the sim and very little to do with the app. Though, some feedback would be good. Not sure how to upload a pic here though.....

 

The stutter fest and massive impact on performance when landing, just second before touchdown is my main problem these last days. I think MSFS_AutoFPS would help but several pointed the weird VRAM usage at this touchdown moment (https://forums.flightsimulator.com/t/fps-performance-vram-bug/668753) is not really workaround-able ;(

4 hours ago, vbazillio said:

The stutter fest and massive impact on performance when landing, just second before touchdown is my main problem these last days. I think MSFS_AutoFPS would help but several pointed the weird VRAM usage at this touchdown moment (https://forums.flightsimulator.com/t/fps-performance-vram-bug/668753) is not really workaround-able ;(

If you run GPU-Z in the background, VRAM+ will be active in the app and that could help in these VRAM overflow situations.

Yep, it's what I did since you implement the GPU-Z integration. Unfortunately, it seems not enough efficient to counteract "the MSFS bug".

4 minutes ago, vbazillio said:

Yep, it's what I did since you implement the GPU-Z integration. Unfortunately, it seems not enough efficient to counteract "the MSFS bug".

I've only made VRAM+ adjust the one thing that the app controls and the user can set that has the largest impact on VRAM use, namely TLOD. The VRAM bug is likely spread across a bunch of other MSFS settings which really needs to be addressed internally by Asobo rather than apps like mine putting a band-aid on externally, but at least AutoFPS trys to do something about it.

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. 

Edited February 4, 20251 yr by Jerryyyyy
clarity

Hi.  Since installing the latest update I notice that my OLOD never gets above 15, even when on the ground.  It used to always get up to 150 when on ground.  I do not use Expert Options and I am running it as IFR with FG active.  HAs this factor changed in the non-expert settings?

1 hour ago, John Hambly said:

Hi.  Since installing the latest update I notice that my OLOD never gets above 15, even when on the ground.  It used to always get up to 150 when on ground.  I do not use Expert Options and I am running it as IFR with FG active.  HAs this factor changed in the non-expert settings?

Nothing changed relating to OLOD automation in the latest update, nor for many versions actually.

The most likely cause is that your default MSFS setting for OLOD, which the automation logic uses as the basis for the settings it makes, has changed to a low value. Normally this app restores the correct default settings if MSFS CTDs but in rare circumstances it may not be reset correctly.

All you need to do is go into your MSFS settings without this app running (important) and set your OLOD back to what it should be (150 from the sounds of it). Also check your TLOD and Cloud Quality settings while you are there.

Then fire up the app and all should be good again in non-expert mode. Let me know if otherwise.

Seems to have worked!  Thanks!