Aircraft became unresponsive...

[Julean]

FYI - The aircraft became unresponsive the moment I selected ILS .. No ILS visuals came..

The aircraft continued to fly and was responsive in rudder, elevator and ailerons but the hole flight deck became unresponsive.

And the ND display froze but not the PFD.

 

 

[richboy2307]

Hi @Julean

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. 

  

On 8/25/2024 at 5:21 AM, Julean said:

The aircraft became unresponsive the moment I selected ILS

This does sound like a type (b) crash as mentioned below. We have not experienced WASM crashes in testing caused by the ILS feature.  However, read of the information below and let us know if you are able to repeat the crash multiple times by doing the same thing.

----------

What is WASM? 

Quote

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. 

- Microsoft FAQ

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, please 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.

Thanks!