7 hours ago, rjack1282 said:

https://github.com/ResetXPDR/MSFS_AutoFPS/releases

Scroll down to the version you want (latest release or test) and there is a dropdown menu called Assets after the release notes.  Drop that down and click on the .exe for the version you want.

@Noel, also on the app main page here it has a link on the right hand side to the latest version without having to go through the list of all release.

 

10 hours ago, Sonosusto said:

So fps cap in the sim at 30, FG brings it up further to 60....then set my monitor to..... 60? What abouy gsync?

I use a 30 limit in the sim (MSFS2024), then FG gives me 60, my monitor is 60hz (in 4k), and I have GSYNC off. I run AutoFPS in FPSCap mode set to 60. This works well for me. You can see my PC spec below.

14 hours ago, Harrier77 said:

I use a 30 limit in the sim (MSFS2024), then FG gives me 60, my monitor is 60hz (in 4k), and I have GSYNC off. I run AutoFPS in FPSCap mode set to 60. This works well for me. You can see my PC spec below.

Thank you. I spoke too soon and im having a lot of issues with random stutters. Microspikes with sound cut offs, like little blips. Random. Doesn't matter what app, dynamic, autofps, all off, fps cap, traffic.... happens randomly and ruins the experience. 

52 minutes ago, Sonosusto said:

Thank you. I spoke too soon and im having a lot of issues with random stutters. Microspikes with sound cut offs, like little blips. Random. Doesn't matter what app, dynamic, autofps, all off, fps cap, traffic.... happens randomly and ruins the experience. 

Everybody has them from time to time. Some core MS2024 issue. Saw a stream of BlackBox711 yesterday evening and he had them as well. Could even see the spikes in DevMode.

4 minutes ago, Farlis said:

Everybody has them from time to time. Some core MS2024 issue. Saw a stream of BlackBox711 yesterday evening and he had them as well. Could even see the spikes in DevMode.

Seems like something more prominent in SU3 as I never experienced these in SU2. Haha. Wonder when SU4 beta starts and hopefully this, and performance optimizing are one of the first fixes. 

At least autofps helps alleviate it at its worst moments. SU3 worked so well at first. 

I don't suffer micro-stutters myself, but I thought this is an interesting video and possible problem/solution:

I like his hardware videos - and he's a flight simmer.

Is there any way to get Autofps working with the in game dynamic settings on? I am noticing that autofps works far better below 1000 feet (on my 8gb vram system with full beyond atc traffic), and dynamic settings works far better above 1000 feet. I find that this combination is extremely smooth and stutter free, the only issue being that autofps disables dynamic settings from time to time.

 

Hello

I haven't been able to get the program to run since MSFS2024 SU3. I've reinstalled runtime 8.0. 
This only happens after I've loaded the flight and am at the gate. I've also tried the latest beta and executed everything 
listed, without success... 

Thanks for your help. 

Regards, Ramon
 

6 hours ago, agent00729 said:

Is there any way to get Autofps working with the in game dynamic settings on? I am noticing that autofps works far better below 1000 feet (on my 8gb vram system with full beyond atc traffic), and dynamic settings works far better above 1000 feet. I find that this combination is extremely smooth and stutter free, the only issue being that autofps disables dynamic settings from time to time.

Why do you consider that dynamic setting does a better job above 1000 ft, considering it only works with a range of 50-100% of your default LOD ranges whereas AutoFPS is much more configurable and in my experience provides a similar experience to dynamic LOD if you give it the same LOD limits it has at higher altitudes? ie. Why not just be more conservative with your AutoFPS settings above 1000 ft?

At this time AutoFPS disables dynamic settings the entire time you are in a flight session because it is generally not a good idea to have two things controlling one setting, especially when dynamic settings is not aware of what AutoFPS is trying to do. I could add a setting that switches between AutoFPS and dynamic settings control, but unless your LODs are exactly matching at the transition point the change could be rather abrupt, which might be fine on departure but not so much on arrival. 

While I could write code to do such an auto switch and smooth such a transition, that is quite a lot of effort involved for one use case that I am struggling to be convinced would actually be of benefit to you. As such, before I go any further, please provide more justification of its worth.

 

 

