Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

MSFS Auto FPS App

Featured Replies

  • Author
3 hours ago, Skenson said:

Unable to install the latest version really frustrating.

 

Did you try all the relevant suggestions in the readme to resolve it?

9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit

MSFS @ 4K Ultra DLSS Performance FG 80 FPS |  VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11

Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11

  • Replies 4.3k
  • Views 701.2k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Developing this app has reignited a joy of coding I haven't experienced for many years. I benefit from the app too, so there is a bit of self interest going on. Also, yours, and others, feedback has h

  • Reset XPDR
    Reset XPDR

    Following no major issues being identified in the test phase that haven't already been resolved, I have just formally released MSFS_AutoFPS v0.4.2.16 here. Thank you to everyone who participated in th

  • Ray Proudfoot
    Ray Proudfoot

    Are you aware this is how FSUIPC was created many years ago? It takes a very clever person to disassemble a executable and analyse the contents. The original UIPC was created by Adam Zofran and then P

Posted Images

Since today autofps doesn't start anymore; I don't know why. I'm on beta 5 FS2024. What informations do you (or me) need for looking for errors? The log-file from today contains this; I tried installing an older version inbetween but it doesn't help.:

 

 

2026-03-20 15:05:47.295 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:05:47.326 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:05:47.353 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:05:47.356 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:05:47.586 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:05:47.586 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:07:44.686 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:07:44.706 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:07:44.733 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:07:44.736 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:07:44.946 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:07:44.946 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:08:02.965 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:08:02.983 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:08:03.008 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:08:03.011 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:08:03.216 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:08:03.217 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:12:56.836 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:12:56.854 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:12:56.876 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:12:56.879 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:12:57.063 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:12:57.064 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:14:06.136 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:14:06.161 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:14:06.183 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:14:06.186 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:14:06.380 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:14:06.380 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:15:18.641 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:15:18.658 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:15:18.682 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:15:18.684 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:15:18.869 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:15:18.870 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:15:25.349 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:15:25.366 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:15:25.389 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:15:25.392 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:15:25.579 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:15:25.579 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:21:00.730 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:21:00.748 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.6 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:21:00.770 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:21:00.773 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:21:00.956 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:21:00.956 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:21:00.963 [INF] [ MainWindow:cbTargetFPSType_Selec ] Default graphics mode is FG 
2026-03-20 15:21:00.964 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:False Mode:FG ATgtFPS:True FltType:IFR TgtFPS:60 TLODMethod:Sens Tol:5 LOS-C:False TMin:50 TBXtra:false TMax:200 TMtns:False TNightDiv2:True TLODBAlt:0 TLODTAlt:0 CustomOLOD:True OLODB:0 OLODT:0 OLODBAlt:2000 OLODTAlt:10000 RSet:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2026-03-20 15:21:01.491 [INF] [ MainWindow:DownloadLatestRelease ] Downloaded fresh release data to check for updates. 
2026-03-20 15:21:01.519 [INF] [ MainWindow:CheckForUpdates       ] Latest test version available: 0.4.6.7-test3. Update option: Silent Updates + Test Versions 
2026-03-20 15:21:01.642 [INF] [ MainWindow:AutoUpdate            ] New app version available for auto update. 
2026-03-20 15:21:01.643 [INF] [ MainWindow:AutoUpdate            ] User silently agreed to auto update app to 0.4.6.7-test3. 
2026-03-20 15:21:01.674 [INF] [ MainWindow:AutoUpdate            ] Auto update in progress. 
2026-03-20 15:21:01.685 [INF] [ ServiceModel:RestorePriority     ] Priority restore skipped — no priority change was applied. 
2026-03-20 15:21:01.685 [INF] [ ServiceModel:RestoreAffinity     ] Affinity restore skipped — no affinity change was applied. 
2026-03-20 15:21:01.685 [INF] [ ServiceModel:RestoreOriginalPowe ] No power plan change to restore. 
2026-03-20 15:21:01.685 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
2026-03-20 15:21:06.092 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:21:06.111 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:21:06.141 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:21:06.143 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:21:06.342 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:21:06.342 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:21:21.564 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:21:21.581 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:21:21.603 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:21:21.605 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:21:21.790 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:21:21.790 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:21:41.462 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:21:41.480 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:21:41.503 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:21:41.506 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:21:41.695 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:21:41.695 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:43:58.306 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:43:58.328 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:43:58.372 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:43:58.375 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:43:58.654 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:43:58.654 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:51:58.855 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:51:58.877 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:51:58.906 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:51:58.910 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:51:59.149 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:51:59.149 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 16:08:54.645 [INF] ----------------------------------------------------------------------- 
2026-03-20 16:08:54.669 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 16:08:54.701 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 16:08:54.705 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 16:08:54.962 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 16:08:54.962 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 

 

