On 7/1/2026 at 7:55 AM, Reset XPDR said:

for @kevinfirth who asked this, and anyone else willing and able, please give it a try.

I've been able to reproduce the 'spiky' conditions in the same scenario as before.

AutoFPS does detect these, and reduces TLOD, but when doing so it doesn't drop incrementally, but straight to TLOD Base Min - is that right?

I've got it to TLOD 900, OLOD 1000, in drone cam view towards central london, 47Gb system RAM and 29 Gb of VRAM in use. All smooth, no stutters. From this I'd say the photogrammetry import code seems pretty solid by itself.
Introduce an aircraft though and it goes to pot.
So, I backed it down to TLOD 80, no stutters, AutoFPS doesn't up the TLOD to find the boundary?

Edited July 5Jul 5 by kevinfirth

6 hours ago, kevinfirth said:

I've been able to reproduce the 'spiky' conditions in the same scenario as before.

AutoFPS does detect these, and reduces TLOD, but when doing so it doesn't drop incrementally, but straight to TLOD Base Min - is that right?

I've got it to TLOD 900, OLOD 1000, in drone cam view towards central london, 47Gb system RAM and 29 Gb of VRAM in use. All smooth, no stutters. From this I'd say the photogrammetry import code seems pretty solid by itself.
Introduce an aircraft though and it goes to pot.
So, I backed it down to TLOD 80, no stutters, AutoFPS doesn't up the TLOD to find the boundary?

Up until Test5, the app was reducing TLOD in your sensitivity setting steps, which was 15 in your last screen shot in this, then since it reduces a 4 times that rate, ie. 60 in your case, otherwise it takes too long to remove the spiking situation. It should therefore only ever drop straight to TLOD Base Min if you were within one reduction step of being back at TLOD Base Min. eg here is the line that calculates how much to reduce TLOD by:

Model.SpikeTLODReductionAmount = Math.Min(Model.SpikeTLODReductionAmount + 4 * Model.FPSTolerance[Model.activeProfile], Model.MaxTLOD[Model.activeProfile] - Model.MinTLOD[Model.activeProfile]);

If you backed TLOD down to 80 and it did not increase TLOD to find the upper boundary, then something is preventing the increases like FPS not being high enough versus your target FPS, settle being currently active, MSFS and being paused or in a menu, MSFS not having focus when using FG, or spike detection had already kicked in and that was your new limit. FYI, as of Test5, the app can now find very low level periodic spiking, which can be very hard to see on the RTSS OSD graph but is quite obvious in the frametime data set, so it is possible your settings already have you in spiking territory. If that is it, I can back off the sensitivity if you want, but that then waters down what you asked for.

In any case, this is mostly speculation on my part. I really need to see your log file, located in %appdata%\MSFS_AutoFPS\log, associated with this to know for sure with both of these, so can you PM me the contents of it and we will take it from there.

Also, please always make sure you are on the latest test version, as this capability often improves notably with each test version, as it did in particular with Test5. The simplest way to do it is to have Silent Updates and Test+ as your app update options, which will automatically update your app to the latest test version if a new one is available as soon as the app starts and will then start up with the newest one.

Edited July 6Jul 6 by Reset XPDR

Here is an example run showing how periodic spike detection works. This is with Test6, not released yet, which has only cosmetic changes from Test5 so far, so effectively the same. The scenario is at default KSFO, Gate 9, default 787, default Ultra 4K graphics settings with DLSS Balanced:

Firstly, initial setup by the app at TLOD 100:

2026-07-06 12:04:24.118 [INF] [ ServiceController:ServiceLoop ] Setting Initial LODs @ 14 ft AGL to 100 / 200
2026-07-06 12:04:25.448 [INF] [ MainWindow:LoadSettings ] MSFS:24 Expert Mode:NFR TgtFPSOpt:Fixed FltType:Test TgtFPS:20 TLODMethod:Sens Tol:20 SProt TMin:100 TBXtra TBXtraMult:15 FreeTLOD TMax:1500 TLODBAlt:1000 TLODTAlt:4000 CustomOLOD OLODB:200 OLODT:20 OLODBAlt:1000 OLODTAlt:5000 MaxLOD:2000