Edited September 5, 2025Sep 5 by Reset XPDR

3 hours ago, Metall4You said:

 

Hello

I haven't been able to get the program to run since MSFS2024 SU3. I've reinstalled runtime 8.0. 
This only happens after I've loaded the flight and am at the gate. I've also tried the latest beta and executed everything 
listed, without success... 

Thanks for your help. 

Regards, Ramon
 

It is hard to tell without seeing your log file so can you direct message me the contents of your latest log file, located in %appdat%\MSFS_AutoFPS\log, and I will take a look.

Hello

Thanks for your feedback. I'd be happy to send you the log files.

Thanks for your help. 

Regards, Ramon

 

2025-09-05 01:18:53.996 [INF] ----------------------------------------------------------------------- 
2025-09-05 01:18:54.016 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.5.5 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2025-09-05 01:18:54.019 [INF] [ ServiceController:Run            ] Service starting ... 
2025-09-05 01:18:56.047 [INF] [ MainWindow:cbTargetFPSType_Selec ] Default graphics mode is FSR3 
2025-09-05 01:18:56.048 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:FSR3 ATgtFPS:False FltType:IFR TgtFPS:58 TLODMethod:FPSCap Tol:5 LOS:False TMin:50 TMin+:true TBase-:True TMax:200 TMax+:False TMax-:False TLODBAlt:1000 TLODTAlt:5000 CustomOLOD:False RSet:False IncCld:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2025-09-05 01:18:56.643 [INF] [ MainWindow:cbUpdateOption_Select ] 1 
2025-09-05 01:18:57.051 [INF] [ IPCManager:WaitForSimulator      ] Simulator not started - waiting 10s between Retries 
2025-09-05 01:19:06.238 [INF] [ MainWindow:chkUseExpertOptions_C ] false 
2025-09-05 01:19:06.240 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:False Mode:FSR3 ATgtFPS:False FltType:IFR TgtFPS:58 TLODMethod:Sens Tol:5 LOS:False TMin:0 TMin+:true TMax:0 TMax+:False TMax-:True TLODBAlt:0 MaxDesRate 2000 CustomOLOD:True OLODB:0 OLODT:0 OLODBAlt:2000 OLODTAlt:10000 RSet:True IncCld:False RLvls:2 RFloor:1 RRecov:0 RSuite:3 VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2025-09-05 01:19:06.833 [INF] [ MainWindow:chkUseExpertOptions_C ] true 
2025-09-05 01:19:06.834 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:FSR3 ATgtFPS:False FltType:IFR TgtFPS:58 TLODMethod:FPSCap Tol:5 LOS:False TMin:50 TMin+:true TBase-:True TMax:200 TMax+:False TMax-:False TLODBAlt:1000 TLODTAlt:5000 CustomOLOD:False RSet:False IncCld:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2025-09-05 01:19:23.516 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
2025-09-05 01:25:16.535 [INF] ----------------------------------------------------------------------- 
2025-09-05 01:25:16.560 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.5.5 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2025-09-05 01:25:16.564 [INF] [ ServiceController:Run            ] Service starting ... 
2025-09-05 01:25:17.570 [INF] [ MainWindow:cbTargetFPSType_Selec ] Default graphics mode is FSR3 
2025-09-05 01:25:17.572 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:FSR3 ATgtFPS:False FltType:IFR TgtFPS:58 TLODMethod:FPSCap Tol:5 LOS:False TMin:50 TMin+:true TBase-:True TMax:200 TMax+:False TMax-:False TLODBAlt:1000 TLODTAlt:5000 CustomOLOD:False RSet:False IncCld:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2025-09-05 01:25:18.120 [INF] [ MainWindow:cbUpdateOption_Select ] 1 
2025-09-05 01:25:18.582 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2025-09-05 01:25:20.672 [INF] [ MemoryManager:MemoryManager      ] MSFS successfully attached after 1 attempt 
2025-09-05 01:25:20.672 [INF] [ MemoryManager:GetActiveDXVersion ] Steam MSFS2024 version 1.5.27.0 detected - DX12 
2025-09-05 01:25:20.683 [INF] [ MemoryManager:GetOptSettings     ] configGPUModel NVIDIA GeForce RTX 3090 
2025-09-05 01:25:20.683 [INF] [ MemoryManager:GetOptSettings     ] Successfully read required settings from UserOpt.cfg 
2025-09-05 01:25:20.683 [DBG] [ MemoryManager:MemoryManager      ] Primary compatibility test bypassed due to previous saved pass found for current MSFS/app/offset combo 
2025-09-05 01:25:20.683 [DBG] [ MemoryManager:MemoryManager      ] Secondary compatibility test bypassed due to previous saved pass found for current MSFS/app/offset combo 
2025-09-05 01:25:20.765 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2025-09-05 01:25:20.766 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 5s between Retries 
2025-09-05 01:26:25.635 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2025-09-05 01:26:25.848 [DBG] [ MobiSimConnect:SimConnect_Receiv ] Sending Ping to MobiFlight WASM Module 
2025-09-05 01:26:26.391 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2025-09-05 01:26:28.559 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2025-09-05 01:26:31.160 [INF] [ IPCManager:WaitForSessionReady   ] Session not ready - waiting 5s between Retries 
2025-09-05 01:28:35.991 [ERR] [ MemoryManager:MemoryManager      ] Unable to attach MSFS and/or determine version number after 15 attempts - memory writes disabled. 
2025-09-05 01:28:36.003 [INF] [ LODController:GetMSFSState       ] Graphics mode changed from FSR3 to NFR 
2025-09-05 01:28:36.328 [INF] [ LODController:gpuzRunning        ] GPU-Z companion app running 
2025-09-05 01:28:36.329 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Load sensor found 
2025-09-05 01:28:36.329 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Memory Used sensor found 
2025-09-05 01:28:36.329 [INF] [ LODController:gpuzRunning        ] GPU-Z Initial Memory Used: 17153 MB 
2025-09-05 01:28:36.358 [INF] [ LODController:gpuzRunning        ] System Reported Total GPU Memory: 24326 MB 
2025-09-05 01:28:36.358 [INF] [ LODController:gpuzRunning        ] GPU Initial Memory Usage: 70% 
2025-09-05 01:28:36.361 [INF] [ ServiceController:ServiceLoop    ] Starting Service Loop 
2025-09-05 01:28:36.361 [INF] [ ServiceController:ServiceLoop    ] Initial LODs PC 150 / 400 and VR 50 / 50 
2025-09-05 01:28:36.361 [INF] [ ServiceController:ServiceLoop    ] Initial Cloud Quality PC Ultra / VR Med 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Off Screen Terrain Pre-Caching PC Ultra / VR Low 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Terrain Shadows Enabled PC Enabled / VR Enabled 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Terrain Shadows PC 512 / VR 256 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Raytraced Shadows PC Disabled / VR Disabled 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Displacement Mapping PC Enabled / VR Disabled 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Buildings PC Ultra / VR Low 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Trees PC Ultra / VR Low 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Plants PC Ultra / VR Low 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Grass PC Ultra / VR Low 
2025-09-05 01:28:36.363 [INF] [ ServiceController:ServiceLoop    ] Initial Parked Aircraft Quantity PC Off / VR Off 
2025-09-05 01:28:36.364 [INF] [ ServiceController:ServiceLoop    ] Initial Aircraft Traffic Quantity PC Med / VR Off 
2025-09-05 01:28:36.364 [INF] [ ServiceController:ServiceLoop    ] Initial Dynamic Settings PC Disabled / VR Disabled 
2025-09-05 01:28:36.364 [INF] [ ServiceController:ServiceLoop    ] Dynamic Settings PC and VR temporarily disabled while MSFS_AutoFPS is controlling MSFS 2024 settings 
2025-09-05 01:28:37.376 [INF] [ ServiceModel:ResetCloudsTLOD     ] FPS source set to MSFS 
2025-09-05 01:28:37.378 [INF] [ ServiceModel:ResetCloudsTLOD     ] Full reset of LODs, clouds, graphics mode and Auto Target FPS states activated 
2025-09-05 01:28:37.379 [INF] [ ServiceController:ServiceLoop    ] Setting Initial LODs @ 8 ft AGL to 0 / 0 
2025-09-05 01:28:37.386 [INF] [ ServiceController:ResetAverageFP ] Average FPS reset to initial state 
2025-09-05 01:28:37.406 [INF] [ LODController:GetMSFSState       ] Graphics mode changed from NFR to FSR3 
2025-09-05 01:28:37.409 [INF] [ ServiceModel:ResetCloudsTLOD     ] FPS source set to MSFS 
2025-09-05 01:28:37.413 [INF] [ ServiceModel:ResetCloudsTLOD     ] Full reset of LODs, clouds, graphics mode and Auto Target FPS states activated 
2025-09-05 01:28:38.430 [INF] [ ServiceController:ResetAverageFP ] Average FPS reset to initial state 
2025-09-05 01:28:38.432 [INF] [ LODController:UpdateVariables    ] FPS:32 Pri:FPSCap TLOD:0 TLODRng:50-200 OLOD:0 AGL:8 FPM:-0 GPU:40% VRAM:70% 
2025-09-05 01:28:57.654 [INF] [ ServiceController:ServiceLoop    ] ServiceLoop ended 
2025-09-05 01:28:57.658 [INF] [ ServiceController:ServiceLoop    ] Resetting LODs to PC 150 / 400 and VR 50 / 50 
2025-09-05 01:28:57.659 [INF] [ ServiceController:ServiceLoop    ] Resetting Cloud Quality to PC Ultra / VR Med 
2025-09-05 01:28:57.659 [INF] [ ServiceController:ServiceLoop    ] Resetting Dynamic Settings to PC False / VR False 
2025-09-05 01:28:57.659 [INF] [ ServiceController:ServiceLoop    ] Resetting Reduction Settings to saved MSFS settings 
2025-09-05 01:28:57.661 [INF] [ MemoryManager:RestoreUserCfgOptS ] Reverting UserCfg.opt individual settings modified during this session to original 
2025-09-05 01:28:57.693 [DBG] [ MemoryManager:RestoreUserCfgOptS ] UserCfg.opt backup file refreshed with individual changes successfully 
2025-09-05 01:28:57.711 [DBG] [ MemoryManager:RestoreUserCfgOptF ] Restored UserCfg.opt file exact match of back up. Deleting back up file... 
2025-09-05 01:28:57.711 [FTL] [ ServiceController:Run            ] MSFS compatibility test failed - app disabled. 
2025-09-05 01:28:57.732 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
2025-09-05 18:53:13.620 [INF] ----------------------------------------------------------------------- 
2025-09-05 18:53:13.643 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.5.5 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2025-09-05 18:53:13.663 [INF] [ ServiceController:Run            ] Service starting ... 
2025-09-05 18:53:14.518 [INF] [ MainWindow:cbTargetFPSType_Selec ] Default graphics mode is FSR3 
2025-09-05 18:53:14.519 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:FSR3 ATgtFPS:False FltType:IFR TgtFPS:58 TLODMethod:FPSCap Tol:5 LOS:False TMin:50 TMin+:true TBase-:True TMax:200 TMax+:False TMax-:False TLODBAlt:1000 TLODTAlt:5000 CustomOLOD:False RSet:False IncCld:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2025-09-05 18:53:14.948 [INF] [ MainWindow:cbUpdateOption_Select ] 1 
2025-09-05 18:53:15.680 [INF] [ IPCManager:WaitForSimulator      ] Simulator not started - waiting 10s between Retries 
2025-09-05 18:53:26.605 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
2025-09-05 18:56:38.284 [INF] ----------------------------------------------------------------------- 
2025-09-05 18:56:38.316 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.5.5 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2025-09-05 18:56:38.322 [INF] [ ServiceController:Run            ] Service starting ... 
2025-09-05 18:56:39.321 [INF] [ MainWindow:cbTargetFPSType_Selec ] Default graphics mode is FSR3 
2025-09-05 18:56:39.323 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:FSR3 ATgtFPS:False FltType:IFR TgtFPS:58 TLODMethod:FPSCap Tol:5 LOS:False TMin:50 TMin+:true TBase-:True TMax:200 TMax+:False TMax-:False TLODBAlt:1000 TLODTAlt:5000 CustomOLOD:False RSet:False IncCld:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2025-09-05 18:56:39.699 [INF] [ MainWindow:cbUpdateOption_Select ] 1 
2025-09-05 18:56:40.350 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2025-09-05 18:56:42.433 [INF] [ MemoryManager:MemoryManager      ] MSFS successfully attached after 1 attempt 
2025-09-05 18:56:42.433 [INF] [ MemoryManager:GetActiveDXVersion ] Steam MSFS2024 version 1.5.27.0 detected - DX12 
2025-09-05 18:56:42.442 [INF] [ MemoryManager:GetOptSettings     ] configGPUModel NVIDIA GeForce RTX 3090 
2025-09-05 18:56:42.442 [INF] [ MemoryManager:GetOptSettings     ] Successfully read required settings from UserOpt.cfg 
2025-09-05 18:56:42.442 [DBG] [ MemoryManager:MemoryManager      ] Primary compatibility test bypassed due to previous saved pass found for current MSFS/app/offset combo 
2025-09-05 18:56:42.442 [DBG] [ MemoryManager:MemoryManager      ] Secondary compatibility test bypassed due to previous saved pass found for current MSFS/app/offset combo 
2025-09-05 18:56:42.521 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2025-09-05 18:56:42.521 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 5s between Retries 
2025-09-05 18:57:47.796 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2025-09-05 18:57:53.129 [DBG] [ MobiSimConnect:SimConnect_Receiv ] Sending Ping to MobiFlight WASM Module 
2025-09-05 18:57:53.239 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2025-09-05 18:57:53.346 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2025-09-05 18:57:57.950 [INF] [ IPCManager:WaitForSessionReady   ] Session not ready - waiting 5s between Retries 
2025-09-05 18:59:42.761 [ERR] [ MemoryManager:MemoryManager      ] Unable to attach MSFS and/or determine version number after 15 attempts - memory writes disabled. 
2025-09-05 18:59:42.767 [INF] [ LODController:GetMSFSState       ] Graphics mode changed from FSR3 to NFR 
2025-09-05 18:59:43.117 [INF] [ LODController:gpuzRunning        ] GPU-Z companion app running 
2025-09-05 18:59:43.117 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Load sensor found 
2025-09-05 18:59:43.117 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Memory Used sensor found 
2025-09-05 18:59:43.118 [INF] [ LODController:gpuzRunning        ] GPU-Z Initial Memory Used: 17198 MB 
2025-09-05 18:59:43.153 [INF] [ LODController:gpuzRunning        ] System Reported Total GPU Memory: 24326 MB 
2025-09-05 18:59:43.153 [INF] [ LODController:gpuzRunning        ] GPU Initial Memory Usage: 70% 
2025-09-05 18:59:43.155 [INF] [ ServiceController:ServiceLoop    ] Starting Service Loop 
2025-09-05 18:59:43.155 [INF] [ ServiceController:ServiceLoop    ] Initial LODs PC 150 / 400 and VR 50 / 50 
2025-09-05 18:59:43.155 [INF] [ ServiceController:ServiceLoop    ] Initial Cloud Quality PC Ultra / VR Med 
2025-09-05 18:59:43.156 [INF] [ ServiceController:ServiceLoop    ] Initial Off Screen Terrain Pre-Caching PC Ultra / VR Low 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Terrain Shadows Enabled PC Enabled / VR Enabled 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Terrain Shadows PC 512 / VR 256 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Raytraced Shadows PC Disabled / VR Disabled 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Displacement Mapping PC Enabled / VR Disabled 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Buildings PC Ultra / VR Low 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Trees PC Ultra / VR Low 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Plants PC Ultra / VR Low 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Grass PC Ultra / VR Low 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Parked Aircraft Quantity PC Off / VR Off 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Aircraft Traffic Quantity PC Med / VR Off 
2025-09-05 18:59:43.157 [INF] [ ServiceController:ServiceLoop    ] Initial Dynamic Settings PC Disabled / VR Disabled 
2025-09-05 18:59:43.158 [INF] [ ServiceController:ServiceLoop    ] Dynamic Settings PC and VR temporarily disabled while MSFS_AutoFPS is controlling MSFS 2024 settings 
2025-09-05 18:59:44.165 [INF] [ ServiceModel:ResetCloudsTLOD     ] FPS source set to MSFS 
2025-09-05 18:59:44.168 [INF] [ ServiceModel:ResetCloudsTLOD     ] Full reset of LODs, clouds, graphics mode and Auto Target FPS states activated 
2025-09-05 18:59:44.169 [INF] [ ServiceController:ServiceLoop    ] Setting Initial LODs @ 8 ft AGL to 0 / 0 
2025-09-05 18:59:44.180 [INF] [ ServiceController:ResetAverageFP ] Average FPS reset to initial state 
2025-09-05 18:59:44.206 [INF] [ LODController:GetMSFSState       ] Graphics mode changed from NFR to FSR3 
2025-09-05 18:59:44.210 [INF] [ ServiceModel:ResetCloudsTLOD     ] FPS source set to MSFS 
2025-09-05 18:59:44.214 [INF] [ ServiceModel:ResetCloudsTLOD     ] Full reset of LODs, clouds, graphics mode and Auto Target FPS states activated 
2025-09-05 18:59:45.238 [INF] [ ServiceController:ResetAverageFP ] Average FPS reset to initial state 
2025-09-05 18:59:45.241 [INF] [ LODController:UpdateVariables    ] FPS:30 Pri:FPSCap TLOD:0 TLODRng:50-200 OLOD:0 AGL:8 FPM:0 GPU:40% VRAM:71% 
2025-09-05 19:00:45.092 [DBG] [ LODController:GetDetectedFPSCap  ] FPS cap detected at 28 FPS 
2025-09-05 19:01:45.889 [INF] [ ServiceController:ServiceLoop    ] ServiceLoop ended 
2025-09-05 19:01:45.893 [INF] [ ServiceController:ServiceLoop    ] Resetting LODs to PC 150 / 400 and VR 50 / 50 
2025-09-05 19:01:45.894 [INF] [ ServiceController:ServiceLoop    ] Resetting Cloud Quality to PC Ultra / VR Med 
2025-09-05 19:01:45.894 [INF] [ ServiceController:ServiceLoop    ] Resetting Dynamic Settings to PC False / VR False 
2025-09-05 19:01:45.894 [INF] [ ServiceController:ServiceLoop    ] Resetting Reduction Settings to saved MSFS settings 
2025-09-05 19:01:45.896 [INF] [ MemoryManager:RestoreUserCfgOptS ] Reverting UserCfg.opt individual settings modified during this session to original 
2025-09-05 19:01:45.909 [DBG] [ MemoryManager:RestoreUserCfgOptS ] UserCfg.opt backup file refreshed with individual changes successfully 
2025-09-05 19:01:45.945 [DBG] [ MemoryManager:RestoreUserCfgOptF ] Restored UserCfg.opt file exact match of back up. Deleting back up file... 
2025-09-05 19:01:45.945 [FTL] [ ServiceController:Run            ] MSFS compatibility test failed - app disabled. 
2025-09-05 19:01:46.059 [INF] [ MobiSimConnect:Disconnect        ] SimConnect Connection closed 
2025-09-05 19:01:46.399 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 