mfg Kai
 

Mainboard: Gigabyte Z690 UD DDR4, CPU: I7 12700K , Grafikkarte RTX 4080, Monitor: LG ULTRAWIDE(38UC99) 3840*1600, 64 GB RAM DDR4 3200 GSkill, Windows 11 pro, MSFS

  • Author
6 hours ago, Kai-Uwe Wei said:

Since today autofps doesn't start anymore; I don't know why. I'm on beta 5 FS2024. What informations do you (or me) need for looking for errors? The log-file from today contains this; I tried installing an older version inbetween but it doesn't help.:

 

 

2026-03-20 15:05:47.295 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:05:47.326 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:05:47.353 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:05:47.356 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:05:47.586 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:05:47.586 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:07:44.686 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:07:44.706 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:07:44.733 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:07:44.736 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:07:44.946 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:07:44.946 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:08:02.965 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:08:02.983 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:08:03.008 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:08:03.011 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:08:03.216 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:08:03.217 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:12:56.836 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:12:56.854 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:12:56.876 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:12:56.879 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:12:57.063 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:12:57.064 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:14:06.136 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:14:06.161 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:14:06.183 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:14:06.186 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:14:06.380 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:14:06.380 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:15:18.641 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:15:18.658 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:15:18.682 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:15:18.684 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:15:18.869 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:15:18.870 [INF] [ MainWindow:MainWindow            ] Initial window position set to (103,110) 
2026-03-20 15:15:25.349 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:15:25.366 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:15:25.389 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:15:25.392 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:15:25.579 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:15:25.579 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:21:00.730 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:21:00.748 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.6 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:21:00.770 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:21:00.773 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:21:00.956 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:21:00.956 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:21:00.963 [INF] [ MainWindow:cbTargetFPSType_Selec ] Default graphics mode is FG 
2026-03-20 15:21:00.964 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:False Mode:FG ATgtFPS:True FltType:IFR TgtFPS:60 TLODMethod:Sens Tol:5 LOS-C:False TMin:50 TBXtra:false TMax:200 TMtns:False TNightDiv2:True TLODBAlt:0 TLODTAlt:0 CustomOLOD:True OLODB:0 OLODT:0 OLODBAlt:2000 OLODTAlt:10000 RSet:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2026-03-20 15:21:01.491 [INF] [ MainWindow:DownloadLatestRelease ] Downloaded fresh release data to check for updates. 
2026-03-20 15:21:01.519 [INF] [ MainWindow:CheckForUpdates       ] Latest test version available: 0.4.6.7-test3. Update option: Silent Updates + Test Versions 
2026-03-20 15:21:01.642 [INF] [ MainWindow:AutoUpdate            ] New app version available for auto update. 
2026-03-20 15:21:01.643 [INF] [ MainWindow:AutoUpdate            ] User silently agreed to auto update app to 0.4.6.7-test3. 
2026-03-20 15:21:01.674 [INF] [ MainWindow:AutoUpdate            ] Auto update in progress. 
2026-03-20 15:21:01.685 [INF] [ ServiceModel:RestorePriority     ] Priority restore skipped — no priority change was applied. 
2026-03-20 15:21:01.685 [INF] [ ServiceModel:RestoreAffinity     ] Affinity restore skipped — no affinity change was applied. 
2026-03-20 15:21:01.685 [INF] [ ServiceModel:RestoreOriginalPowe ] No power plan change to restore. 
2026-03-20 15:21:01.685 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
2026-03-20 15:21:06.092 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:21:06.111 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:21:06.141 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:21:06.143 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:21:06.342 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:21:06.342 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:21:21.564 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:21:21.581 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:21:21.603 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:21:21.605 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:21:21.790 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:21:21.790 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:21:41.462 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:21:41.480 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:21:41.503 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:21:41.506 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:21:41.695 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:21:41.695 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:43:58.306 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:43:58.328 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:43:58.372 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:43:58.375 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:43:58.654 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:43:58.654 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 15:51:58.855 [INF] ----------------------------------------------------------------------- 
2026-03-20 15:51:58.877 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 15:51:58.906 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 15:51:58.910 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 15:51:59.149 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 15:51:59.149 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 
2026-03-20 16:08:54.645 [INF] ----------------------------------------------------------------------- 
2026-03-20 16:08:54.669 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.7-test3 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-03-20 16:08:54.701 [INF] [ App:OnStartup                    ] Test Mode active 
2026-03-20 16:08:54.705 [INF] [ ServiceController:Run            ] Service starting ... 
2026-03-20 16:08:54.962 [INF] [ MainWindow:MainWindow            ] Virtual screen coordinates: (0,0) (3840,1600) 
2026-03-20 16:08:54.962 [INF] [ MainWindow:MainWindow            ] Initial window position set to (50,50) 

 

