sirupflex Posted January 1 Posted January 1 Information Aircraft: A350-900, Standard Cabin, Ethiophian Airlines livery from inibuilds Manager Simulator: MSFS 2024 SU4 Navdata Method: NAVIGRAPH subscription Specs: Intel i7-12700K, RTX 3080 12GB, 64GB RAM, Windows 11 Other add-ons: BeyondATC (latest version), GSX Pro (latest version) Hardware: Winwing EFIS, FCU (via SimApp Pro), Thrustmaster Airbus Throttle/Joystick Autosave: Attached latest .BIN file before crash. Autosave file is from 15:07h. Crash was shortly after. The A350 was flying on FL410, there was no user input or any activity for minutes, I was just observing the flight, then suddenly many cockpit displays turned red, showing a WASM Crash message (see attached pictures). The error message on the red displays (see picture) says: WASM module crashed Package: inibuilds-aircraft-a350 Module: /SimObjects/Airplanes/A350/attachments/iniBuilds/Function/Interior_A350/panel/inibuilds-A350.wasm Gauge: EFIS I stopped MSFS 2024 after the WASM crash (probably ~2mins after the crash). It was not a CTD, I left the flight myself as it was obvious that the flight / A350 was gone. Then I realized I should restart MSFS 2024 to get to the console. In the dev console, no WASM Crash message was seen. The console messages visible on the screenshot came from starting MSFS 2024 again, it seems. Given the type of error and the error message on the red display, it obviously was a WASM Crash related to the EFIS module. I hope this report helps you finding the root cause of this issue. If there's anything I can do in addition, please let me know. Comment: Due to the constant crashes of the A350, this morning I deleted the A350 WASM folder following these instructions, just to make sure that there are no issues coming from outdated files in there. On one hand, I love the A350, but then again it is the one airplane in MSFS 2024 that nearly constantly crashes, since day one, and it only mildly improved during the past months. The MSFS stock A320 V2 runs very consistently, can't remember the last time I had a crash with the A320. Unfortunately, there is hardly any longer flight (more than 60-90mins) with the A350 that does not end with a crash, still. "Crash" does not mean CTD usually, but that the A350 or some functions of it get unresponsive and you have to abort the flight (I guess a behavior that people usually would qualify as "typical WASM crashes"). 1767276420.bin
sirupflex Posted January 1 Author Posted January 1 Oh, I realize I posted this in the MSFS 2020 section instead of the MSFS 2024 section. Please kindly move my posting to the right section. Thank you!
IniJamir Posted 11 hours ago Posted 11 hours ago Inibuilds A350 Master WASM Crash Thread v1.2.0 FS2020 This thread will be the new location for all WASM Crashes relating to the Inibuilds A350-900/1000 for Microsoft Flight Simulator 2020 Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A350. NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo. All WASM Crashes existing in this thread will be removed following the release of a new update. i.e. Any Crashes identified in Inibuilds A350 v1.2.0 will be removed from the post following the release of v1.x.x and so forth. Please ensure that when posting WASM crashes you post the WASM log from the in-game console alongside any media (photo/video) and a brief description of what you were doing leading up to the crash. Instructions on what to do are located in this thread - Thank you
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now