[FS2024] FSUIPC 7.5.4 WASM module crash

[hargn]

Hello,

There are many bug issues posted on the Self Loading Cargo support forum on their discord (https://www.selfloadingcargo.com/discord) related to bad integration with the Fenix A320 familly aircrafts.

Last time i encountered this issue, i checked for the FSUIPC's WASM module in FS2024's dev tools, and i saw it was in DIRTY mode. So according to FS2024 documentation, the module has crashed.

This issue seems to be frequent enough for quite a lot of people complain for these issue in SLC's support forum.

We also got another issue: according to SLC developper, some variables of the aircraft cannot be read, that prevent the integration of MECH/INT/PA call buttons to properly work. That another issue that the WASM module crash, but i also wanted to report that.

Thanks

[FPVSteve]

I just want to jump in here (as the Self-Loading Cargo developer) and say that I don't think this is a fault with FSUIPC at all, I think it's a fault with MSFS and have been quite clear about it on Discord. There are numerous times that I am able to have a completely trouble free experience (as are others). If there was an issue with FSUIPC this wouldn't be the case since the code doesn't change on each tune - and indeed the same code runs flawlessly on MSFS 2020.

Given the wider WASM related issues with MSFS (especially in 2024) I consider this an issue Asobo need to solve.

Having said that, if anybody is aware of how to mitigate the circumstances in which these issues occur and the fsuipc7 wasm module gets to a "dirty" state I'm all ears!

Edit - whoops, cross post with John. Thanks for the information John.

Edited 2 hours ago by FPVSteve
Post was made while I wrote mine.

[John Dowson]

The FSUIPC WASM crash is a known and ongoing issue and has been reported many times, and also seems to be more common in MSFS2024. This is related to the scanning for the new lvars which must be disabled - see the following FAQ entry: 

 

I have previously looked into this in detail and there are no memory issues in the WASM itself and I am at a loss as to what is causing this. I have also reported to Asobo but have received no response. However, I haven't checked this for quite a while now, and will look into it again at some point (when time permits).

If the current crash you are reporting is not related to the scanning for lvars, I will need to see your FSUIPC_WASM.log file, with Debug level logging enabled in the WASM. For all WASM crash reports you should attach this file. Note that, as a new forum member, your attachment limit will be very low. You should compress/zip the file, but if it is too large to attach you can deliver it via one of the free file transfer websites (e.g. https://filetransfer.io/)

John