Hi team, reporting a WASM crash on the A380 that has gone from rare to every single load.

Aircraft: iniBuilds A380 (v1.0.3)

Simulator: MSFS 2024 on Xbox (console)

Navdata: default Xbox (EFB navdata source not verified)

WASM error: "The WASM module has encountered a fatal error and stopped responding." Package: inibuilds-aircraft-a380, Module: inibuilds-A380.wasm, Gauge: DU. All display units go solid orange with the "WASM module crashed" message. On one occasion the new v1.0.3 crash diaog appeared instead. Automatic reporting was DISABLED and no manifest ID was recorded, so nothing was sent automatically.

Reproduction (100% — happens on every load):

1. Load the iniBuilds A380 at any airport — either a runway spawn or a cold & dark start at a gate/heavy parking.

2. The displays are already solid orange with the WASM crashed message before I can touch anything.

3. Even on a cold & dark start with every power switch in the OFF position, the screens still show orange with the WASM message.

Frequency: this used to happen on roughly 0.3% of loads. Since around Oct 8 (after the v1.0.3 update installed) it is 100% — every load, both runway and gate starts.

Notes: I am on Xbox so I cannot provide dev-console output, INI_CRASH LVARs, or the.bin autosave file — none of the PC verification steps apply on console. Happy to test any steps you suggest.

Update: clean reinstall did NOT fix it.

To rule out a corrupted download, I fully uninstalled the A380 from My Library, reinstalled it fresh (2.38 GB), fully quit MSFS 2024 on Xbox (not just dashboarded), and restarted. The WASM crash still happens on every load — identical error, inibuilds-A380.wasm, Gauge: DU, all displays orange before I can touch anything. Tested both a runway spawn and a cold & dark start at a gate.

So this is not a bad file on my end. It looks like a v1.0.3 regression on Xbox specifically — it went from ~0.3% of loads to 100% right after the update. Happy to test anything you suggest.

Has there been any official acknowledgment of this?

I’m presuming it’s completely unusable on Xbox for now.

I’m getting exactly the same issue on pc since installing 1.0.3 yesterday. Wasm on entry on all circumstances. Have cleared wasm folder but not tried a fresh install so doing that next

Edit: after three failed attempts at installing and a second wasm folder clear, it’s working, but the Heathrow loaded in with no terminal buildings just jetways and floating people. Next problem to solve

Edited yesterday at 11:49 AM1 day by richinspirit

Yep same with me. The initial release of it on Xbox was perfect but these new updates have practically dropped the performance of it on Xbox and you can not fly it anymore

Same here on PC. Exactly same symptoms and error message

On 10/10/2026 at 11:31 AM, HansOffHelmut said:

Has there been any official acknowledgment of this?

I’m presuming it’s completely unusable on Xbox for now.

Yes, it is completely unusable as it stands. As for an official acknowledgment by the IniBuilds Team? One guy on YouTube said that he attended the FSUK event. He met up with some IniBuilds Team member(s) and inquired about it. According to him, IniBuilds is aware of the A380 problem on Xbox and is working on a fix that will be available in an Update coming out in the next few days.

Edited 1 hour ago1 hr by ChristyKrohne