On 8/13/2025 at 12:47 PM, Reset XPDR said:

 

I am using this exact combo right now and it is connecting and working.

If you haven't done all this, please do so:

If after installing and running the app your simconnect always stays red, your TLOD and OLOD values show as zero or you see "Critical Exception occurred: MSFS_AutoFPS - Unable to load DLL 'GpuzShMem.x64.dll' or one of its dependencies" in the log file:

• Try reinstalling the app with the "Install Latest Redistributable" options selected. If any of the redistributables fail to install during this process, try downloading and installing/repairing (as applicable):
  • A Microsoft official version of “Microsoft Visual C++ 2015 - 2022 Redistributable”, which may be missing from your Windows installation. Try installing this and this.
  • The NET desktop runtime from here if still available. Alternatively, go to the Micrsoft .NET 8.0 download page here and download and install the latest .NET Desktop Runtime X64 version.
• If still not resolved and the error code in your AutoFPS log file is Exception 31, you most likely have a corrupt MSFS WASM installation.
  • First, try deleting the MSFS WASM folder, located under the Microsoft Flight Simulator directory in either %appdata% or %localappdata% for Steam and MS Store install directories respectively, which will rebuild when you next run MSFS.
  • If that doesn't fix it, a full clean reinstall of MSFS will be required, which can be done in less than 15 minutes for MSFS 2024 but may take many hours for MSFS 2020.
    • If reinstalling MSFS 2024, you need to do a clean install, as outlined for your MSFS version here.
      • Ensure you backup/relocate your Community folder BEFORE you do this, then put it back when the reinstallation is complete.
      • All your settings, controller assignments, career progression and your pilot profile are retained.

I have already done all these things, including full and clean reinstall msfs2024, but i have the same issue, no connect... log files says Exception: 31

6 hours ago, Reset XPDR said:

It was a bit of a doozy to work out why ALT-R was no longer functioning, but it was entertaining and I believe I have fixed in now in 0.4.5.5-test1 here, so if you could give it a try to confirm it now works I would appreciate it.

It will conflict with the AMD shortcut to open the Adrenalin app.

9 hours ago, PlantsAreDead said:

It works, but only if you've previously selected AutoFPS as the active window. If the simulator is running and the window is displayed in the simulator, it doesn't work.

That is the way it has always worked, per the readme:

Reset button

• Resets TLOD, Clouds, Auto Target FPS and graphics mode detection to initial state.
• Useful to reinitialise and recommence the seek process for TLOD Min/Top + should conditions change significantly from what they were on initial start-up.
• Can be activated by pressing ALT-R while the app has the focus, making it suitable to be assigned as a VR-friendly voice command with an app like VoiceAttack.

