For @cjk28, and anyone else interested in being able to have free ranging TLOD when using an FPS cap, 0.4.6.8-test4 now has the capability to do just that when configured in a particular way, namely:

• FPS Sensitivity Mode selected
• Capped Target FPS selected
• Target FPS set to match your system-set FPS cap
• TLOD Base Min and Top Max set to the min and max TLOD you ever want to achieve
• The Extra multiplier set so that TLOD Base Min times the multiplier equals TLOD Top Max.
• Start Max is enabled

 

When set this way, no matter whether you start your flight on the ground or in the air, TLOD will start at TLOD Base Min with Extra (ie. 42 x 4), which equals TLOD Top Max (168). If performance conditions drop you below your FPS cap, TLOD will quickly and rapidly reduce enough to maintain your FPS cap, but no lower than TLOD Base Min. If performance conditions improve again, no matter what your altitude is, then TLOD will start increasing after about 30 seconds and will do so in increasing steps until either TLOD Top Max is reached or the FPS cap is breached. This effectively gives you the free ranging TLOD I believe @cjk28was desiring.

At the moment it only works this way with the new Capped Target FPS option as that is what I focused on first. I will also see if I can get it working with the Manual Target FPS as well, for those that wish to try with the normally recommended uncapped Target FPS for FPS Sensitivity mode. I will also try and come up with a simpler way to set free ranging TLOD, without having to do any multiplier maths (although the multiplier tooltip already tells you what the resultant TLOD Min will be with Extra), but for now it works well enough as a concept demonstrator. Something like the Extra checkbox being replaced with a dropdown with options of Fixed (ie. no Extra), Extra (with the existing multiplier) and Free, with no multiplier needed as I will get the app to calculate Extra internally so that TLOD Base Min + Extra = TLOD Top Max.

@cjk28, and anyone else who tries this, I'd appreciate any feedback on how this functions, without getting too worried about the currently convoluted UI aspect of it which I already aim to improve.

Edited April 14Apr 14 by Reset XPDR

working nicely, thanks so much!