3 hours ago, Reset XPDR said:

Why do you consider that dynamic setting does a better job above 1000 ft, considering it only works with a range of 50-100% of your default LOD ranges whereas AutoFPS is much more configurable and in my experience provides a similar experience to dynamic LOD if you give it the same LOD limits it has at higher altitudes? ie. Why not just be more conservative with your AutoFPS settings above 1000 ft?

At this time AutoFPS disables dynamic settings the entire time you are in a flight session because it is generally not a good idea to have two things controlling one setting, especially when dynamic settings is not aware of what AutoFPS is trying to do. I could add a setting that switches between AutoFPS and dynamic settings control, but unless your LODs are exactly matching at the transition point the change could be rather abrupt, which might be fine on departure but not so much on arrival. 

While I could write code to do such an auto switch and smooth such a transition, that is quite a lot of effort involved for one use case that I am struggling to be convinced would actually be of benefit to you. As such, before I go any further, please provide more justification of its worth.

 

 

I think for lower/middle end hardware like mine, the dynamic settings are more aggressive and “dynamic” than autofps in regard to adjusting graphics settings that are not TLOD and OLOD. In contrast, autofps is more aggressive with LODs. I feel like a combination of setting the Autofps and dynamic settings is the sweet spot for hardware like mine that can’t even do half of max TLOD at ground level. I think perhaps dynamic settings is also doing more than adjusting graphics presets (like autofps is only able to do), but I am not sure. For example, when flying from Rome to LAX with only autofps on, I got severe sound and fps stuttering with horrible image quality at altitude over Los Angeles, making it unplayable. Then, on final approach, as the LOD settles to the 1000 foot setting as per autofps, it became smooth again. This was with dynamic settings off. TLOD under 1000 set to 50, TLOD above set to 150.
 

