Hi all,

Upon updating the a380 to 1.0.3 and following these steps:

• Uninstall the plane

• Uninstall the liveries

• Go to free flight and select any plane that isn't the A380 (no need to then go into a flight or anything, but just have selected another plane and then clicked save & back)

• Go to settings > online > set rolling cache to 1GB (results in the game prompting you that it will clear the cache)

• Once done, reset the cache to your chosen amount (I've done 64GB - no science behind that choice)

• Install the plane

• Install the liveries

I now have instant WASM orange screens when loading into the sim.

I've tried exiting the game, power-cycling the xbox (including leaving unplugged for 2+minutes) and same behaviour...

Edit: have tried uninstalling the plane/liveries and tried to stream it, same result :(

Edited October 8Oct 8 by BourneY

Additional update, I cleared the reserved space within Manage MSFS2024 on the xbox, and same result.

Whereas the A350 appears to be fine.

I have the same problem after the A380 to 1.0.3 Update. I must add, though, that I STREAM only. Meaning I don't do the Download and Install process, as I want to save space on my Xbox Series X. Apparently, this is the best way for the IniBuilds A380 to operate smoothly.

This is what META AI is suggesting in order for me to resolve the Orange Screens problem. I haven't had time yet to test it;

META AI - range = ADIRS not aligned / no IRS data. The displays can't get attitude, so they go amber. Why you're getting it now (at FYWH especially): FYWH is high + sometimes you spawn with ADIRS switches in OFF because MSFS cold & dark is buggy. At low altitude airports you can get away with it longer, at FYWH it shows instantly.Quick fix, 30 seconds: Overhead — check the 3 ADIRS knobs (top left of overhead, above Captain)They must be on NAV — not OFFIf OFF, turn all 3 to NAVEFB — Instant AlignTablet > Aircraft > Settings / StatusHit ALIGN IRS or INSTANT ALIGN — FYWH takes 7+ minutes real align, so use instantIf still orange:Check BAT 1 + 2 are ONExternal power button on overhead — EXT PWR on? If not, turn on and click AVAIL light. Or just start APU: APU MASTER ON > START. Brightness knob — sometimes the screens are not orange, just dim. Under each PFD/ND there's a brightness knob — roll it to the middle. The order that works 100% at FYWH: BAT ON > EXT PWR ON > ADIRS 1-2-3 to NAV > EFB INSTANT ALIGN > Wait 10 sec > Screens turn blue/white. If you did ADIRS to NAV and it's STILL orange after 10 sec, do a full restart:

MCDU > EFB > Reset IRS > ADIRS OFF, then back to NAV.

I have the same issue as well, I uninstalled / reinstalled the plane, restarted the sim etc.

I highly doubt this has anything to do with the IRS. Metas AI has no clue what causes the WASM crash and it hallucinate anything which sounds like an answer but is just a bunch of probabilities piled together to a pile of nonsense

I’ve tried both streaming the aircraft and locally installed - same behaviour

I have encountered the same problem. Tried loading the aircraft at generic airports both downloaded and as streamed, and still get the same result. Have also tired resetting my cache and restarting both the sim and the console, no change.

Same on Xbox X Streamed or downloaded. Totally unusable today.

Same issue here as well it’s so frustrating.

Absolutely frustrating I’ve had problems since the day I purchased the aircraft, INIBUILDS please do something, this is constantly annoying!

Hello same for me since 1.0.3 Xbox

I'm experiencing the same issue on Xbox Series X with the iniBuilds A380 purchased through the MSFS 2024 Marketplace. After updating to version 1.0.3, the WASM module crashes immediately when loading the aircraft, and all cockpit displays turn orange.

The error message is:

• Package: inibuilds-aircraft-a380

• Module: /SimObjects/Airplanes/inibuilds-a380/common/panel/inibuilds-A380.wasm

• Gauge: DU

I've updated Microsoft Flight Simulator Add-on Support, restarted the console, and reinstalled the aircraft, but the issue persists. Could the development team investigate this Xbox-specific issue?

The same here. It seems it is only an Xbox problem after update 1.0.3. I don't understand why IniBuilds haven't said anything about this so far.

Could be that they’re at an expo so are tied up. Also I’ve heard anecdotally that apparently if you enrol in the SU7 beta that the issue isn’t present, which feels as though it could have been an Asobo issue rather than inibuilds, but they may not have enough info to say that out loud. Obviously that’s just me speculating

Hi everyone,

Very sorry for the delay in responding. Could you please try disabling and re-enabling the aircraft within the content manager.

Let me know if that helps solve the WASM issues.

Thanks!

Thankfully, and you'll hear this a million times - the SU7 update has resolved it :) Fired her up, no orange, happy days.

Question - I was under the impression the updated liveries had the RR logo on the QTS livery, but mine still doesn't. Will the new updates be pushed separately to market place?

45 minutes ago, BourneY said:

Thankfully, and you'll hear this a million times - the SU7 update has resolved it :) Fired her up, no orange, happy days.

Question - I was under the impression the updated liveries had the RR logo on the QTS livery, but mine still doesn't. Will the new updates be pushed separately to market place?

I'm happy to hear SU7 has resolved the issue!

I will double check with the team about the QTS livery.

Thanks!

7 hours ago, iniKyle said:

Salut tout le monde,

Veuillez nous excuser pour ce délai de réponse. Pourriez-vous essayer de désactiver puis de réactiver l'avion dans le gestionnaire de contenu ?

Dites-moi si cela permet de résoudre les problèmes liés à WASM.

Merci!

Hello, yes, I’ve already tried everything, but it’s not working. However, I see that it works for some people on SU7; personally, I’m not on the beta—I assume we should be able to get it working without having to switch to the beta, right? Thanks.

SU7 is being rolled out today. So no need to join a beta. Hopefully you’ll get the update soon (if you haven’t already) was a 3.7GB update for me. And then you should be fine