richboy2307

Hi, I've included a screenshot of how its looking on my end. However, I did notice a similar issue as you when trying via Xbox Cloud.
MSFS on Xbox will sometimes disable certain objects and effects in order to save memory, so it may be what is happening in those instances there.
Thanks!

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:
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.
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!

Hi @Adrian Ramdeholl
Thanks for your suggestions.
The A320 Neo V2 "Enhanced" pack,  which adds the cabin among other things, is only available on PC due to performance reasons. Specifically, the RAM limitations on Xbox that unfortunately prevent the inclusion of a high quality cabin without causing excessive Avionics Black Out (ABO) issues.
Should that change, we'll be more than happy to make it available but until then it is not possible.
Thanks, your suggestion is noted.
While we would love to, as in the A300, ultimately this decision rests with Microsoft as it is their product. Since the functionality is dependent on third-party programs, it is not something that typically gets added to "default" sim aircraft, which the A320Neo V2 is. Again, should that change, we'll be more than happy to make it available but until then it is not possible.
Thanks!

Hi @ThibaudBenjaminVandenhoven, I notice your engines aren't running as yet. As the hydraulics are driven by the engines, can you check if it works fine *after* you have started your engines? What I see on your screenshots seems normal for an engine-off situation as the BGY (Blue,Green,Yellow) hydraulic systems aren't pressurized as yet.
However, in case you still notice an issue after starting the engines, can you please check your assistance options to ensure all the AI Assists under Piloting, as well as assists such as "autorudder" are disabled? They are known to have caused issues in the past.
Also if you're on PC, you can try to clear the contents of this folder below such that the plane will recompile all files "fresh" on next launch of the A300:
The location will vary depending on which version of MSFS you have:
Steam Version: MS Store Version: Thanks!

Hi @Patrick C.
The latest update to the A300 already has our new TERR RADAR incorporated into it. Read more here: 
 
It will also be making its way into the A320Neo with the upcoming Aircraft & Avionics Update 3 (AAU3) by Microsoft soon as showcased in the dev livestream yesterday:
https://www.twitch.tv/videos/2224195807?t=0h19m8s
 
Thanks!

Hi, thanks for the suggestion, will pass it along.

Please Calibrate your throttles in the EFB using the guide below:

Hi,

Thanks for your suggestion.
There are no custom GSE used, it just calls for the default sim Ground Service Vehicles using the buttons on the EFB. So you could call for such services using the in-gam ATC menu as well if you are not using 3rd party tools like GSX.
 
I'll check with the team if we could add a "Toggle Stairs" option as well. Thanks!