planedriver95

As per the WASM crash FAQ, here are the details requested: Aircraft: A350-1000 inibuilds Etihad livery A6-XWB Simulator: MSFS2024 Navdata Method: NAVIGRAPH Console messages: WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty Specs: CPU: AMD Ryzen 5 5600x GPU: nVidia RTX3060 12GB RAM: 32GB (2x 16GB) DDR4 3600MT/s CL18 Unfortunately I didn't take any screenshots or videos of the event. As described in my OP, I was initially trying to insert an ALTN route. I had a few short freezes as I kept trying to force the software to comply. At some point I tried to activate the route to alternate by selecting a point in the ALTN section of the FPLN. The result was that the active FPLN was erased. I had the flight plan copied to SEC 1. When trying to activate it, the crash happened and the airplane froze.

To add to this topic, I noticed that if you are browsing the FPLN page on both MCDUs, pressing a button on either side will affect both CDUs. This doesn't seem to be realistic behavior, as they should be independent.

OPTIONS only seems to appear on the left OIS, for some reason. Unable to access it from the right seat unless VIEW OFFSIDE is selected. I you are on the left seat but VIEW OFFSIDE is selected there, then you won't be able to see it as you'll be seeing the right OIS. Any intentions from devs to fix this?

Hello! I was jus in trying to do my second flight on the A350 when this happened. From previous posts, it seem to be related to WASM crashing. I was trying to input a route to the alternate flight plan while enroute, but to my surprise this function in the FMS doesn't seem to behave correctly, since it does not allow for any entry on the ALTN route and any waypoint that I tried to insert got placed as next active waypoint. After a lot of trial and error, I somehow managed to get the whole active flight plan erased. I had a copy of it on SEC 1, but when I tried to swap it to active the whole cockpit froze. No systems or buttons worked, but the simulator kept running. Was flying on MSFS2024. I bought the product after the 1.0.4 update and did one flight successfully.

Same here. Indeed I got the whole airplane to freeze while attempting to enter the ALTN flight plan.

I am also unable to enter the ALTN flight plan. Indeed I just managed to cause the airplane to freeze in flight while attempting to work around it. My flight plan got erased as I tried to input the ALTN route and, while trying to swap SEC 1 (which had a copy of the original FPLN) to active, the whole flight deck froze, but the airplane kept flying. I had to restart the flight.

Same here, unable to make inputs with physical keyboard on the RH CDU.

Sorry for bringing up an old topic, but I thought it would be better than starting a new one about the same subject. I'd just like to echo the OPs observations here and say that the spool up time is something that would be very appreciated if you could fix. Indeed the engines are spooling up too quickly, which is unrealistic for any jet engine, let alone an older design like the CF6. It's a small detail that would improve immersion by a large margin.