Both mcdu freeze

[ThibaudBenjaminVandenhoven]

it's not the first time that's happened to me but i need to know why, the both mcdu have frozen, i can't enter any more information or even change page... everytime that i forget and configure the flight plan for the alternate airport in the main flight plan instead of the second one, the both mcdu frozen complely. am I really obliged to restart... I promise I won't bother you again after that. 

Edited August 23 by ThibaudBenjaminVandenhoven

[ThibaudBenjaminVandenhoven]

i just realise that the Engines and Apu fire extinguisher donsn't work too... the transponder&radio also and the Ecam, some thnigs work but many others not

[ThibaudBenjaminVandenhoven]

my edit crash, i was saying everything freeze except buttons, and views

[richboy2307]

Hi @ThibaudBenjaminVandenhoven

This is an instance of a 'WASM Crash'. When that crashes, any systems that rely on this 'container' to execute code will also equally stop responding. The sim itself will continue to work, but parts of the plane that depend on WASM will fail. 

Below is information from Microsoft's own FAQ:

Quote

What is WASM? 

WASM is an acronym for WebAssembly Module, and Microsoft Flight Simulator uses WebAssembly for scripting. Most commonly this means aircraft instruments, such as controls, panels, and displays, will function as intended (without WASM these instruments may not function at all or would function incorrectly). However, WASM usage is not only limited to aircraft.

Why do WASM Crashes happen?

These can be caused by either a) faults in the code, or b) in the way that code is executed by the sim.

a) Faults in Code

While we try our best to find and quash all bugs in code, we are still human. Mistakes or oversights can happen and sometimes these can lead the code to fail in certain specific instances, resulting in a WASM crash. These kind of crashes will be reliably reproducible, meaning you can have the crash nearly every time by executing the same code (e.g. by selecting something on the MCDU, or by pressing certain buttons on the plane, or by flying certain SID/STAR/APPROACH etc.)

These types of WASM crashes are actionable, and dependent on your reports of the steps taken immediately before the crash happened. These, if reproducible on our end by following the same steps, can be debugged and usually resolved in a following update.

b) Faults in the way the code is executed by the sim

Since SU15, we suspect, there have been instances of "random" WASM Crashes caused by a "memory allocation bug", wherein the sim tries to reserve memory (for WASM) that it does not have access to, as a result leading to a WASM crash. These types of WASM crashes are difficult to reproduce and not something we can address as its not an issue with the code, rather just in the way the sim tries to store and execute it in some instances.

These types of WASM crashes are also in-actionable on our part and would instead need fixes on the simulator's code (if possible0.

So why did you experience a WASM Crash?

As mentioned above, we will first need to find out if the crash was (a) or (b). So you need to take note of what you pressed or things you did, just before you noticed this crash happen.

What systems stop responding, or what you cannot click after the crash is irrelevant as the whole WASM has already crashed, so anything using WASM will equally stop responding.

Additionally, you need to see if you are able to repeat the crash by following those same steps. Once you know, you can mention those steps to us, and we can try to reproduce on our end to see if its actionable.

20 hours ago, ThibaudBenjaminVandenhoven said:

configure the flight plan for the alternate airport in the main flight plan instead of the second one, the both mcdu frozen complely

I think in your case, are you trying to enter information for the ALTN flight plan? If so, when are you noticing the crash? When you try to enter a STAR/APPROACH? More information will help.

Thanks!

[ThibaudBenjaminVandenhoven]

i had make a explicative video but, is too big to be send, so yeah basically that's it, i accidentally put the sec flight plan in the end of the main flight plan, as a suite of the flight plan, i know is no import but here's all my information on my flight... and i replaced the point "LA" by "AGO" and remove the point "NZ" cause it was not like in my flight plan... i thinks also that it's the option B

Edited August 26 by ThibaudBenjaminVandenhoven

[ThibaudBenjaminVandenhoven]

i mean option A sorry has you said for me it's all because the game is like to internet

Edited August 26 by ThibaudBenjaminVandenhoven
be more acurate

[ThibaudBenjaminVandenhoven]

"i accidentally put the sec flight plan in the end of the main flight plan, as a suite of the flight plan" WARNING the video lags a little at the end

Edited August 26 by ThibaudBenjaminVandenhoven
forgot something

[richboy2307]

14 hours ago, ThibaudBenjaminVandenhoven said:

"i accidentally put the sec flight plan in the end of the main flight plan, as a suite of the flight plan" WARNING the video lags a little at the end

Ok, I was able to reproduce the issue by following the steps taken in your video.
It is indeed a type (a) WASM crash and we'll look into it.

For now, avoid using the ALTN airport section of the F-PLN. Instead add the ALTN flight route to your SEC F-PLN instead.
Thanks for the report!