mfg Kai
 

Both versions of the app you tried should be compatible with the latest SU5 Beta. Is this the first time you have tried the app with SU5? What was the last working configuration of app and MSFS you had? Any major changes on your system before you experienced this today?

Try reinstalling the app again and select the Repair option, then try again.

Are you manually quitting the app or is it CTDing by itself? If the latter, does Windows Event Viewer show any app crash details? To check, open Event Viewer, on the tree on the left expand out to Even Viewer (Local) -> Windows Logs ->Application, under actions on the right click Find and search for "AutoFPS" and paste the details of any errors that occur into a PM and send that to me.

Edited by Reset XPDR

9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit

MSFS @ 4K Ultra DLSS Performance FG 80 FPS |  VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11

Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11

Congratulations on winning the Best Freeware Tool or Utility at the FS Awards 2026 FS Weekend, which is really well deserved. Thank you.

CPU: AMD Ryzen 7 9800X3D | GPU: NVIDIA GeForce RTX 4080 Super | MoBo:  ASUS Prime X670-P WIFI | OS: Windows 11 Home 64bit| RAM: 64GB 6000 MHz DDR5 | HD: 2TB Samsung 990 PRO M.2 PCIe SSD, 1TB Samsung 990 PRO M.2 PCIe SSD | MSFS 2024

  • Author
21 minutes ago, Harrier77 said:

Congratulations on winning the Best Freeware Tool or Utility at the FS Awards 2026 FS Weekend, which is really well deserved. Thank you.

Thanks so much. I’m just glad the tool is helping people enjoy the sim more.

9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit

MSFS @ 4K Ultra DLSS Performance FG 80 FPS |  VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11

Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11

hi, thanks for the app, works nicely, can anyone advise if its possible to configure it to start a session with your preferred top TLOD, and to only decrease TLOD if below target FPS? atm i've configured in FPS sensitivity, base min 42@1000, extra x4, top max 168@2000 which works nicely apart from the first 30sec during FPS settle will always have the min TLOD, so for things like landing challenges the terrain looks bad to start with.

