Hello, see screenshot

MSFS2020, A320neo V2

loaded after previously loading Fenix.

No OFP, wanted to manually insert LKPR-LLBG to test how ranged alt cstr are showed.

I think the freeze occured when clicking on GODED2 STAR.

WASM: Exception c0000005 in gauge FMGS in module vfs://microsoft-aircraft-a320neo/SimObjects/Airplanes/microsoft-aircraft-a320neo/panel/inibuilds-A320.wasm

51 minutes ago, Nikolaj Delaney said:

Hello, see screenshot

MSFS2020, A320neo V2

loaded after previously loading Fenix.

No OFP, wanted to manually insert LKPR-LLBG to test how ranged alt cstr are showed.

I think the freeze occured when clicking on GODED2 STAR.

WASM: Exception c0000005 in gauge FMGS in module vfs://microsoft-aircraft-a320neo/SimObjects/Airplanes/microsoft-aircraft-a320neo/panel/inibuilds-A320.wasm

Have sent onto the team, thank you for feedback

I experienced a very similar WASM crash in Microsoft Flight Simulator 2024 with the Microsoft/iniBuilds A320neo V2.

Platform: PC – Microsoft Store
Aircraft: Microsoft/iniBuilds A320neo V2
Flight: LSZH (Zurich) → LEPA (Palma de Mallorca)

In my case, the crash occurred after a go-around while reprogramming the FMGS/MCDU for a second approach.

Sequence immediately before the crash:

• Flying ILS Z RWY 24L into LEPA

• Go-around executed

• ATC instructed me to maintain 3,000 ft and cleared me toward MJV for another ILS Z RWY 24L approach

• After the go-around, the F-PLN showed MANUAL / F-PLN DISCONTINUITY / END OF F-PLN

• I entered and successfully inserted a Direct-To MJV

• I then started preparing/rebuilding the arrival/approach in the MCDU

• During this FMGS/MCDU reprogramming, the WASM module crashed

Both the PFD and ND simultaneously displayed:

WASM module crashed

Package:
microsoft-aircraft-a320neo

Module:
/SimObjects/Airplanes/microsoft-a320neo/attachments/inibuilds/Function_Interior/panel/inibuilds-A320.wasm

Affected gauges: PFD and ND

The aircraft itself remained in flight, but the loss of the primary flight displays made continuation of the flight impractical.

The timing may be relevant because the crash happened directly after a go-around and during FMGS arrival/approach reprogramming.

I have also reported this to Microsoft:

Microsoft Flight Simulator forum – existing bug-logged thread:
https://forums.flightsimulator.com/t/inibuilds-airbus-wasm-crash/737554

Microsoft Zendesk bug report: #284135

I can provide additional screenshots or test the same sequence again if that would help reproduce the issue.

14 minutes ago, Dreikosinus8289 said:

I experienced a very similar WASM crash in Microsoft Flight Simulator 2024 with the Microsoft/iniBuilds A320neo V2.

Platform: PC – Microsoft Store
Aircraft: Microsoft/iniBuilds A320neo V2
Flight: LSZH (Zurich) → LEPA (Palma de Mallorca)

In my case, the crash occurred after a go-around while reprogramming the FMGS/MCDU for a second approach.

Sequence immediately before the crash:

• Flying ILS Z RWY 24L into LEPA

• Go-around executed

• ATC instructed me to maintain 3,000 ft and cleared me toward MJV for another ILS Z RWY 24L approach

• After the go-around, the F-PLN showed MANUAL / F-PLN DISCONTINUITY / END OF F-PLN

• I entered and successfully inserted a Direct-To MJV

• I then started preparing/rebuilding the arrival/approach in the MCDU

• During this FMGS/MCDU reprogramming, the WASM module crashed

Both the PFD and ND simultaneously displayed:

WASM module crashed

Package:
microsoft-aircraft-a320neo

Module:
/SimObjects/Airplanes/microsoft-a320neo/attachments/inibuilds/Function_Interior/panel/inibuilds-A320.wasm

Affected gauges: PFD and ND

The aircraft itself remained in flight, but the loss of the primary flight displays made continuation of the flight impractical.

The timing may be relevant because the crash happened directly after a go-around and during FMGS arrival/approach reprogramming.

I have also reported this to Microsoft:

Microsoft Flight Simulator forum – existing bug-logged thread:
https://forums.flightsimulator.com/t/inibuilds-airbus-wasm-crash/737554

Microsoft Zendesk bug report: #284135

I can provide additional screenshots or test the same sequence again if that would help reproduce the issue.

Hi,

Sorry to hear you've experienced a WASM crash. I appreciate you taking the time to provide your feedback and submit the log/bug report to Microsoft through their forums.

We'll log this internally as well for the team to review.

Thanks!