Then, I discovered dynamic settings might do something similar to autofps, so I gave it a try on SFO-BUR. This time, I increased TLOD to 200 in MSFS2024 settings. Everything at altitude was extremely smooth, and even visually, it looked far better than autofps. Even flying into the LA area it was buttery smooth. Then, as I got lower to the ground on approach (~2000 feet) it became unplayable. Even on the ground in BUR it was unplayable. So for my next flight,  I decided to combine autofps for the ground, and dynamic settings for the air (above 1000).  I’ve been flying that way ever since. On the return from BUR-SFO I enabled autofps, then reenabled dynamic settings. Everything was buttery smooth again. Although I noticed that dynamic settings gets switched off whenever autofps decreases settings apart from LODs, but not necessarily when adjusting LODs at various altitudes. So I may need to test and see if it still switches off when I turn off autofps ability to do that, and just let autofps focus on LODs.

sorry if this is a convoluted post. In summary, dynamic settings seems more optimized and dynamic than autofps when it comes to graphics settings that are not LODs. Autofps has a better range for handling LODs, in contrast. So the combination of the two works for me. 
 

I also find that even on the ground, with both dynamic settings and autofps on, autofps actually increases the min LOD much more frequently. It’s almost always at 100 now, according to autofps settings. I’m not sure if this is because dynamic settings is doing something else under the hood to make it smoother, and so autofps compensates by adding more LOD. This never happened before as frequently and at busy airports.

