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

I noticed that if you try to change msfs 2024 gfx settings while running AutoFPS, you'll get a message that basically doesn't want you to do that, which makes sense.

Lately, I've been playing with FCR and like to run FSR3, instead of DLSS when watching replays. Less ghosting. I've been switching this on the fly with no message coming from AutoFPS. Does this cause an issue with AutoFPS?

Thanks

i7-13700KF @ 5.3GHz    32.0GB DDR5 @ 5600    RTX 3080    65" LG OLED @ 4k

  • 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

 Sir thank you for autofps 

Absolutely love it.

Question thou regarding using frame gen as I just started using it For 2020 how would i go about settings in auto fps.

 

Shall i use cap sensitivity or tolerance?

Man 3x fg?

Fps target at 48?

144hz monitor freesync 

 

Vsync is on in Nvidia control panel.

Thanks 

Mike

Edited by mikeymike

  • Author
5 hours ago, 0stones0 said:

I noticed that if you try to change msfs 2024 gfx settings while running AutoFPS, you'll get a message that basically doesn't want you to do that, which makes sense.

Lately, I've been playing with FCR and like to run FSR3, instead of DLSS when watching replays. Less ghosting. I've been switching this on the fly with no message coming from AutoFPS. Does this cause an issue with AutoFPS?

Thanks

AutoFPS only makes a fuss if you change a setting it is currently managing, or could potentially manage if you changed AutoFPS settings mid-flight. FG type is not one of them, hence no warning and this is not an issue.

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
37 minutes ago, mikeymike said:

 Sir thank you for autofps 

Absolutely love it.

Question thou regarding using frame gen as I just started using it For 2020 how would i go about settings in auto fps.

 

Normally, I don't give out individual settings advice, but you've been around here for a long time so I will make an exception this time.

 

Quote

Shall i use cap sensitivity or tolerance?

