On 12/9/2025 at 5:27 PM, Reset XPDR said:

Edit: I just reread your scenerio and have another suggestion. If your free range FPS is normally 115 and you are confident your system can achieve 105 FPS pretty much all the time, including the worst-case performance conditions, then I recommend that you set max frame rate in MSFS to 50, which is the native FPS of 100 FPS with 2X FG, then use FPS Cap mode in AutoFPS with a target FG FPS set to 100. This mode is specifically designed to work with a matching FPS cap and will give you FPS Sensitivity mode like results. Having an FPS cap set in MSFS also tends to minimise stutters as the sim knows what it is targeting internally and can manage performance headroom much better than AutoFPS can because it knows exactly what the headroom actually is. I suggest you give this a try first.

Thanks for all of that I appreciate it and sorry for the late reply.  It was mostly a curiosity because what I notice is that my fixed rate of 60FPS-fg will manifest flicker/strobing that can be a side effect of using NV DLSS FG and when I hit a key to unlock the rate to wide open that effect is diminished greatly, in part from the higher rate (nowhere always near 115 on the ground) but also from the fluctuating rate.  The strobe/flicker really are consistently space pulsations if you will.  But of course no headroom per se unlocked an at some level will introduce a bit of stutter, especially with add-ons like GSX which seems to play best with multiples of 30FSP.  

I've had a handful of users experiencing the dreaded SimConnect Exception 31 issue with the SU4 update to MSFS 2024. This actually happens with each major MSFS update, but the numbers are extremely small (< 0.02% of users) and I have been unable to reproduce it myself, so a simple fix to it has eluded me for more than two years!

Today, I decided to try a rewrite of the Simconnect interface, which allows AutoFPS to try a completely new connection three separate times with a fresh connection, spaced a few seconds apart, instead of fruitlessly trying the same initial connection that seems doomed to never get good communication with AutoFPS again.

If anyone else is experiencing the Exception 31 issue, I strongly suggest you try this new test version before doing anything else as I'd really like to know if it can fix it all on its little lonesome.

As it is experimental (just the Simconnect part), I normally would suggest only users experiencing this issue try it, but if anyone else wants to help me confirm that it still continues to work as normal and is comfortable in rolling back to the release version if anything goes wrong, then I would appreciate feedback on that as well. For the record, it works fine on both of my MSFS systems and, other than new log entries relating to new/revised SimConnect events, is functionally identical to 0.4.5.12.

The new 0.4.6.0-exp1 test version can be downloaded here.

If anyone tries it and has any issues with it, just check (if not already checked) then uncheck the +Test option and you should be presented the auto-update option to roll back to the 0.4.5.12 latest release. If not, just got to the latest release page here, download the 0.4.5.12 installer and run that.

Any feedback on this test version's ability to deal with the Exception 31 issue would be greatly appreciated, preferably on my github issue topic for this here, but also here at Avsim by personal message so a not to clutter up this discussion topic. Thanks.

Edited December 16, 2025Dec 16 by Reset XPDR

17 hours ago, Reset XPDR said:

I've had a handful of users experiencing the dreaded SimConnect Exception 31 issue with the SU4 update to MSFS 2024. This actually happens with each major MSFS update, but the numbers are extremely small (< 0.02% of users) and I have been unable to reproduce it myself, so a simple fix to it has eluded me for more than two years!

Today, I decided to try a rewrite of the Simconnect interface, which allows AutoFPS to try a completely new connection three separate times with a fresh connection, spaced a few seconds apart, instead of fruitlessly trying the same initial connection that seems doomed to never get good communication with AutoFPS again.

If anyone else is experiencing the Exception 31 issue, I strongly suggest you try this new test version before doing anything else as I'd really like to know if it can fix it all on its little lonesome.

As it is experimental (just the Simconnect part), I normally would suggest only users experiencing this issue try it, but if anyone else wants to help me confirm that it still continues to work as normal and is comfortable in rolling back to the release version if anything goes wrong, then I would appreciate feedback on that as well. For the record, it works fine on both of my MSFS systems and, other than new log entries relating to new/revised SimConnect events, is functionally identical to 0.4.5.12.

The new 0.4.6.0-exp1 test version can be downloaded here.