i also thought that perhaps dynamic settings is just taking the autofps setting and dividing it by 2, which is why i seem to have such good performance. But, in the autofps app, the TLOD is showing 200 in the air, and 100 (50 added to 50) on the ground. So I’m not sure what is going on exactly but it is working very well.

Perhaps there is a way for them to work together, not necessarily by having autofps and dynamic settings alternate between who is controlling, as you referenced, but to have autofps control the base setting of LODs at all times, spit that out to MSFS, and then dynamic settings can react to that base. Sort of like how anyone can just go into MSFS settings and manually adjust graphics settings at all times, even with dynamic settings on. Only, autofps can automate that. Perhaps this is what is already happening now in my tests? 

Edited September 6, 2025Sep 6 by agent00729

1 hour ago, agent00729 said:

I think for lower/middle end hardware like mine, the dynamic settings are more aggressive and “dynamic” than autofps in regard to adjusting graphics settings that are not TLOD and OLOD. In contrast, autofps is more aggressive with LODs. I feel like a combination of setting the Autofps and dynamic settings is the sweet spot for hardware like mine that can’t even do half of max TLOD at ground level. I think perhaps dynamic settings is also doing more than adjusting graphics presets (like autofps is only able to do), but I am not sure. For example, when flying from Rome to LAX with only autofps on, I got severe sound and fps stuttering with horrible image quality at altitude over Los Angeles, making it unplayable. Then, on final approach, as the LOD settles to the 1000 foot setting as per autofps, it became smooth again. This was with dynamic settings off. TLOD under 1000 set to 50, TLOD above set to 150.
 