7800x3d, 4070ti, 32GB, Quest 3 (virtual desktop)

I am starting to learn to fly helicopters. Can I get some suggestions as to the best way(s) to configure AutoFPS for helicopter flying? I will be flying simple ones initially like the Cabri G2.

Thanks.

Case: (Lian Li PC-011 Dynamic XL), PSU: (MEG Ai300p pcie 5 & ATX 3.0), Motherboard: (ASUS TUF Gaming x670E-PLUS WIFI 6E), CPU: (AMD Ryzen 7 7800-X3D) 

Memory: (G.Skill Trident Z5 NEO RGB Series 64GB DDR5 6000), GPU: (Zotac Gaming GeForce RTX 4090 AMP Extreme Airo). CPU Cooler: (ASUS ROG Strix LC RGB 360) 

Fans: (7 Corsair LL Series 120mm RGB)

  • Author
11 hours ago, cjk28 said:

hi, thanks for the app, works nicely, can anyone advise if its possible to configure it to start a session with your preferred top TLOD, and to only decrease TLOD if below target FPS? atm i've configured in FPS sensitivity, base min 42@1000, extra x4, top max 168@2000 which works nicely apart from the first 30sec during FPS settle will always have the min TLOD, so for things like landing challenges the terrain looks bad to start with.

The app's automation is designed primarily for flight starts from the ground or, if in the air, from a reasonable way out to give time for the automation to settle. Landing challenges are not really suited to this so you have the choice of either not using the app when doing such landing challenges or set up an Auto TLOD flight profile with 42@1000 and top max 168@2000 which will instantly give you the correct TLOD for a given altitude as there is no seek or settle in this mode*.

 

Untitled.png

 

* After trying this out myself, I realise that there are still some settle events for Auto TLOD in 0.4.6.6 that really should not be there so I will fix in 0.4.6.7-test so that you never see any of them.

Edit: 0.4.6.7-test12, or later, available here, has had all FPS settle events removed from Auto TLOD mode, as they are irrelevant in this specific mode.

Edited by Reset XPDR

9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit

MSFS @ 4K Ultra DLSS Performance FG 80 FPS |  VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11

Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11

  • Author
1 hour ago, Rob G said:

I am starting to learn to fly helicopters. Can I get some suggestions as to the best way(s) to configure AutoFPS for helicopter flying? I will be flying simple ones initially like the Cabri G2.

Thanks.

It should really be no different than with normal aircraft because the app automates based on AGL, so it shouldn't matter whether you come in on a glide path like a normal aircraft or descend vertically in a helicopter. I use the same settings for both types with no noticable issues.

9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit

MSFS @ 4K Ultra DLSS Performance FG 80 FPS |  VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11

Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11

18 hours ago, Reset XPDR said:

 

Ah thanks I wasn't aware of the test versions.


I guess i was hoping to either:

be able to override the initial settle time to something shorter

or have an alternate mode not considering altitude, where you start at your preferred max TLOD and only decrease towards the min TLOD based on delta from target FPS, that feels like a more catch all approach that accounts for variance in system demand caused by different environments, planes etc.

7800x3d, 4070ti, 32GB, Quest 3 (virtual desktop)

  • Author
4 hours ago, cjk28 said:

be able to override the initial settle time to something shorter

The initial 30 second settle timer is there to not only give MSFS time to stabilise after loading in but also for AutoFPS to intiialise its own smoothing parameters. It can go as low as 10 seconds, which is what I force it to when developing as MSFS is usually in a flight session all the time while I am doing so, but for normal MSFS use I have found this is not long enough and causes sub-optimal TLOD, and possibly even premature settings reductions, on the ground. I don't think even allowing users to adjust it down to 10 seconds will be low enough for what you want to achieve.

 

5 hours ago, cjk28 said:

or have an alternate mode not considering altitude, where you start at your preferred max TLOD and only decrease towards the min TLOD based on delta from target FPS, that feels like a more catch all approach that accounts for variance in system demand caused by different environments, planes etc.

