Wasm crash report.

[Donforcefeedback]

Hi,

Had a wasm crash usually when I'm about to land at an airport. Specifically around turning off AP1 (autopilot) before landing.

Unfortunately I don't have a video, but it seems to happen when trying to disengage the autopilot around the decision altitude above the runway. Aircraft is fully set for landing (gear down, max flaps, autobrake set to medium, brake fan on, armed spoilers, land selected on the MCP) I was aware of the same crash when disengaging the autopilot yesterday so turned off ap2 first, still fine (switch moved), then tried to turn off ap1 however the switch didn't move, but i could use the joystick to fly the plane onto the runway. Throttles were fixed into position so had to manual brake and pull off runway with around 40/50% thrust. I did have control of the throttles beforehand as I had disengaged the auto throttles 10 seconds before i went to turn off the autopilot.

Outside of physical joystick control (no cockpit or model animation) i also had rudder brakes and parking brake control. Flaps, spoilers and all buttons became pretty much unresponsive (though when clicking on the parking brake, that could engage and release despite no cockpit animation happening).

I believe in my flight yesterday it happened again when coming into land despite flying into a different airport. Yesterday i flew EGSS to EGPH and today flew EGPH to BIKF. Both have payware scenery.

• Aircraft: A300-600 Premium
• Simulator: FS2024
• WASM Error: WASM: Error during Systems_gauge_update execution. Error code : 0xc0000005
• Specs:  CPU: AMD Ryzen 7 9800X3d, GPU: AMD Radeon RX 9070 XT (XFX SWIFT), RAM: 96gb DDR5 6000mhz (cl30)

[Eddie]

Hello,

Very sorry to hear that you've experienced a WASM crash. While this is not a guaranteed, please clear your WASM folders just incase: 

 

I'll forward this to the team. Thank you 🙂 

[Donforcefeedback]

Thank you for replying,

I have cleared the WASM folder and had no issues when retrying the EGLL to EGPH route, the only other difference is that I realised after landing today is that I used the PW cargo model and not retried the GE cargo model where I had the issues. 

I'll give it another try tomorrow with the GE variant but hopefully clearing the WASM folder has fixed things. If WASM affects both aircraft engine variants equally then this could be a good sign. I'll give a quick update later this week after more testing just to be sure.

Many thanks again!

[Donforcefeedback]

I've been retrying flights when I can this week, and have found that out of the two freighters, the GE engine variant has had the same issue every time even after clearing the wasm folder. the PW variant has had two flights and seems ok still. (GE has had around 4 flights).

I have not checked the passenger variants. 

All flights are full EGLL to EGPH flying empty.

 

EDIT: Just to add i did the GE passenger variant and the same error comes up:

 

The only difference is that instead of turning on both autopilots then having it fail when switching off, I had forgotten to turn on ap2 before landing and went to switch it on and the error occurred then, all errors come at a point in the landing when I turn off auto throttle first before the autopilot a few moments later. (after 500ft call I turn off auto throttle, around 200 I turn off autopilot)

I am unsure if its because I had the auto throttle off that causes the error to be repeatable or not but that's the only similarity I can see so far, especially as this is the first time it crashed when trying to add in ap2 having not touched the ap1 switch where the error normally occurs:


It could all be for nothing but I just wanted to provide what I can to hopefully pin down what could be wrong or to help in some way.

Thanks again.

Edited yesterday at 08:18 PM by Donforcefeedback
more info

[Donforcefeedback]

Sorry to bump again, but I've flown all the variants of the premium a300 and found that this wasm crash happens on the GE variants of both passenger and cargo aircraft whereas the PW variants are all fine.