I did it this way because Reset should be a rarely used button (the app didn't even have one for a very long time) and 2D users can simply click it on the app's UI. It is more difficult for VR users to do this, as the UI does not normally appear in VR,  and this gives them a way to control it via VoiceAttack, hence the simple access key method was added.

Is there some particular reason you need to use Reset often enough that switching to the app window and clicking the Reset button on the UI is too onerous?

4 hours ago, Wundermann said:

It will conflict with the AMD shortcut to open the Adrenalin app.

That it does, but that specific hotkey can be changed or removed in the Adrenaline app if you really want to use this access key with AutoFPS.

As just mentioned to PlantsAreDead, this access key method of resetting the app was designed as a way for VR users to Reset AutoFPS without having to see it. For 2D users, it is simpler to just click on the Reset button rather than press ALT-R to do the same.

9 hours ago, Siberier said:

I have already done all these things, including full and clean reinstall msfs2024, but i have the same issue, no connect... log files says Exception: 31

In every case that a user has had a persisent Exception 31 issue after reinstalling MSFS 2024, it has turned out that they have not followed the clean installation instructions to the letter, specifically the instruction to manually delete the main MSFS 2024 installation folder (noting my warning to backup your Community folder first). You also need to clean install AutoFPS after the clean install of MSFS 2024 so that the mobifilight folder gets put back in your Community folder.

With my system it is often advisable to turn down beforehand and not only at 1000 feet, by resetting I could have the level readjusted in critical moments, so I find the function practical

8 minutes ago, PlantsAreDead said:

With my system it is often advisable to turn down beforehand and not only at 1000 feet, by resetting I could have the level readjusted in critical moments, so I find the function practical

If you are having to reset the app this often then your settings are not appropriate for how you are flying, so I suggest you change them, back to default if necessary.  

The only times Reset may be required is if you start up LSFG after a flight session with the app has been started and you want LSFG to be detected and what I quoted from the readme, namely:

Useful to reinitialise and recommence the seek process for TLOD Min/Top + should conditions change significantly from what they were on initial start-up.

Other than those two things, the Reset button should normally be left alone.

I tried the latest version in MSFS 2020 but couldnt make it work. Is it compatible with SU 16 MSFS 2020?

32 minutes ago, History said:

I tried the latest version in MSFS 2020 but couldnt make it work. Is it compatible with SU 16 MSFS 2020?

Yes it is. Copy and paste your log file, located in %appdata%\MSFS_AutoFPS\log, associated with it not working in a direct message to me and I will take a look.

20 minutes ago, Reset XPDR said:

Yes it is. Copy and paste your log file, located in %appdata%\MSFS_AutoFPS\log, associated with it not working in a direct message to me and I will take a look.

Thank you. I will try again and see how it goes. 

3 hours ago, History said:

I tried the latest version in MSFS 2020 but couldnt make it work. Is it compatible with SU 16 MSFS 2020?

Just to be sure, I just tried AutoFPS 0.4.5.4 with MSFS 2020 1.39.9.0 (SU16) and it worked fine:

And the log:

2025-08-15 15:47:02.524 [INF] [ MemoryManager:GetActiveDXVersion ] Steam 1.39.9.0  MSFS2020 version detected - DX12 
2025-08-15 15:47:02.524 [DBG] [ MemoryManager:MemoryManager      ] New MSFS/app/offset combo detected 
2025-08-15 15:47:02.524 [DBG] [ MemoryManager:MemoryManager      ] Trying offsetModuleBase: 0x004B2368 
2025-08-15 15:47:02.529 [INF] [ MemoryManager:GetOptSettings     ] Successfully read required settings from UserOpt.cfg 
2025-08-15 15:47:02.529 [DBG] [ MemoryManager:MemoryManager      ] Running primary compatibility test for new MSFS/app/offset combo 
2025-08-15 15:47:02.529 [DBG] [ MemoryManager:MemoryManager      ] Primary compatibility test passed - memory writes enabled 

 

37 minutes ago, Reset XPDR said:

Just to be sure, I just tried AutoFPS 0.4.5.4 with MSFS 2020 1.39.9.0 (SU16) and it worked fine:

And the log:

2025-08-15 15:47:02.524 [INF] [ MemoryManager:GetActiveDXVersion ] Steam 1.39.9.0  MSFS2020 version detected - DX12 
2025-08-15 15:47:02.524 [DBG] [ MemoryManager:MemoryManager      ] New MSFS/app/offset combo detected 
2025-08-15 15:47:02.524 [DBG] [ MemoryManager:MemoryManager      ] Trying offsetModuleBase: 0x004B2368 
2025-08-15 15:47:02.529 [INF] [ MemoryManager:GetOptSettings     ] Successfully read required settings from UserOpt.cfg 
2025-08-15 15:47:02.529 [DBG] [ MemoryManager:MemoryManager      ] Running primary compatibility test for new MSFS/app/offset combo 
2025-08-15 15:47:02.529 [DBG] [ MemoryManager:MemoryManager      ] Primary compatibility test passed - memory writes enabled 

 

Thank you for all of your contributions sir!

On 8/14/2025 at 7:15 PM, Siberier said:

I have already done all these things, including full and clean reinstall msfs2024, but i have the same issue, no connect... log files says Exception: 31

So. I have done clean reinstall of autofps and everything is getting OK! Thank you very much!

Hi, I've noticed the Line of Sight Correction checkbox doesn't remain enabled between sessions. Is this a known issue?

2 hours ago, LukeFF said:

Hi, I've noticed the Line of Sight Correction checkbox doesn't remain enabled between sessions. Is this a known issue?

Good catch. It actually does remain enabled between sessions but it erroneously doesn't show on the UI unless the current or last selected profile is ALTOD or FPS Cap. I shall fix and put it in the next test release.