5 hours ago, Reset XPDR said:

What app version are you using and what specific error message is popping up? If a more recent app version, have you tried any of the suggested remedies and if so which ones? If on an older version of the app have you tried updating to the latest version? 

Fixed by uninstalling and reinstalling newer version instead of updating.

It seems when updating caused the issue.

Thanks

Mike

6 hours ago, mikeymike said:

Fixed by uninstalling and reinstalling newer version instead of updating.

It seems when updating caused the issue.

Thanks

Mike

That's great news. Can you tell me what version you went from and to? Also is there any reason why you uninstalled/reinstalled instead of just updating it? Sorry to be pedantic but I am trying to work out exactly what it is that fixes this elusive bug. Thanks.

For anyone experiencing the SimConnect Exception 31 issue, may I ask that, without uninstalling the app first, you update to 0.4.6.0-test6 or later, available here,  and if the issue still persists follow each step in the message box that appears until it is resolved, namely:

MSFS WASM Module Error (Exception 31)

This usually means there is a problem with the SimConnect interface between MSFS and the app.

1. Run the AutoFPS installer and select Repair, then reboot your PC.

2. If the problem continues, close MSFS and delete the MSFS WASM folder under (WASM path relevant to your MSFS install will be shown here). Then reboot your PC.

3. If the issue still occurs, perform a full CLEAN reinstall of MSFS per the explicit instructions in the readme.

4. If none of the above steps resolve the issue, report it using the button below.

[Report Issue] [Close]

I am really hoping that it will only take step 1, which is a new installer feature that effectively fresh reinstalls AutoFPS and retains your app settings, for the issue to be resolved.

Let me know if anyone tries this and how far you had to go in the list. Thanks.

Edited December 26, 2025Dec 26 by Reset XPDR

2 hours ago, Reset XPDR said:

That's great news. Can you tell me what version you went from and to? Also is there any reason why you uninstalled/reinstalled instead of just updating it? Sorry to be pedantic but I am trying to work out exactly what it is that fixes this elusive bug. Thanks.

Hi

Yes i updated from the one before the latest test .

That caused the error.

So i thought ill uninstall and reinstall the latest test.

And worked.

Mike

MSFS_AutoFPS 0.4.6.0 has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase.

This release delivers major SimConnect changes to minimise and resolve Exception 31 occurrences, introduces a new Repair Install option and installer UI clarity improvements, refines Auto Increase Clouds behaviour for smarter performance control when GPU-Z is running, and includes general improvements and fixes across the app.

Example (new) Repair Install:

Edited December 30, 2025Dec 30 by Reset XPDR

MSFS_AutoFPS 0.4.6.1 VRAM+ Hotfix has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase. 

This VRAM+ Hotfix improves VRAM+ reliability, activation, recovery behaviour, and configuration access, adds VRAM+ support to Auto TLOD mode, and resolves a test‑version update detection issue.

On 1/3/2026 at 12:38 AM, Reset XPDR said:

MSFS_AutoFPS 0.4.6.1 VRAM+ Hotfix has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase. 

This VRAM+ Hotfix improves VRAM+ reliability, activation, recovery behaviour, and configuration access, adds VRAM+ support to Auto TLOD mode, and resolves a test‑version update detection issue.

Interesting addition with VRAM+ mode added to Auto TLOD mode. I use that for my flights, but wondering about if it is possible to implement an option to use the RTSS VRAM sensor in any way for monitoring the VRAM usage? That will enable those of us who use RTSS for FPS limiting to use it also for that, which would be very handy. I do not think (disclaimer, I am not a developer) it should be too much work to implement it given how I have seen RTSS interact with other softwares and how simply the sensors are configured. 

hi, I have good fps locked at 40 in sim plus Frame genx2. What  should I use in AutoFps? I have read the documentation on Github. currently without AutoFps I have tlod and olod on 200. Mainly airliners. Have now and then an occasional stutter which I would like to eliminate.

On 1/3/2026 at 12:38 AM, Reset XPDR said:

MSFS_AutoFPS 0.4.6.1 VRAM+ Hotfix has just been formally released, available either through auto update in the app or from here. My thanks goes out to all who provided valuable feedback during the test phase. 

This VRAM+ Hotfix improves VRAM+ reliability, activation, recovery behaviour, and configuration access, adds VRAM+ support to Auto TLOD mode, and resolves a test‑version update detection issue.

After updating to 0.4.6.1 i don't see the VRAM+ checkbox anymore even if i have GPU-Z running and VRAM usage is correctly displayed in AutoFPS. Is this working as intended? Nothing changed by my side since 0.4.6.0

4 hours ago, Blaster79 said:

After updating to 0.4.6.1 i don't see the VRAM+ checkbox anymore even if i have GPU-Z running and VRAM usage is correctly displayed in AutoFPS. Is this working as intended? Nothing changed by my side since 0.4.6.0