I have not implemented this before because it could easily result in FPS remaining way below target at the start of a flight on the ground, which is where most users commence flights from, at a complex airport until TLOD dropped low enough to achieve it, which would make for unhappy users. Also, MSFS already has something similar to this with Dynamic Settings where it will give you your set LODs unless FPS is below target, in which case it will reduce them up to 50% and pretty much instantly, so there is really no need for AutoFPS to duplicate this. If you haven't tried Dynamic Settings yet for this particular scenario, I suggest you do so.

 

9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit

MSFS @ 4K Ultra DLSS Performance FG 80 FPS |  VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11

Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11

On 3/20/2026 at 9:49 PM, Reset XPDR said:

Try reinstalling the app again and select the Repair option, then try again.

Sorry for my late replying. Reinstalling and repaIring solved the problem.

 

Mainboard: Gigabyte Z690 UD DDR4, CPU: I7 12700K , Grafikkarte RTX 4080, Monitor: LG ULTRAWIDE(38UC99) 3840*1600, 64 GB RAM DDR4 3200 GSkill, Windows 11 pro, MSFS

If I understand correctly, is enabling Dynamic LOD in the settings the only requirement for hybrid mode to work, assuming both use the same target FPS?

Edited by Denco

ASUS Maximus VIII Hero Alpha, Intel Core i7 6700K 4.5GHz, Corsair Vengeance Black LPX 32GB, MSI 5060Ti 16G Ventus 3X, Samsung 850 EVO 500GB SSD

  • Author
1 hour ago, Denco said:

If I understand correctly, is enabling Dynamic LOD in the settings the only requirement for hybrid mode to work, assuming both use the same target FPS?

You must be in Expert mode, as being in Non-Expert mode will automatically disable Dynamic Settings for the duration of your flight session. Also, from the readme:
 

  • Works best when using MSFS-set FPS cap, with Max and Dynamic Settings Target Frame Rates in MSFS settings set to the native frame rate equivalent of the AutoFPS target FPS, and the FPS Cap automation mode in AutoFPS.
  • If not using an FPS cap, it is recommended to set the MSFS dynamic settings target frame rate to at least 10 FPS lower than the native frame rate equivalent of the AutoFPS target FPS for best results.

 

9800X3D | 4090 | 64GB | 2+1TB NVME | 2TB SSD | 2TB HDD | 85/50/43” TVs | Quest 3 | DOF H3 Motion Rig | Buttkicker | T.16000M Flight Kit

MSFS @ 4K Ultra DLSS Performance FG 80 FPS |  VR VDXR Godlike 80Hz SSW | MSFS VR DLSS Quality, Ultra Preset - Windows 11

Acer Nitro 5 | i5-11400H | RTX 3060 6 GB | 32GB DDR4 | 15.6" FHD IPS 144Hz | 2 x 512 GB SSD | Windows 11

11 minutes ago, Reset XPDR said:

You must be in Expert mode, as being in Non-Expert mode will automatically disable Dynamic Settings for the duration of your flight session. Also, from the readme:
 

  • Works best when using MSFS-set FPS cap, with Max and Dynamic Settings Target Frame Rates in MSFS settings set to the native frame rate equivalent of the AutoFPS target FPS, and the FPS Cap automation mode in AutoFPS.
  • If not using an FPS cap, it is recommended to set the MSFS dynamic settings target frame rate to at least 10 FPS lower than the native frame rate equivalent of the AutoFPS target FPS for best results.

 

I am using framegen. I have capped the fps using RTSS at 40. Since FG disables the option to set in game fps cap. I have set the target fps in autofps app to 40 and option selected to 'FR'. Is this ok ? Or do i need to select a different option in autofps app? 

Baber

 

My Youtube Channel http://www.youtube.com/user/HDOnlive

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.