Hartley

Same thing just happened this time KLAX to RJTT. Same exact issue, as soon as I landed and taxiied off of runway 22 in RJTT, wasm crashed. The good part about these crashes is at least I'm able to file the flight report with my VA before the crash finishes . Again, couldn't create an autosave so I used one already created and uploaded that instead. I've also attached the console picture. Again, you'll see it says 39 kts for ground speed but the aircraft is completely frozen and locked up. Also WASM folder was completely cleared from above when this occurred the second time. EDIT: I swapped from using Navigraph Navdata to Sim Default nav data when this wasm crash occurred also. Not sure if that's important. 1753296856.bin

Hello! I recently uninstalled the A350 and reinstalled when I heard about the 1.1.2 update to give her another shot. I had already cleared out the WASM folder prior to the reinstall. This was a clean install of the Inibuilds A350 and its first flight. I do not run any third party scenery at all, only what comes stock with Standard MSFS 2024. I landed at KLAX after coming from LFPG. While taxiing off the runway, the simulator froze. The plane would not move, and all gauges were stuck and the console reported a WASM crash. Pictures are attached. I attempted to do a .bin autosave but it would not save the airplane post-wasm crash. My last autosave prior to the wasm crash has been uploaded though. The second picture indicates a ground speed of 31 kts but the airplane was physically frozen and would not move. Simulator: MFS2024 Aircraft: A350-900 Navdata Method: Navigraph i7-13900k RTX 4070 RAM 32GB 1753281701.bin

I had the WASM crash on v1.1.1. The plane was not at all installed on MSFS 2020 when this update was released, so it was very fresh. I was using it on MSFS 2024 though and had held off on installing it on MSFS 2020 hoping that 2024 would work but it has not. The WASM crash occurred about 500 miles outside of Seattle, or about 8 and a half hours into this flight. When it crashed, I was specifically changing the runways, approach and the STAR prior to reaching them due to a runway change at the field. I have tried MSFS 2024, now MSFS 2020 and I can not use this plane in its current state. I can't wait to come back to it and I wish you all the best in getting everything squared away whenever this issue stops. Below is the error I got in the console. Thanks for all the help. WASM: Exception c000001d in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Simulator: MFS2020 Aircraft: A350-900 Navdata Method: Navigraph i7-13900k RTX 4070 RAM 32GB Route: RCTP/05L N0506F350 MOLK1C MOLKA M750 IMPAL Y755 CARDS DCT HIOTI DCT CBE Y121 SWING Y88 PIGAP/N0497F370 Y88 DAIGO Y889 OATIS R580 OPHET DCT PLADO/N0497F390 G215 CURVS DCT RADIC DCT 55N160W 56N150W DCT PHINK/N0489F410 DCT KATCH DCT YZT Q902 VIXOR MARNR8 KSEA/16L Let me add - you guys did a great job with this bird. She's beautiful, she's a joy to fly and I love her to death. I can't wait to get back in the cockpit whenever the issues are done. Thanks again for giving me the opportunity to fly what I already have, it was an absolute blast.