Then, I discovered dynamic settings might do something similar to autofps, so I gave it a try on SFO-BUR. This time, I increased TLOD to 200 in MSFS2024 settings. Everything at altitude was extremely smooth, and even visually, it looked far better than autofps. Even flying into the LA area it was buttery smooth. Then, as I got lower to the ground on approach (~2000 feet) it became unplayable. Even on the ground in BUR it was unplayable. So for my next flight,  I decided to combine autofps for the ground, and dynamic settings for the air (above 1000).  I’ve been flying that way ever since. On the return from BUR-SFO I enabled autofps, then reenabled dynamic settings. Everything was buttery smooth again. Although I noticed that dynamic settings gets switched off whenever autofps decreases settings apart from LODs, but not necessarily when adjusting LODs at various altitudes. So I may need to test and see if it still switches off when I turn off autofps ability to do that, and just let autofps focus on LODs.

sorry if this is a convoluted post. In summary, dynamic settings seems more optimized and dynamic than autofps when it comes to graphics settings that are not LODs. Autofps has a better range for handling LODs, in contrast. So the combination of the two works for me. 
 

I also find that even on the ground, with both dynamic settings and autofps on, autofps actually increases the min LOD much more frequently. It’s almost always at 100 now, according to autofps settings. I’m not sure if this is because dynamic settings is doing something else under the hood to make it smoother, and so autofps compensates by adding more LOD. This never happened before as frequently and at busy airports.