No this is not intended. The change I made in 0.4.6.1 to make VRAM+ controls show all the time is to look for the process name "GPU-Z" instead of waiting for the session to start to get a GPU load reading. I set it to be an exact match of "GPU-Z", as I believed this was the only variant process name out there, but maybe yours is showing as something else.

Can I get you to open up task manager on the process tab, find GPU-Z in the list of background tasks, right click and select Go to Details:

then tell me exacty what it takes you to:

eg. GPU-Z.exe in this case.

Also, please let me know what version of GPU-Z you are running. FYI v2.68.0 is the latest version.

Edit: BTW, if you are using Expert mode and have the app window reduced like I have in that screenshot for 0.4.6.1, the VRAM+ control is actually present but is on the  Expert settings panel that you have hidden. If so, just double click anywhere a control is not present and you will cycle through the reduction views back to the full app window where you will find the VRAM+ control.

Edited January 4Jan 4 by Reset XPDR

5 hours ago, pilotter said:

hi, I have good fps locked at 40 in sim plus Frame genx2. What  should I use in AutoFps? I have read the documentation on Github. currently without AutoFps I have tlod and olod on 200. Mainly airliners. Have now and then an occasional stutter which I would like to eliminate.

Did you see the FAQ entry in the readme on settings suggestions?

 

Quote

 

You developed this app and must therefore know how to best configure it, so surely you can tell me the best settings for me to use?

• The best settings for you to use are highly dependent on your system's capabilities, what other addons and supporting apps you use, and what your expectation of "best" actually is - higher FPS, improved visuals, smoother experience - some of which are mutually exclusive (i.e you can have one but only at the expense of another).
• Additionally, there are now thousands of users of this app and I simply don't have the time to provide individual settings advice to everyone that asks.
• As such, your best course of action is to start off with non-expert mode to see what the app actually does and when.
• Once you are comfortable with how the app operates, enable expert settings and start reading the tooltip and readme on what each setting does.
• When making changes, it is best to make small changes to only a few settings so that you can see the effect of them and adjust as desired.

 

7 hours ago, Benjamin H said:

Interesting addition with VRAM+ mode added to Auto TLOD mode. I use that for my flights, but wondering about if it is possible to implement an option to use the RTSS VRAM sensor in any way for monitoring the VRAM usage? That will enable those of us who use RTSS for FPS limiting to use it also for that, which would be very handy. I do not think (disclaimer, I am not a developer) it should be too much work to implement it given how I have seen RTSS interact with other softwares and how simply the sensors are configured. 

The RTSS shared memory interface the app uses is very limited in the data it provides and does not currently provide any such VRAM sensor data. As this interface was developed by someone else in a slightly different language (C++ instead of C#) and uses data that I do not currently have access to, it would likely be a significant undertaking to access and expose this data to AutoFPS to satisfy a very small number of users, which I generally don't do.

Given that the app already has a suitable and very reliable VRAM usage data source through the GPU-Z companion app, I suggest you use that. If you follow the instructions in the readme, GPU-Z is very easy to set up to auto run in the background and has an extremely small system footprint (< 4.5MB memory and negligible CPU load).

 

1 hour ago, Reset XPDR said:

No this is not intended. The change I made in 0.4.6.1 to make VRAM+ controls show all the time is to look for the process name "GPU-Z" instead of waiting for the session to start to get a GPU load reading. I set it to be an exact match of "GPU-Z", as I believed this was the only variant process name out there, but maybe yours is showing as something else.

Can I get you to open up task manager on the process tab, find GPU-Z in the list of background tasks, right click and select Go to Details:

 

Hi, in my "go to details" screen the app was named GPU-Z.2.68.0.exe (i have the latest version too).

I just renamed the exe to GPU-Z.exe and now i see it correctly on AutoFPS.

11 minutes ago, Blaster79 said:

Hi, in my "go to details" screen the app was named GPU-Z.2.68.0.exe (i have the latest version too).

I just renamed the exe to GPU-Z.exe and now i see it correctly on AutoFPS.

OK, that's why. It seems that the latest version of GPU-Z doesn't automatically run an installer like previous versions, so it runs the downloaded exe by default which can have the trailing version numbers in the process name. Since this will likely affect other users wanting to use VRAM+, I will update the app shortly to fix this. Thanks for bringing it to my attention.

@Blaster79, I have updated the app to look for any process name starting with "GPU-Z" to consider that GPU-Z is running, which should solve your original issue. Just to be doubly sure, I have also reintroduced the method I used prior to 0.4.6.1 as a backup detection method, however this one will only work when you are in a flight session just as before.

Can I get you rename your GPU-Z exe back to "GPU-Z.2.68.0.exe", run it then update to 0.4.6.2-RC2, available here or enable + Tests and auto update to it, and confirm that your VRAM+ controls now show at all times. It should now behave like this:

Let me know how it goes. I will likely release this as a hotfix once you have verified it is working correctly. Thanks.