If anyone tries it and has any issues with it, just check (if not already checked) then uncheck the +Test option and you should be presented the auto-update option to roll back to the 0.4.5.12 latest release. If not, just got to the latest release page here, download the 0.4.5.12 installer and run that.

Any feedback on this test version's ability to deal with the Exception 31 issue would be greatly appreciated, preferably on my github issue topic for this here, but also here at Avsim by personal message so a not to clutter up this discussion topic. Thanks.

No negative feedback on this so far, so I have gone ahead and released 0.4.5.6 as a normal test version in order to get broader exposure of the changes. If you try this and experience any SimConnect issues at all, please let me me know.

On 12/16/2025 at 2:26 AM, Reset XPDR said:

If anyone else is experiencing the Exception 31 issue, I strongly suggest you try this new test version before doing anything else as I'd really like to know if it can fix it all on its little lonesome

Not sure but maybe that's why for some reason I see DynamicLOC_ResetEdition in TaskManager as a running process, but the interface doesn't display?  I just yesterday downloaded I think the recent edition.   Have uninstalled and reinstalled a few times but it's still happening.  What might I look at to resolve?

Also, am running in Admin Mode.  Using in 2024.  And when I pause MSFS and look it appears DynLOC is operating, I just can't see the interface so can't select a different profile.  Thanks!

PS:  just read the linked documentation and maybe it was because I installed under Administrator so will REMOVE the app and reinstall, and try again.  Cheers

Edited December 18, 2025Dec 18 by Noel

5 hours ago, Noel said:

Not sure but maybe that's why for some reason I see DynamicLOC_ResetEdition in TaskManager as a running process, but the interface doesn't display?  I just yesterday downloaded I think the recent edition.   Have uninstalled and reinstalled a few times but it's still happening.  What might I look at to resolve?

Also, am running in Admin Mode.  Using in 2024.  And when I pause MSFS and look it appears DynLOC is operating, I just can't see the interface so can't select a different profile.  Thanks!

PS:  just read the linked documentation and maybe it was because I installed under Administrator so will REMOVE the app and reinstall, and try again.  Cheers

DynamicLOD_ResetEdition is different to MSFS_AutoFPS, and always has been, in that the app icon only ever resides in the system tray. When you initially close the window, it does not close the app, rather it sends it to the system tray, and if left like that the app window will not appear when you next start the app because it remembers that as your preference.

If you want to see the app window again, simply locate the app icon in the system tray and either double click on it or right click on it and select Show Window. More details are in the DynamicLOD_ResetEdition readme.

 

BTW, MSFS_AutoFPS, can also be configured to behave similarly by choosing the "App Closes to System Tray" option when installing, which is not checked by default making the app behave like a normal window residing on the task bar and thus differently than DynamicLOD_ResetEdition does.

Edited December 18, 2025Dec 18 by Reset XPDR

Still no feedback on 0.4.5.6-test in over 800 downloads, which is a normally a good thing as it means I likely haven't broken anything when rewriting the SimConnect interface. However, it also means I have no idea whether what I have changed has actually fixed the SimConnect Exception 31 issue for those users that have experienced it and are yet to try a clean reinstall of MSFS 2024.

If you are one of those users, please let me know whether, without having had to resort to the clean reinstall, the new test version has fixed it for you or not. Thanks.

 

18 hours ago, Reset XPDR said:

DynamicLOD_ResetEdition is different to MSFS_AutoFPS, and always has been, in that the app icon only ever resides in the system tray.

Awesome!  I was mystified by this in part because the last time I used it the interface would stay open, behind MSFS.  But yes I see it in the tray now and was able to open it.  Thanks!

Just wanted to say MSFSAutoFPS has been fantastic and invaluable thank you!  But SU4...  Triple 4k screens,  had severe stuttering like many and reverted Nvidia to a prior release..  stable until I activate autofps, the stuttering returns.  Same settings I had on SU3 seem to have more poorer results and reintroduces stuttering in SU4.

2 hours ago, LA JACKPOT said:

Just wanted to say MSFSAutoFPS has been fantastic and invaluable thank you!  But SU4...  Triple 4k screens,  had severe stuttering like many and reverted Nvidia to a prior release..  stable until I activate autofps, the stuttering returns.  Same settings I had on SU3 seem to have more poorer results and reintroduces stuttering in SU4.