i have my FPS set to 37 in autoFPS (with system cap at 40 (virtual desktop set to 80Hz with forced spacewarp) as otherwise i find TLOD seems to decrease unnecessarily (presumably due to occasional frame drop) - hopefully this doesn't invalidate the testing of this test version.

I tried launching from a demanding airport and TLOD dropped nice and quickly.

the 30s wait before considering to increasing TLOD again doesn't feel ideal but not sure if there are better options available.

i got the feeling that AutoFPS is a overly keen to reduce TLOD in response to a small frame drop, I guess the Sens and target FPS settings can be used to tune this.

Other than that, being able to open up the range so i can set my min to something lower (e.g. 20) without limiting my top max would be perfect

N.B. I noticed that the app reports GPU usage values similar to GPUZ/MSI, but I found that these values are misleading, as they are some kind of aggregated value of 3D GPU%, GPU Video encode etc, so GPU 3D 80% and GPU Video Encode of 20% (for VR users) can get reported as GPU 99%, so could adversely affect places where gpu usage is used in the app.

Edited April 14Apr 14 by cjk28

Thanks for trying it out. Re the way it has responsive drops and delay/progressive increases with TLOD is specifically designed for when you are using an FPS cap as something you always want to be achieving. ie. do everything it can to maintain it when it looks like it is going to drop and to tentatively increase it when it is reasonably safe to do so. You are not really using your FPS cap this way as you seem OK with it being a couple of FPS below that cap and while that works OK with VR headsets like the Quest 3, dropping FPS like that can cause motion reprojection to drop out or stutter on others, and in 2D it can cause tearing with older locked vsync monitors, hence the need for this specific mode.

As mentioned, I will now try to get free ranging TLOD working in uncapped mode in FPS Sensitivity mode, which will provide the less aggressive drops and faster response on the upside. I suggest you + Test ticked when the app starts so that you automatically get notified and offered an auto-update to the new test version that I put this in.

Re GPU usage reported by the app, yes it is going off what GPU-Z is telling it. I get your point that GPU load may be split between 3D and video encode, but surely that does not matter as 100% load is 100% load regardless of how it is constituted. ie. if the GPU is maxed out then it is maxed out and the app should respond accordingly. The same goes for VRAM usage in that it doesn't matter what VRAM MSFS is consuming itself, if you run out of VRAM then all apps using it will be affected by the paging to system memory that will ensue.

Edit: I have managed to get free ranging TLOD working in uncapped mode in FPS Sensitivity mode working, which will give the same responsiveness without delays for both FPS increases and decreases above the Target FPS, which is why I believe @cjk28is really looking for. I am just fixing a few other things first, then I will put it out in Test 5 for you to try.

eg. here is a graph of a quick test run with an uncapped target FPS of 60 in free range TLOD mode. You can see TLOD responds proportionally to the variance from 60 FPS, regardless of whether above or below it. AGL is provided to show that the response is the same regardless of altitude.

 

Edited April 14Apr 14 by Reset XPDR

Nice! re. the gpu-usage thing, the video encoder is separate dedicated hardware, hence why GPUZ reporting 99% can be misleading. obviously a bit of an edge case as only applies to meta quest users, but thought worth mentioning in case theres an easy to use API that gives the 3d GPU usage % that task manager shows

46 minutes ago, cjk28 said:

Nice! re. the gpu-usage thing, the video encoder is separate dedicated hardware, hence why GPUZ reporting 99% can be misleading. obviously a bit of an edge case as only applies to meta quest users, but thought worth mentioning in case theres an easy to use API that gives the 3d GPU usage % that task manager shows

I wasn't aware of that and will look into it, noting that unless I can get GPU-Z to decouple the two readings then it is likely I won't be able to do anything about it with the current design.

Some good news now that I have just released Test5 which now has free TLOD working in Manual Target FPS mode, which I believe is what you were after. I have also refined the UI so that it is much easier to select and configure, no longer requiring you to do any TLOD Extra multiplier calculations.

Simply:

• Select FPS Sensitivity mode
• Select the Manual Target FPS option
• Set your target FPS at least 1 FPS below your FPS cap (I know you have used 37 FPS previously, but it works when set to 39 FPS and will maintain your FPS cap of 40 better)
• Select Free for the TLOD Base Option
• Setting Start Max is now optional, so enable it you want to start at TLOD Max otherwise it will start at TLOD Min
• TLOD altitudes will show n/a and not be editable because they are irrelevant in Free TLOD mode.

Have a go and tell me what you think. The download link is here if you are not on auto updates.

Amazing App as always and thanks for all the improvements.

I had a little issue that might be worth noting

. I updated and was suffering for a couple of days with sound stutters in the main menu something I had a while back so I thought it might be the MSFS servers again but this time it was bad so I tried to troubleshoot. I discovered if I closed AutoFPS they went away so I did a bit more digging. I must have  checked the Use the Physical Cores Button + High Priority. I am running a AMD Ryzen 9 7900X3D Chip so I thought it mentioned that it was making it use the core with the most cache so I downloaded a CCD Visualizer and saw that Auto FPS was I think cutting out some of the cores on that CCD which was leading to the audio stuttering. I am not that advanced in how this all works but thought I would let you know.

I am attaching the Core Visualizer with the normal set up then the one with AUTO FPS Physical Cores Box ticked so you can see the difference...

 

[img]https://i.ibb.co/xKvSxNDm/Corem-Mask-Cache.jpg[/img]

 

[img]https://i.ibb.co/Y7LR7fBD/Auto-FPS-Physical-Cores.jpg[/img]

 

All the best

 

Hamish

 

These Screenshots wont appear unfortunately and I am not sure why so if you want to see them please message me and I will send an email or Google Drive them...

 

 

 

 

 

 

 

 

 

Edited April 15Apr 15 by Hamish100
Cant Upload Photo

10 minutes ago, Hamish100 said:

Amazing App as always and thanks for all the improvements.

I had a little issue that might be worth noting

. I updated and was suffering for a couple of days with sound stutters in the main menu something I had a while back so I thought it might be the MSFS servers again but this time it was bad so I tried to troubleshoot. I discovered if I closed AutoFPS they went away so I did a bit more digging. I must have  checked the Use the Physical Cores Button + High Priority. I am running a AMD Ryzen 9 7900X3D Chip so I thought it mentioned that it was making it use the core with the most cache so I downloaded a CCD Visualizer and saw that Auto FPS was I think cutting out some of the cores on that CCD which was leading to the audio stuttering. I am not that advanced in how this all works but thought I would let you know.

I am attaching the Core Visualizer with the normal set up then the one with AUTO FPS Physical Cores Box ticked so you can see the difference...

 

When AutoFPS sets physical cores, it only does so for the MSFS process, not every process, so it should not affect any other running app, including itself. The reason it may look like AutoFPS has set a global affinity is that MSFS tends to hog most of the CPU time anyway, but if you look closely at the graphs you posted you can see there is load on all the other cores. If you want me to tell you for sure, copy/paste the early part of your log file (located in %appdata%\MSFS_AutoFPS\log) for a run of the app when you have it enabled and I will take a look. The relevant lines look something like this:

2026-04-12 21:18:03.037 [INF] [ ServiceModel:ApplyPerfOptAffinit ] Captured original affinity=0xFFF 
2026-04-12 21:18:03.037 [INF] [ ServiceModel:ApplyPerfOptAffinit ] Universal physical‑cores‑only mask built. Mask=0x555 
2026-04-12 21:18:03.038 [INF] [ ServiceModel:ApplyPerfOptAffinit ] Affinity applied to MSFS. 6 physical cores allocated 
...
2026-04-12 21:18:03.171 [INF] [ MemoryManager:GetOptSettings     ] CPU: 11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz
2026-04-12 21:18:03.173 [INF] [ MemoryManager:LogCpuSummary      ] Core 0: CoreType=SMT Pair, LogicalProcessors=[0,1], EfficiencyClass=0 
2026-04-12 21:18:03.173 [INF] [ MemoryManager:LogCpuSummary      ] Core 1: CoreType=SMT Pair, LogicalProcessors=[2,3], EfficiencyClass=0 
2026-04-12 21:18:03.173 [INF] [ MemoryManager:LogCpuSummary      ] Core 2: CoreType=SMT Pair, LogicalProcessors=[4,5], EfficiencyClass=0 
2026-04-12 21:18:03.173 [INF] [ MemoryManager:LogCpuSummary      ] Core 3: CoreType=SMT Pair, LogicalProcessors=[6,7], EfficiencyClass=0 
2026-04-12 21:18:03.173 [INF] [ MemoryManager:LogCpuSummary      ] Core 4: CoreType=SMT Pair, LogicalProcessors=[8,9], EfficiencyClass=0 
2026-04-12 21:18:03.173 [INF] [ MemoryManager:LogCpuSummary      ] Core 5: CoreType=SMT Pair, LogicalProcessors=[10,11], EfficiencyClass=0 
2026-04-12 21:18:03.174 [INF] [ MemoryManager:LogCpuSummary      ] CPU Core Summary: Physical=6, Logical=12, SMT Cores=6, Single Cores=0 

In your case with a 7900X3D, it should have detected that you have 12 physical cores (6 on each CCD) and if you chose single CCD only when if gave you the option then the first 6 cores would have been selected. While I don't have a 7900X3D, my gaming laptop has a i5-11400H, which has 6 physical core and I did test the app with that feature enabled to make sure it wasn't too much for six cores and there were no issues at all.

In any case, the reason I made the feature optional is because what may work for some may not work for others, so in your case it may be worth turning off one or both of those features if they do not give your system any improvement or cause audio stuttering as you experienced.

 

Ah yes I ticked the box I did not realise you can have it selected without having to have it use the first CCD only but unfortunately it gives worse performance than allowing it to use all the cores. There is a program called CPU Set Setter that allows you to make sure MSFS uses the first CCD Cache but also keeps the other CCD working whereas it also has a setting called 'Cache No SMT' which behaves the same as Auto FPS it blocks six of the cores on that die so to speak. Next time I run MSFS I will enable the first CCD in Auto FPS and grab the log for you.

 

Thanks

 

Hamish

 

I could not find the exact same part you had but does this help?

 

2026-04-15 16:29:15.803 [INF] [ MainWindow:PromptForAmdFirstCcdC ] AMD First‑CCD mode enabled by user choice 
2026-04-15 17:04:33.824 [INF] [ MemoryManager:MemoryManager      ] MSFS successfully attached after 2 attempts 
2026-04-15 17:04:33.829 [INF] [ ServiceModel:ApplyPerfOptAffinit ] Captured original affinity=0xFFFFFF 
2026-04-15 17:04:33.829 [INF] [ ServiceModel:ApplyPerfOptAffinit ] Universal physical‑cores‑only mask built. Mask=0x555555 
2026-04-15 17:04:33.829 [INF] [ ServiceModel:ApplyPerfOptAffinit ] AMD first‑CCD filter applied. Using 6 physical cores. Mask=0x555 
2026-04-15 17:04:33.830 [INF] [ ServiceModel:ApplyPerfOptAffinit ] Affinity applied to MSFS. 6 physical cores allocated 
2026-04-15 17:04:33.831 [INF] [ MemoryManager:GetActiveDXVersion ] Steam MSFS2024 version 1.6.34.0 detected - DX12 
2026-04-15 17:04:33.841 [INF] [ MemoryManager:GetOptSettings     ] GPU: NVIDIA GeForce RTX 4080 
2026-04-15 17:04:33.841 [INF] [ MemoryManager:GetOptSettings     ] CPU: AMD Ryzen 9 7900X3D 12-Core Processor           
2026-04-15 17:04:33.842 [INF] [ MemoryManager:LogCpuSummary      ] CPU Core Summary: Physical=12, Logical=24, SMT Cores=12, Single Cores=0 
2026-04-15 17:04:33.843 [INF] [ MemoryManager:GetOptSettings     ] RAM: 64 GB 
2026-04-15 17:04:33.843 [INF] [ MemoryManager:GetOptSettings     ] Successfully read required settings from UserOpt.cfg 
2026-04-15 17:04:33.843 [DBG] [ MemoryManager:MemoryManager      ] Primary compatibility test bypassed due to previous saved pass found for current MSFS/app/offset combo 
2026-04-15 17:04:33.843 [DBG] [ MemoryManager:MemoryManager      ] Secondary compatibility test bypassed due to previous saved pass found for current MSFS/app/offset combo 
2026-04-15 17:04:33.876 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 5s between Retries 
2026-04-15 17:05:39.166 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2026-04-15 17:06:17.425 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2026-04-15 17:06:17.747 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2026-04-15 17:06:18.496 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2026-04-15 17:06:19.560 [INF] [ IPCManager:WaitForSessionReady   ] Session not ready - waiting 5s between Retries 
2026-04-15 17:09:05.110 [DBG] [ MemoryManager:GetOptSettings     ] Backing up pre flight session state UserCfg.opt file 
2026-04-15 17:09:05.121 [DBG] [ MemoryManager:GetOptSettings     ] Backed up UserCfg.opt file exact match of original.  Keeping backed up file... 
2026-04-15 17:09:05.123 [INF] [ MemoryManager:GetOptSettings     ] Successfully read required settings from UserOpt.cfg 
2026-04-15 17:09:05.125 [INF] [ ServiceModel:UpdateDynamicSettin ] Dynamic Settings disabled 
2026-04-15 17:09:05.131 [INF] [ LODController:GetMSFSState       ] Initial graphics mode FSR3 
2026-04-15 17:09:05.165 [INF] [ LODController:LODController      ] GPU-Z companion app not running 
2026-04-15 17:09:05.166 [INF] [ ServiceController:ServiceLoop    ] Starting Service Loop 
2026-04-15 17:09:05.166 [INF] [ ServiceController:ServiceLoop    ] Initial LODs PC 400 / 200 and VR 50 / 50 
2026-04-15 17:09:05.166 [INF] [ ServiceController:ServiceLoop    ] Initial Cloud Quality PC Ultra / VR Med 
2026-04-15 17:09:05.166 [INF] [ ServiceController:ServiceLoop    ] Initial Off Screen Terrain Pre-Caching PC Ultra / VR Low 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Terrain Shadows Enabled PC Enabled / VR Enabled 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Terrain Shadows PC 1024 / VR 256 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Raytraced Shadows PC Enabled / VR Disabled 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Displacement Mapping PC Disabled / VR Disabled 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Buildings PC High / VR Low 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Trees PC High / VR Low 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Plants PC High / VR Low 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Grass PC High / VR Low 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Parked Aircraft Quantity PC Off / VR Off 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Aircraft Traffic Quantity PC High / VR Off 
2026-04-15 17:09:05.167 [INF] [ ServiceController:ServiceLoop    ] Initial Dynamic Settings PC Disabled / VR Enabled @ 60 
2026-04-15 17:09:06.176 [INF] [ ServiceModel:ResetCloudsTLOD     ] FPS source set to MSFS 
2026-04-15 17:09:06.179 [INF] [ ServiceModel:ResetCloudsTLOD     ] Full reset of LODs, clouds, graphics mode and Auto Target FPS states activated 
 

I started a separate thread for this but wanted to duplicate it here in case it might have something to do with AutoFPS.

 

OK, I guess I should start with some background. I have a 7800X3D CPU, RTX 4090 GPU, and 64GB of 6000hz memory. I am using AutoFPS with FPS Cap, FPS set to 35 in AutoFPS, Max Framerate in sim, and Dynamic Settings in sim.

All of my testing is with the Beachcraft Bonanza G36 Mod.

What I am experiencing, in both 2D and VR, is that certain functions, when invoked, cause a stutter, while during normal straight flight I do not have stuttering.

For instance, I take off just fine. Right after takeoff, I hit the control to put up the wheels. That causes a stutter. Then shortly after I hit the control to put up the flaps. That causes a stutter. Opening the toolbar and doing something from there causes a stutter.

Looking at GPU-Z I do not see any resources maxed out.\Can anyone provide any insight that might help me understand why this is happening to me with my system?

Since it happens in both 2D and VR I put it in this part of the forum in hopes that more people will see it and perhaps have some guidance for me.

 

Thanks everyone. Looking forward to getting your responses.

4 hours ago, Hamish100 said:

2026-04-15 16:29:15.803 [INF] [ MainWindow:PromptForAmdFirstCcdC ] AMD First‑CCD mode enabled by user choice 
2026-04-15 17:04:33.829 [INF] [ ServiceModel:ApplyPerfOptAffinit ] Captured original affinity=0xFFFFFF 
2026-04-15 17:04:33.829 [INF] [ ServiceModel:ApplyPerfOptAffinit ] Universal physical‑cores‑only mask built. Mask=0x555555 
2026-04-15 17:04:33.829 [INF] [ ServiceModel:ApplyPerfOptAffinit ] AMD first‑CCD filter applied. Using 6 physical cores. Mask=0x555 
2026-04-15 17:04:33.830 [INF] [ ServiceModel:ApplyPerfOptAffinit ] Affinity applied to MSFS. 6 physical cores allocated 
2026-04-15 17:04:33.841 [INF] [ MemoryManager:GetOptSettings     ] CPU: AMD Ryzen 9 7900X3D 12-Core Processor           
2026-04-15 17:04:33.842 [INF] [ MemoryManager:LogCpuSummary      ] CPU Core Summary: Physical=12, Logical=24, SMT Cores=12, Single Cores=0 

These are the relevant lines and shows the app is applying the mask correctly to have MSFS use the 6 physical cores on the first CCD. As previously advised, using it results in stutters or poorer performance, simply uncheck Physical Cores on the MSFS Peformance Optimiser sub-control panel if you want to keep using the other options, or uncheck MSFS Peformance Optimiser to turn them all off. The tooltips will confirm the current state of each feature.

 

1 hour ago, Rob G said:

I started a separate thread for this but wanted to duplicate it here in case it might have something to do with AutoFPS.

 

OK, I guess I should start with some background. I have a 7800X3D CPU, RTX 4090 GPU, and 64GB of 6000hz memory. I am using AutoFPS with FPS Cap, FPS set to 35 in AutoFPS, Max Framerate in sim, and Dynamic Settings in sim.

All of my testing is with the Beachcraft Bonanza G36 Mod.

What I am experiencing, in both 2D and VR, is that certain functions, when invoked, cause a stutter, while during normal straight flight I do not have stuttering.

For instance, I take off just fine. Right after takeoff, I hit the control to put up the wheels. That causes a stutter. Then shortly after I hit the control to put up the flaps. That causes a stutter. Opening the toolbar and doing something from there causes a stutter.

Looking at GPU-Z I do not see any resources maxed out.\Can anyone provide any insight that might help me understand why this is happening to me with my system?

Since it happens in both 2D and VR I put it in this part of the forum in hopes that more people will see it and perhaps have some guidance for me.

 

Thanks everyone. Looking forward to getting your responses.

Try doing your flight without AutoFPS and if it still does it, it is not AutoFPS causing it. If it is, it could be from the MSFS Performance Optimiser if you have that enabled, although it should work fine with a 7800X3D as it does for my 9800X3D, so if so try turning that off. Unless AutoFPS happens to be significantly changing settings at the same time as when you activate those aircraft functions, then the only other explanation is that your LOD settings are too high. This could also occur if you weren't using AutoFPS and had them set similarly high in MSFS itself, so try not using AutoFPS and set your LODs to what AutoFPS would have set them to for that phase of flight. If it stutters the same, then LODs being too high are your issue.

If none of that helps, PM me the contents of your latest log file, located in %appdata%\MSFS_AutoFPS\log, where this happens and I will take a look. It would also be useful if you can tell me the exact timestamps where it is happening so I can see if there is any correlation with what AutoFPS was doing at the time.

37 minutes ago, Reset XPDR said:

Try doing your flight without AutoFPS and if it still does it, it is not AutoFPS causing it. If it is, it could be from the MSFS Performance Optimiser if you have that enabled, although it should work fine with a 7800X3D as it does for my 9800X3D, so if so try turning that off. Unless AutoFPS happens to be significantly changing settings at the same time as when you activate those aircraft functions, then the only other explanation is that your LOD settings are too high. This could also occur if you weren't using AutoFPS and had them set similarly high in MSFS itself, so try not using AutoFPS and set your LODs to what AutoFPS would have set them to for that phase of flight. If it stutters the same, then LODs being too high are your issue.

If none of that helps, PM me the contents of your latest log file, located in %appdata%\MSFS_AutoFPS\log, where this happens and I will take a look. It would also be useful if you can tell me the exact timestamps where it is happening so I can see if there is any correlation with what AutoFPS was doing at the time.

Sorry but what do you mean by the performance optimizer. Do you mean Dynamic Settings?

1 hour ago, Rob G said:

Sorry but what do you mean by the performance optimizer. Do you mean Dynamic Settings?

I mean the checkbox to the left of the blue text:

29 minutes ago, Reset XPDR said:

I mean the checkbox to the left of the blue text:

Ah ok. I have it checked but I only have the priority option checked. I will try some of your suggestions and report back. Thanks. Your level of support to all of us is nothing short of amazing.