i also thought that perhaps dynamic settings is just taking the autofps setting and dividing it by 2, which is why i seem to have such good performance. But, in the autofps app, the TLOD is showing 200 in the air, and 100 (50 added to 50) on the ground. So I’m not sure what is going on exactly but it is working very well.

Perhaps there is a way for them to work together, not necessarily by having autofps and dynamic settings alternate between who is controlling, as you referenced, but to have autofps control the base setting of LODs at all times, spit that out to MSFS, and then dynamic settings can react to that base. Sort of like how anyone can just go into MSFS settings and manually adjust graphics settings at all times, even with dynamic settings on. Only, autofps can automate that. Perhaps this is what is already happening now in my tests? 

Thanks for the detailed explanation. Your suggestion that AutoFPS could control the base setting of LODs has merit, however it would mean that dynamic settings would have to be working off the changes that AutoFPS has made and not its own recollection of base TLOD and OLOD settings. Also, doing so would mean that AutoFPS settings reduction for LODs would have to be disabled, which would add another layer of complication to any solution.

One thing I need to clarify is whether when you say you are trying dynamic settings, you are still running AutoFPS or not? If you are then this is not something I have tested, as AutoFPS is expecting dynamic settings to be disabled for the duration that AutoFPS has control of the settings.

1 hour ago, Reset XPDR said:

Thanks for the detailed explanation. Your suggestion that AutoFPS could control the base setting of LODs has merit, however it would mean that dynamic settings would have to be working off the changes that AutoFPS has made and not its own recollection of base TLOD and OLOD settings. Also, doing so would mean that AutoFPS settings reduction for LODs would have to be disabled, which would add another layer of complication to any solution.

One thing I need to clarify is whether when you say you are trying dynamic settings, you are still running AutoFPS or not? If you are then this is not something I have tested, as AutoFPS is expecting dynamic settings to be disabled for the duration that AutoFPS has control of the settings.

Thank you. Yes, I am running autofps and dynamic settings simultaneously, as this is how I see the best performance.  I will test tonight and see if autofps, with auto reduce settings unchecked, will still disable dynamic settings after I have reenabled dynamic settings. 

22 minutes ago, agent00729 said:

Thank you. Yes, I am running autofps and dynamic settings simultaneously, as this is how I see the best performance.  I will test tonight and see if autofps, with auto reduce settings unchecked, will still disable dynamic settings after I have reenabled dynamic settings. 

For you to be achieving that you would have to be going into MSFS settings after you start a flight session and re-enabling dynamic settings because the first thing AutoFPS does is disable dynamic settings when a flight session starts, which it then restores to whatever you had it set to before you started your flight. Is this what you are doing?