Thanks for the feedback. Yours is the only report so far of AutoFPS behaving like this with SU4. Are you continuously experiencing the stuttering, even after AutoFPS has set its initial settings and and is no longer showing changing values, like it does when on the ground?  If so, it may be something other than AutoFPS.

Did you update your AutoFPS when MSFS updated from SU3 to SU4? If so, what AutoFPS version were you running beforehand? Apart a recent change that force sets MSFS defaults when AutoFPS resets, which shouldn't actually affect MSFS if its setting are currently set to default, the way the app makes MSFS settings changes hasn't fundamentally changed since MSFS 2024 was released.

Edited December 19, 2025Dec 19 by Reset XPDR

20 hours ago, Reset XPDR said:

Thanks for the feedback. Yours is the only report so far of AutoFPS behaving like this with SU4. Are you continuously experiencing the stuttering, even after AutoFPS has set its initial settings and and is no longer showing changing values, like it does when on the ground?  If so, it may be something other than AutoFPS.

Did you update your AutoFPS when MSFS updated from SU3 to SU4? If so, what AutoFPS version were you running beforehand? Apart a recent change that force sets MSFS defaults when AutoFPS resets, which shouldn't actually affect MSFS if its setting are currently set to default, the way the app makes MSFS settings changes hasn't fundamentally changed since MSFS 2024 was released.

Thank you!  I dug deeper into it last night and found a strange behavior where I'm needing to toggle the fsr frame gen off/on,  as well as the anti aliasing toggle or I have a pacing issue that doesn't appear in the fps graph as spikes,  something in in terms of a flush/reset happens when that is toggled and the pacing issue resolves itself.  Whatever was happening, autofps was unaware of it because fps data remained consistent around 70 frames with no visible spikes.   Whatever was choking it was made worse by the autofps adjustments.     I do think it's an su4 bug somewhere in the pipelin...  autofps is once again working great after discovering the toggle fix.    Your app really is amazing, thank you so much for the support and updates. 

4 hours ago, LA JACKPOT said:

Thank you!  I dug deeper into it last night and found a strange behavior where I'm needing to toggle the fsr frame gen off/on,  as well as the anti aliasing toggle or I have a pacing issue that doesn't appear in the fps graph as spikes,  something in in terms of a flush/reset happens when that is toggled and the pacing issue resolves itself.  Whatever was happening, autofps was unaware of it because fps data remained consistent around 70 frames with no visible spikes.   Whatever was choking it was made worse by the autofps adjustments.     I do think it's an su4 bug somewhere in the pipelin...  autofps is once again working great after discovering the toggle fix.    Your app really is amazing, thank you so much for the support and updates. 

I have found MSFS becomes a stuttery mess when turning FSR off, and I am pretty sure FG too, regardless of whether AutoFPS is running at the time or not. If you ever experience that again, I find it best to just quit MSFS and restart it and it is gone.

Hi and Merry Christmas 

 

May somebody please help me as i am getting wasm.error when running auto fps with msfs2024

5 hours ago, mikeymike said:

Hi and Merry Christmas 

 

May somebody please help me as i am getting wasm.error when running auto fps with msfs2024

Before you do anything further, please go here and attach your last three log files and let me know any further details about when it first happened, including what was different when it was last working properly, and what you've done to try an fix it (if anything). Thanks.

Edited December 26, 2025Dec 26 by Reset XPDR

46 minutes ago, Reset XPDR said:

Before you do anything further, please go here and attach your last three log files and let me know any further details about when it first happened, including what was different when it was last working properly, and what you've done to try an fix it (if anything). Thanks.

Hi sir,

Not at my pc ATM

Its my first time using it with 2024.

As i am merging from 2020.

Works fine with 2020 but when switched to 2024 in auto fps thats the error that pops up.

Thanks 

Mike

24 minutes ago, mikeymike said:

Hi sir,

Not at my pc ATM

Its my first time using it with 2024.

As i am merging from 2020.

Works fine with 2020 but when switched to 2024 in auto fps thats the error that pops up.

Thanks 

Mike

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?