TLOD starts increasing rapidly towards 1500. Twice it encounters what looks like a periodic spike sequence, but after a 2 second TLOD change pause it disappears, meaning it was a side effect of the rapidly increasing TLOD from the app and not the MSFS graphics engine being consistently overloaded, so it gets ignored. Note having a high Sens value of 20 like I have will stress the MSFS graphics engine, and I was only doing so in this case to demonstrate the app's ability to distinguish from an own goal detection.

2026-07-06 12:04:34.333 [INF] [ LODController:UpdateVariables ] Mode:NFR FPS:40 Pri:FPS TLOD:180 TLODRng:100-1500 OLOD:200 AGL:14 FPM:-0 GPU:58% VRAM:76%
2026-07-06 12:04:42.488 [DBG] [ ServiceController:DetectPeriodic ] Total Spikes: 12, Periodic Spikes: 4, AvgInterval: 0.84s, StdDev: 0.09s, SteadyAvg: 26.3569ms, SteadyStd: 5.2764ms, SpikeFreeAvg: 25.1847ms, SpikeFreeStd: 0.8776ms, SpikeAvg: 37.1436ms, SpikeStd: 6.0190ms, Detected: True
2026-07-06 12:04:42.489 [INF] [ LODController:RunTick ] 2 second periodic spike TLOD reduction verification started
2026-07-06 12:04:44.525 [INF] [ LODController:RunTick ] 2 second periodic spike TLOD reduction verification ended with no continued detection
2026-07-06 12:04:54.720 [INF] [ LODController:UpdateVariables ] Mode:NFR FPS:39 Pri:FPS+ 618 TLOD:718 TLODRng:100-1500 OLOD:200 AGL:14 FPM:-0 GPU:63% VRAM:85%
2026-07-06 12:05:02.916 [DBG] [ ServiceController:DetectPeriodic ] Total Spikes: 9, Periodic Spikes: 4, AvgInterval: 1.27s, StdDev: 0.06s, SteadyAvg: 28.1147ms, SteadyStd: 6.1386ms, SpikeFreeAvg: 27.4634ms, SpikeFreeStd: 2.3204ms, SpikeAvg: 36.3774ms, SpikeStd: 1.7881ms, Detected: True
2026-07-06 12:05:02.916 [INF] [ LODController:RunTick ] 2 second periodic spike TLOD reduction verification started
2026-07-06 12:05:04.961 [INF] [ LODController:RunTick ] 2 second periodic spike TLOD reduction verification ended with no continued detection
2026-07-06 12:05:15.181 [INF] [ LODController:UpdateVariables ] Mode:NFR FPS:32 Pri:FPS+ 885 TLOD:985 TLODRng:100-1500 OLOD:200 AGL:14 FPM:-0 GPU:61% VRAM:89%
2026-07-06 12:05:25.397 [INF] [ LODController:UpdateVariables ] Mode:NFR FPS:31 Pri:FPS+ 1030 TLOD:1130 TLODRng:100-1500 OLOD:200 AGL:14 FPM:-0 GPU:64% VRAM:90%

Finally, just passing TLOD 1200, periodic spikes are detected again, but this time they persist when TLOD changes are paused so this is a true MSFS graphics engine overload, so down the TLOD comes until at TLOD 884 the spikes are no longer present:

2026-07-06 12:05:35.634 [INF] [ LODController:UpdateVariables ] Mode:NFR FPS:29 Pri:FPS+ 1104 TLOD:1204 TLODRng:100-1500 OLOD:200 AGL:14 FPM:0 GPU:60% VRAM:92%
2026-07-06 12:05:35.635 [DBG] [ ServiceController:DetectPeriodic ] Total Spikes: 7, Periodic Spikes: 5, AvgInterval: 1.13s, StdDev: 0.04s, SteadyAvg: 35.2645ms, SteadyStd: 6.6278ms, SpikeFreeAvg: 33.9730ms, SpikeFreeStd: 2.3029ms, SpikeAvg: 57.9797ms, SpikeStd: 10.4702ms, Detected: True
2026-07-06 12:05:35.635 [INF] [ LODController:RunTick ] 2 second periodic spike TLOD reduction verification started
2026-07-06 12:05:36.654 [DBG] [ ServiceController:DetectPeriodic ] Total Spikes: 7, Periodic Spikes: 5, AvgInterval: 1.14s, StdDev: 0.03s, SteadyAvg: 35.7395ms, SteadyStd: 6.9187ms, SpikeFreeAvg: 34.2731ms, SpikeFreeStd: 2.4344ms, SpikeAvg: 60.4975ms, SpikeStd: 8.1877ms, Detected: True
2026-07-06 12:05:37.680 [DBG] [ ServiceController:DetectPeriodic ] Total Spikes: 7, Periodic Spikes: 6, AvgInterval: 1.14s, StdDev: 0.03s, SteadyAvg: 36.0543ms, SteadyStd: 7.1137ms, SpikeFreeAvg: 34.4614ms, SpikeFreeStd: 2.4040ms, SpikeAvg: 60.6386ms, SpikeStd: 7.5882ms, Detected: True
2026-07-06 12:05:37.680 [INF] [ LODController:RunTick ] 2 second periodic spike TLOD reduction verification ended with continued detection
2026-07-06 12:05:37.680 [INF] [ LODController:RunTick ] Automatic periodic spike TLOD reduction activated
2026-07-06 12:05:38.698 [DBG] [ ServiceController:DetectPeriodic ] Total Spikes: 8, Periodic Spikes: 6, AvgInterval: 1.16s, StdDev: 0.05s, SteadyAvg: 36.4604ms, SteadyStd: 7.9169ms, SpikeFreeAvg: 34.5181ms, SpikeFreeStd: 2.3181ms, SpikeAvg: 63.8370ms, SpikeStd: 11.2111ms, Detected: True
2026-07-06 12:05:39.717 [DBG] [ ServiceController:DetectPeriodic ] Total Spikes: 9, Periodic Spikes: 6, AvgInterval: 1.16s, StdDev: 0.05s, SteadyAvg: 36.8457ms, SteadyStd: 8.0009ms, SpikeFreeAvg: 34.8069ms, SpikeFreeStd: 2.2270ms, SpikeAvg: 62.0141ms, SpikeStd: 10.4129ms, Detected: True
2026-07-06 12:05:40.739 [DBG] [ ServiceController:DetectPeriodic ] Total Spikes: 10, Periodic Spikes: 7, AvgInterval: 1.15s, StdDev: 0.07s, SteadyAvg: 36.7055ms, SteadyStd: 7.1040ms, SpikeFreeAvg: 34.9154ms, SpikeFreeStd: 2.0921ms, SpikeAvg: 61.2274ms, SpikeStd: 9.9603ms, Detected: True
2026-07-06 12:05:45.853 [INF] [ LODController:UpdateVariables ] Mode:NFR FPS:29 Pri:FPS+ 784 SRed:616 TLOD:884 TLODRng:100-1500 OLOD:200 AGL:14 FPM:-0 GPU:73% VRAM:91%

Here is what it looks like graphically where:

1. The noise of rapid TLOD increases with a few false periodic spike patterns that get ignored.

2. A real periodic spike sequence starts and is sustained through the 2 second pause, so it is acted upon.

3. TLOD starts rapidly marching down to eradicate it.

4. Eradication complete, TLOD capped at this level until you have flown far and high enough away from where it happens and smooth frame times now result.

As an observation from doing this testing is that even after eliminating the periodic spikes, having resultant excessively high TLOD in a complex scenario like this is a recipe for very stuttery view changes and panning because the scenery has to quickly load for the new direction you are facing, even with MSFS OSTPC set to Ultra and VRAM no longer maxed out. My normal settings for such a scenario would be TLOD Min 50, TLOD Extra x4 (to give up to 200 on the ground) and TLOD Max 400 VR and 600 2D, in which case it is very unlikely the periodic spikes would be encountered in the first place.

Nonetheless, as @kevinfirth has experienced, a complex aircraft like the Fenix A320 may make these periodic spikes occur at a much lower TLOD than I encountered, down into the TLOD range you would normally like to use, and in that case this would be a useful protection mechanism.

Edited July 6Jul 6 by Reset XPDR

6 hours ago, Reset XPDR said:

latest test version, as this capability often improves notably with each test version, as it did in particular with Test5. The simplest way to do it is to have Silent Updates and Test+ as your app update options

Yes this is already selected
I've gone with TLOD Base Min 80 Extra x4 Start Max, with TLOD Top Max 1000 for settings
That should a) produce a low enough base that I see no spikes in the heaviest possible scenario, b) give me up to TLOD 320 on the ground in medium stress situations and up to TLOD 1000 in the air and in low stress scenarios. All with OLOD 1000.
Here's what happened:


TLOD Base starting from low - zero spikes

TLOD Base starting from high (320) - TLOD seems to be reduced partially for fps, but spike protection does not kick in, despite evident frame time issues. Wonder if this is because the spikes seem to be more prolonged and 'less spiky', more tabletop?

So I backed down Extra to x2...to see the impact. As expected, TLOD Base started at 160 rather than 320. Spikes had a different profile, as again expected. Spike protection still didn't activate.

Backing off the tests above showed that TLOD Base 70 was the absolute sweet spot, It started, and stayed at that level..

The trick appears to be to have settings that aim to achieve a 1% low at the fixed fps target level.
Then switching to a less graphically intense scenario, but with those same settings.... TLOD base starts at 70, then rapidly increases to its x4 max, all super smooth.
So, 3 things that come out of this for me.
1. Why wasn't AutoFPS upping TLOD in my first instance, when it had TLOD at 80 and spike detection hadn't activated?
2. When starting at TLOD Base max, why weren't those evident frame time issues detected as spikes?
3. For people like me, with powerful hardware, medium stress situations probably mean that we could go above Extra x4, would that be possible?

56 minutes ago, kevinfirth said:

Backing off the tests above showed that TLOD Base 70 was the absolute sweet spot, It started, and stayed at that level..

The trick appears to be to have settings that aim to achieve a 1% low at the fixed fps target level.
Then switching to a less graphically intense scenario, but with those same settings.... TLOD base starts at 70, then rapidly increases to its x4 max, all super smooth.
So, 3 things that come out of this for me.
1. Why wasn't AutoFPS upping TLOD in my first instance, when it had TLOD at 80 and spike detection hadn't activated?
2. When starting at TLOD Base max, why weren't those evident frame time issues detected as spikes?
3. For people like me, with powerful hardware, medium stress situations probably mean that we could go above Extra x4, would that be possible?

Can you PM me the contents of the logs associated with these so I can correlate with what you observed and can see what is going on. Thanks.

Also, I am about to release Test6, which I will instrument up so that it shows why it rejects a frame time sequence with a potentially valid periodic spike pattern. By the looks of it, it is either because they are outside the 0.7 to 1.8 second cadence range the app enforces or because there is so much noise in your frame time runs (it is hard to tell whether it is just the way you have set up graphing or it is ridiculously spiky, the latter condition being a rejection criteria).

Edited July 6Jul 6 by Reset XPDR

OK, Test6 is now out with the extra diagnostic logging. Due to the verbosity of this new logging, I have made it so that you have to enable Log+ for these log lines to appear, so make sure you check the Log+ checkbox before any further testing.

@kevinfirth given this is now getting into the weeds of development as it is a complex beast to quantify, let alone tame, let's take this to PMs from here on in until we have an outcome worthy of public consumption.

Ok, again a little bit lost with AutoFPS: did not have time to fly around that much recently, but it seems that I no longer have the ideal settings anymore.

Currently, I use the Nexusmod version.dll to enable 4x frame gen on my 4090. I use a FPS cap at 36 and dynamic settings at 35 inside MSFS2024. This results in pretty stable 138FPS in the sim, even on big hubs, with TLOD and OLOD both on 200. The 138FPS limit although 4x36 should give 144FPS is due to whatever reason, it only started to be like this after one of the last version.dll updates. According to their Nexus page, it is somehow related to nVIDIA Reflex? Who knows.

My "issue" is that I had 144FPS as a setting inside AutoFPS with good results. Now I realize that even if I lower this to 138FPS, the tool somehow does not equally good recognize my "FG FPS" anymore and as a result, the TLOD setting is kept low and even when flying on cruise altitude, it doesnt increase from the value I set on ground (100 in my case, with 400 top).

Should I start using the baseline FPS (36) again instead of the frame generated numbers? Does version.dll and 4x frame gen interfere with AutoFPS?

20 minutes ago, AnkH said:

Ok, again a little bit lost with AutoFPS: did not have time to fly around that much recently, but it seems that I no longer have the ideal settings anymore.