FPS Cap if you have capped FPS somewhere else and your system is running mostly at that FPS cap, otherwise FPS Sensitivity (don't worry about using Tolerance mode unless Sensitivity mode is a stutter fest)

Quote

Man 3x fg?

If you have externally set FG to 3X and it is not otherwise auto detecable by AutoFPS, then yes.

Quote

Fps target at 48?

If 48 FPS is your target after 3X FG is factored in, then your raw FPS is 24 which is pretty low to get a good FG experience. If, on the other hand, 48 FPS is your base FPS, which is good for FG, then set your target FPS to 3X times that ie. 144.
 

Quote

 

144hz monitor freesync 

Vsync is on in Nvidia control panel.

 

If your target FPS is 144 from the point above, then 144 is all you will get so you may as well use FPS Cap mode in that case.

 

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

14 minutes ago, Reset XPDR said:

Normally, I don't give out individual settings advice, but you've been around here for a long time so I will make an exception this time.

 

FPS Cap if you have capped FPS somewhere else and your system is running mostly at that FPS cap, otherwise FPS Sensitivity (don't worry about using Tolerance mode unless Sensitivity mode is a stutter fest)

If you have externally set FG to 3X and it is not otherwise auto detecable by AutoFPS, then yes.

If 48 FPS is your target after 3X FG is factored in, then your raw FPS is 24 which is pretty low to get a good FG experience. If, on the other hand, 48 FPS is your base FPS, which is good for FG, then set your target FPS to 3X times that ie. 144.
 

If your target FPS is 144 from the point above, then 144 is all you will get so you may as well use FPS Cap mode in that case.

 

Understood.

Appreciated 

Thank you and god bless sir.

Mike

 

 

2 hours ago, Reset XPDR said:

AutoFPS only makes a fuss if you change a setting it is currently managing, or could potentially manage if you changed AutoFPS settings mid-flight. FG type is not one of them, hence no warning and this is not an issue.

I forgot to mention that this is in the anti-aliasing area and it is being changed in sim, not in AutoFPS. Although, it still doesn't seem to be affecting anything, changing in mid flight.

Thanks again.

i7-13700KF @ 5.3GHz    32.0GB DDR5 @ 5600    RTX 3080    65" LG OLED @ 4k

  • Author
1 hour ago, 0stones0 said:

I forgot to mention that this is in the anti-aliasing area and it is being changed in sim, not in AutoFPS. Although, it still doesn't seem to be affecting anything, changing in mid flight.

Thanks again.

Yes, anything AA, FG , and Vsync in MSFS settings does not cause a red card because the app may monitor them but does not actually control them.

All you really need to know is that if you are not being pinged, then that is an acceptable setting to change.

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

I am on MSFS2024/v0.4.6.4 and I keep getting the 'unable to attach MSFS" error. Had this error with several versions now (also 4.6.5).

Have tried all suggestions in the error message (restart in menu, virus exclusion, admin) but to no avail. A reinstall of the app makes it work one time, but then it is back to the same error.

Any ideas what could be causing this?

Edited by LGKR

  • Author
5 minutes ago, LGKR said:

I am on MSFS2024/v0.4.6.4 and I keep getting the 'unable to attach MSFS" error. Had this error with several versions now (also 4.6.5).

Have tried all suggestions in the error message (restart in menu, virus exclusion, admin) but to no avail. A reinstall of the app makes it work one time, but then it is back to the same error.

Any ideas what could be causing this?

I won't be in front of my Dev PC for about 8 hours, so I can't really speculate for sure what the issue is but it is usually a permissions issue with AutoFPS being able to see that MSFS is running but not being able to get access to where it lives in memory. 

In the interim, can you message me the contents (copy and paste - you can't attach files here) of your latest log file, located in %appdata%/MSFS_AutoFPS/log, and I will see if it reveals any more. 

Also, has AutoFPS worked for you previously?  If so, what version did it stop working? Were there any other major changes on your system around that time, hardware or software?

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

12 minutes ago, Reset XPDR said:

I won't be in front of my Dev PC for about 8 hours, so I can't really speculate for sure what the issue is but it is usually a permissions issue with AutoFPS being able to see that MSFS is running but not being able to get access to where it lives in memory. 

In the interim, can you message me the contents (copy and paste - you can't attach files here) of your latest log file, located in %appdata%/MSFS_AutoFPS/log, and I will see if it reveals any more. 

Also, has AutoFPS worked for you previously?  If so, what version did it stop working? Were there any other major changes on your system around that time, hardware or software?

Many thanks for your quick reply. AutoFPS has worked fine for a long time, but with different versions I have suddenly gotten this particular error, seemingly for no reason. I cannot remember with which version this started. Yesterday and today have been particularly difficult and I cannot get the app working at all. No changes to hardware or software.

Again many thanks if you would take a look at the log file, it is really annoying when it is not working!

log as follows:

 

2026-02-11 10:48:52.062 [INF] ----------------------------------------------------------------------- 
2026-02-11 10:48:52.205 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.4 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-02-11 10:48:52.209 [INF] [ App:InitSystray                  ] Creating SysTray Icon ... 
2026-02-11 10:48:52.358 [INF] [ ServiceController:Run            ] Service starting ... 
2026-02-11 10:48:52.526 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:NFR ATgtFPS:False FltType:IFR TgtFPS:40 TLODMethod:ATLOD Tol:5 LOS-C:False TMin:150 TBXtra:false TMax:265 TMtns:False TNightDiv2:False TLODBAlt:2000 TLODTAlt:10000 CustomOLOD:False RSet:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2026-02-11 10:48:53.358 [INF] [ MainWindow:DownloadLatestRelease ] Downloaded fresh release data to check for updates. 
2026-02-11 10:48:53.389 [INF] [ MainWindow:CheckForUpdates       ] Latest test version available: 0.4.6.5-test4. Update option: Show Updates + Test Versions 
2026-02-11 10:48:54.377 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2026-02-11 10:49:26.015 [ERR] [ MemoryManager:MemoryManager      ] Unable to determine MSFS version number after 15 attempts - memory writes disabled. 
2026-02-11 10:49:26.037 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2026-02-11 10:49:26.037 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 5s between Retries 
2026-02-11 10:49:26.152 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2026-02-11 10:49:26.253 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2026-02-11 10:49:26.361 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2026-02-11 10:49:31.297 [FTL] [ ServiceController:Run            ] MSFS compatibility test failed - app disabled. 
2026-02-11 10:49:31.397 [INF] [ MobiSimConnect:Disconnect        ] SimConnect Connection closed 
2026-02-11 10:49:53.567 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
2026-02-11 10:50:18.640 [INF] ----------------------------------------------------------------------- 
2026-02-11 10:50:18.681 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.4 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-02-11 10:50:18.683 [INF] [ App:InitSystray                  ] Creating SysTray Icon ... 
2026-02-11 10:50:18.746 [INF] [ ServiceController:Run            ] Service starting ... 
2026-02-11 10:50:18.895 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:NFR ATgtFPS:False FltType:IFR TgtFPS:40 TLODMethod:ATLOD Tol:5 LOS-C:False TMin:150 TBXtra:false TMax:265 TMtns:False TNightDiv2:False TLODBAlt:2000 TLODTAlt:10000 CustomOLOD:False RSet:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2026-02-11 10:50:19.190 [INF] [ MainWindow:DownloadLatestRelease ] Downloaded fresh release data to check for updates. 
2026-02-11 10:50:19.211 [INF] [ MainWindow:CheckForUpdates       ] Latest test version available: 0.4.6.5-test4. Update option: Show Updates + Test Versions 
2026-02-11 10:50:19.756 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2026-02-11 10:50:50.914 [ERR] [ MemoryManager:MemoryManager      ] Unable to determine MSFS version number after 15 attempts - memory writes disabled. 
2026-02-11 10:50:50.927 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2026-02-11 10:50:50.927 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 5s between Retries 
2026-02-11 10:50:51.031 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2026-02-11 10:50:51.133 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2026-02-11 10:50:51.235 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2026-02-11 10:50:55.777 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
2026-02-11 10:51:01.279 [INF] ----------------------------------------------------------------------- 
2026-02-11 10:51:01.320 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.4 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-02-11 10:51:01.321 [INF] [ App:InitSystray                  ] Creating SysTray Icon ... 
2026-02-11 10:51:01.388 [INF] [ ServiceController:Run            ] Service starting ... 
2026-02-11 10:51:01.530 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:NFR ATgtFPS:False FltType:IFR TgtFPS:40 TLODMethod:ATLOD Tol:5 LOS-C:False TMin:150 TBXtra:false TMax:265 TMtns:False TNightDiv2:False TLODBAlt:2000 TLODTAlt:10000 CustomOLOD:False RSet:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2026-02-11 10:51:01.531 [INF] [ MainWindow:DownloadLatestRelease ] Using cached release data to check for updates (age: 42.3s) 
2026-02-11 10:51:01.552 [INF] [ MainWindow:CheckForUpdates       ] Latest test version available: 0.4.6.5-test4. Update option: Show Updates + Test Versions 
2026-02-11 10:51:02.408 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2026-02-11 10:51:33.726 [ERR] [ MemoryManager:MemoryManager      ] Unable to determine MSFS version number after 15 attempts - memory writes disabled. 
2026-02-11 10:51:33.738 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2026-02-11 10:51:33.739 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 5s between Retries 
2026-02-11 10:51:33.844 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2026-02-11 10:51:33.946 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2026-02-11 10:51:34.047 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2026-02-11 10:51:38.995 [FTL] [ ServiceController:Run            ] MSFS compatibility test failed - app disabled. 
2026-02-11 10:51:39.096 [INF] [ MobiSimConnect:Disconnect        ] SimConnect Connection closed 
2026-02-11 10:51:45.511 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
2026-02-11 10:53:13.661 [INF] ----------------------------------------------------------------------- 
2026-02-11 10:53:13.679 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.5-test4 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-02-11 10:53:13.700 [INF] [ App:InitSystray                  ] Creating SysTray Icon ... 
2026-02-11 10:53:13.770 [INF] [ ServiceController:Run            ] Service starting ... 
2026-02-11 10:53:13.894 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:NFR ATgtFPS:False FltType:IFR TgtFPS:40 TLODMethod:ATLOD Tol:5 LOS-C:False TMin:150 TBXtra:false TMax:265 TMtns:False TNightDiv2:False TLODBAlt:2000 TLODTAlt:10000 CustomOLOD:False RSet:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2026-02-11 10:53:14.485 [INF] [ MainWindow:DownloadLatestRelease ] Downloaded fresh release data to check for updates. 
2026-02-11 10:53:14.503 [INF] [ MainWindow:CheckForUpdates       ] Latest release version available: 0.4.6.4. Update option: Show Updates + Test Versions 
2026-02-11 10:53:14.778 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2026-02-11 10:53:28.052 [INF] [ MainWindow:PerfOptToggle         ] Perf opt enabled 
2026-02-11 10:53:45.943 [ERR] [ MemoryManager:MemoryManager      ] Unable to determine MSFS version number after 15 attempts - memory writes disabled. 
2026-02-11 10:53:45.957 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2026-02-11 10:53:45.957 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 5s between Retries 
2026-02-11 10:53:46.062 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2026-02-11 10:53:46.164 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2026-02-11 10:53:46.266 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2026-02-11 10:53:51.213 [FTL] [ ServiceController:Run            ] MSFS compatibility test failed - app disabled. 
2026-02-11 10:53:51.316 [INF] [ MobiSimConnect:Disconnect        ] SimConnect Connection closed 
2026-02-11 10:54:14.908 [INF] [ ServiceModel:RestorePriority     ] Priority restore skipped — no priority change was applied. 
2026-02-11 10:54:14.908 [INF] [ ServiceModel:RestoreAffinity     ] Affinity restore skipped — no affinity change was applied. 
2026-02-11 10:54:14.908 [INF] [ ServiceModel:RestoreOriginalPowe ] No power plan change to restore. 
2026-02-11 10:54:14.909 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
2026-02-11 11:01:27.395 [INF] ----------------------------------------------------------------------- 
2026-02-11 11:01:27.427 [INF] [ App:InitLog                      ] MSFS_AutoFPS v0.4.6.5-test4 started! Log Level: Debug Log File: ..\log\MSFS_AutoFPS.log 
2026-02-11 11:01:27.477 [INF] [ App:InitSystray                  ] Creating SysTray Icon ... 
2026-02-11 11:01:27.633 [INF] [ ServiceController:Run            ] Service starting ... 
2026-02-11 11:01:27.805 [INF] [ MainWindow:LoadSettings          ] MSFS:24 Expert:True Mode:NFR ATgtFPS:False FltType:IFR TgtFPS:40 TLODMethod:ATLOD Tol:5 LOS-C:False TMin:150 TBXtra:false TMax:265 TMtns:False TNightDiv2:False TLODBAlt:2000 TLODTAlt:10000 CustomOLOD:False RSet:False VRAM+:Max Vrec:93% Vhld:96% Vred:98% 
2026-02-11 11:01:28.521 [INF] [ MainWindow:DownloadLatestRelease ] Downloaded fresh release data to check for updates. 
2026-02-11 11:01:28.561 [INF] [ MainWindow:CheckForUpdates       ] Latest release version available: 0.4.6.4. Update option: Show Updates + Test Versions 
2026-02-11 11:01:28.656 [INF] [ IPCManager:WaitForSimulator      ] Simulator started 
2026-02-11 11:01:59.984 [ERR] [ MemoryManager:MemoryManager      ] Unable to determine MSFS version number after 15 attempts - memory writes disabled. 
2026-02-11 11:01:59.999 [INF] [ MobiSimConnect:Connect           ] SimConnect Connection open 
2026-02-11 11:01:59.999 [INF] [ IPCManager:WaitForConnection     ] Connection not established - waiting 5s between Retries 
2026-02-11 11:02:00.104 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received 
2026-02-11 11:02:00.207 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection 
2026-02-11 11:02:00.309 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened 
2026-02-11 11:02:03.818 [INF] [ ServiceModel:RestorePriority     ] Priority restore skipped — no priority change was applied. 
2026-02-11 11:02:03.819 [INF] [ ServiceModel:RestoreAffinity     ] Affinity restore skipped — no affinity change was applied. 
2026-02-11 11:02:03.819 [INF] [ ServiceModel:RestoreOriginalPowe ] No power plan change to restore. 
2026-02-11 11:02:03.820 [INF] [ App:OnExit                       ] MSFS_AutoFPS exiting ... 
 

 

 

 

 

  • Author
5 minutes ago, LGKR said:

Many thanks for your quick reply. AutoFPS has worked fine for a long time, but with different versions I have suddenly gotten this particular error, seemingly for no reason. I cannot remember with which version this started. Yesterday and today have been particularly difficult and I cannot get the app working at all. No changes to hardware or software.

Again many thanks if you would take a look at the log file, it is really annoying when it is not working!

log as follows:

 

2026-02-11 10:50:50.914 [ERR] [ MemoryManager:MemoryManager      ] Unable to determine MSFS version number after 15 attempts - memory writes disabled. 
 

This line is of interest as it seems to be stumbling on the MSFS version number, which I have not seen before but gives me something to go on. I will be in contact via PM with what I find and possibly a special instrumented test version that can tell me a bit more about why the version number is not coming through.

IIRC, it pulls the MSFS version number from the MSFS Window title bar, so it would be helpful if you could tell me exactly what it says on your system. If in full screen mode, you need to hit ALT-ENTER to go to windowed mode to see the title. Once you have recorded the exact title, hit ALT-ENTER again to return to full screen. It should be "Microsoft Flight Simulator 2024 - 1.6.34.0".

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

50 minutes ago, Reset XPDR said:

This line is of interest as it seems to be stumbling on the MSFS version number, which I have not seen before but gives me something to go on. I will be in contact via PM with what I find and possibly a special instrumented test version that can tell me a bit more about why the version number is not coming through.

IIRC, it pulls the MSFS version number from the MSFS Window title bar, so it would be helpful if you could tell me exactly what it says on your system. If in full screen mode, you need to hit ALT-ENTER to go to windowed mode to see the title. Once you have recorded the exact title, hit ALT-ENTER again to return to full screen. It should be "Microsoft Flight Simulator 2024 - 1.6.34.0".

Thanks, I can confirm it says 1.6.34.0

  • Author
6 hours ago, LGKR said:

Thanks, I can confirm it says 1.6.34.0

With no "Microsoft Flight Simulator - " prefix? I need to know EXACTLY what it say, including whether those periods are actually commas instead.

In any case, as you are now on 0.4.6.5-test4, I will put out a version shortly that will log exactly what the entire MSFS window title says, so I can know what I am dealing with.

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

47 minutes ago, Reset XPDR said:

With no "Microsoft Flight Simulator - " prefix? I need to know EXACTLY what it say, including whether those periods are actually commas instead.

In any case, as you are now on 0.4.6.5-test4, I will put out a version shortly that will log exactly what the entire MSFS window title says, so I can know what I am dealing with.

Thanks

The window title says:

"Microsoft Flight Simulator 2024 - 1.6.34.0 with WideServer: waiting for clients"

 

  • Author
17 minutes ago, LGKR said:

Thanks

The window title says:

"Microsoft Flight Simulator 2024 - 1.6.34.0 with WideServer: waiting for clients"

 

Ah, that's interesting. We'll take it to PMs from here as I want to keep this thread clean of detailed support. You'll hear from me very soon.

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

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.