Currently, I use the Nexusmod version.dll to enable 4x frame gen on my 4090. I use a FPS cap at 36 and dynamic settings at 35 inside MSFS2024. This results in pretty stable 138FPS in the sim, even on big hubs, with TLOD and OLOD both on 200. The 138FPS limit although 4x36 should give 144FPS is due to whatever reason, it only started to be like this after one of the last version.dll updates. According to their Nexus page, it is somehow related to nVIDIA Reflex? Who knows.

My "issue" is that I had 144FPS as a setting inside AutoFPS with good results. Now I realize that even if I lower this to 138FPS, the tool somehow does not equally good recognize my "FG FPS" anymore and as a result, the TLOD setting is kept low and even when flying on cruise altitude, it doesnt increase from the value I set on ground (100 in my case, with 400 top).

Should I start using the baseline FPS (36) again instead of the frame generated numbers? Does version.dll and 4x frame gen interfere with AutoFPS?

This sounds like a possible bug. Can you PM me the section of the log file, including a settings line, where TLOD is not increasing as you expect. If you can't locate it just send me the entire log via PM. You will have to copy and and paste it as Avsim doesn't allow attachments.

Edited July 6Jul 6 by Reset XPDR

It IS increasing, but somehow it doesnt recognize the FPS properly or to be more precise, it shows the FPS number orange almost all the time, of course if I set 144FPS this is clear, but also if I use 138FPS. It shows green, TLOD increases, a second later the number gets orange and TLOD stays. Before, it was almost 90% of the time green and TLOD was constantly increasing.

Will see when I have time to get you those logs...

18 minutes ago, AnkH said:

It IS increasing, but somehow it doesnt recognize the FPS properly or to be more precise, it shows the FPS number orange almost all the time, of course if I set 144FPS this is clear, but also if I use 138FPS. It shows green, TLOD increases, a second later the number gets orange and TLOD stays. Before, it was almost 90% of the time green and TLOD was constantly increasing.

Will see when I have time to get you those logs...

If any text box goes orange, just hover your mouse over it and the tooltip will tell you what the issue is and where applicable what to do to fix it.

Not the textbox, the FPS number in the counter, the one on which TLOD increase or decrease is based on. It somehow fails to read out my FPS properly since I started using version.dll from NEXUS mods to get 4x frame gen.

11 hours ago, AnkH said:

Not the textbox, the FPS number in the counter, the one on which TLOD increase or decrease is based on. It somehow fails to read out my FPS properly since I started using version.dll from NEXUS mods to get 4x frame gen.

When you are using FG, the FPS number shows orange when MSFS doesn't have the focus to indicate that FG is no longer active. The TLOD will also show in orange, even when not changing, as that is to indicate that TLOD is currently being limited to reductions only, again because FG is inactive and automation then would otherwise be unreliable.

hey, i want to use automatic Switching of VFR/IFR Regarding what aircraft i use. i utilize Axis and Ohs for that and use a automatic script for Airlines to start AutoFPS with IFR settings and GA to start AutoFPS with VFR.

Since i want to switch it on the fly so after a flight in an Airline, i had to kill the process and restart it again. But after i kill and restart the AutoFPS it wont connect to MSFS anymore, Simconnect and Session stays red.

Any ideas how i can get this working?

1 hour ago, Bam2000 said:

hey, i want to use automatic Switching of VFR/IFR Regarding what aircraft i use. i utilize Axis and Ohs for that and use a automatic script for Airlines to start AutoFPS with IFR settings and GA to start AutoFPS with VFR.

Since i want to switch it on the fly so after a flight in an Airline, i had to kill the process and restart it again. But after i kill and restart the AutoFPS it wont connect to MSFS anymore, Simconnect and Session stays red.

Any ideas how i can get this working?

Why did you kill the AutoFPS process instead of just closing the app down normally? I am not surprised AutoFPS won't reconnect to simconnect if you kill it because you left MSFS's interface thinking AutoFPS was still connected and therefore would not allow another connection to the same app. Not only that, you didn't give the app the chance to restore all MSFS settings back to default so MSFS will be stuck in what ever state it was when you killed it.

The simple solution is to stop killing AutoFPS and just close it down normally or just manually switch between IFR and VFR in the app when you are picking your different aircraft.

Edit: I just had a thought that I could provide a command line option in the app where it auto exits the app whenever a flight ends rather than waiting for another flight to occur. Would that work?

Edited July 9Jul 9 by Reset XPDR