All Activity

Hello, I am also experiencing this issue. The program is doing something, but ultimately never loads Started yesterday. WORKAROUND: Connected to a uk VPN (nordvpn) and program runs instantly.

Same issue here as well it’s so frustrating.

This is how it is at Inibuilds airports currently with multi jetways implemented. All jetways, single or multi, must now be controlled using the multi jetway tool which of course won't work on Xbox. I think this 'change' is a very strange one by Inibuilds..

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

Tenho o mesmo problema

The new A380 v1.0.3 update on Xbox has caused the aircraft’s systems to stop working properly. I have already restarted the simulator several times, completely uninstalled and reinstalled the aircraft, cleared the cache, and the issue still persists. The aircraft is now completely unusable. The OIS is also not responding and remains with the screen turned off all the time. I have tested the aircraft at several different airports and under various conditions, but the aircraft’s panels and systems still do not work. The panels remain red and display the error message “WASM Module Fatal Error.” This issue started after the v1.0.3 update. Before the update, everything was working normally. Please investigate this issue, as the aircraft is currently unusable on Xbox.

I've also had this on the last couple of flights. if you adjust the brighness of the OIS screen "knob just above speaker to the right of the OIS screen" it'll come back. but it'll be gone again next time you load so it does need to be added to the bug list.

Maybe it's one of the controls (hardware) that's causing the issue? I had the same long time ago for another add-on. Perhaps, try clearing out the control inputs and only add the primary inputs that are necessary and see if that works. I'm though aware of FBW flying flawless with your current setup and presets/assignments.

Still have this kind of issue in the latest V1.03 . After I updated it to Airrac 2609 i cannot update ist to 2610, i tried to logout/login and also to move it from community1 folder to the new community folder. Nothing works

Hello, When powering up the cockpit, all the screens light up except for the OIS screen, which remains black—even though it was working during the previous flight. Thanks in advance.

The normal one as well

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.

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

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

Hi! I'm having the same issue, MSFS2024, A380 and yes running same AIRAC and NAVDATA

Hi Inibuilds, after the update to version 1.03 I have orange screen (WASM crashes) in every single try to start a flight in cold and dark (I tried multiple liveries at multiple airports). The plane is not usable at all right now. It went from okay performance (1.0) to bad performance (1.01 - much more memory induced black screens then before) to no performance at all. Honestly, how is this even possible to miss such a critical issue? Did you test the version not even once on a real Xbox before pushing out the update? This needs to be addressed and fixed ASAP.

yes, see my response to Kyle

Just had the time to try again with an autosave, double checked that pause at TOD was enabled, same deal, straight past TOD and ended up circling the destination at FL400. Flightplan is WSSS/02L AROSO3E AROSO Y513 KALIL Y501 RINBA Y503 VPL P628 RK G202 ZB L750 RANAH B449 ETRAP B447 KRS B143 TUNEK A909 RODAR M11 REBLO UM11 CRM UL746 ODERO DCT OPT DCT SOKRU DCT BEGLA DCT DEXIT DCT INBED DCT BOMBI DCT ADKUV DCT SOGRI DCT DENUT L608 LOGAN LOGAN2H EGLL/27L and I added waypoint RICHY after LAM to setup the approach to 27L, no disco's

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 tried everything that were suggested...adjusted turbulence to low, unbind autopilot keys, no live weather, increase sensitivities of flight stick to 5%, no auto rudder and other stick controls etc.....nothing works. Seems these intermittent autopilot disengage happens on every flight but with varying frequencies...the most frustrating thing about flying the aircraft. I am at wit's end as to how to neutralise this very frequent autopilot dis-engaging. One factor that would make me give up on flying this aircraft. Starting to regret on my purchase of the Inibuilds A380. The free FBW A380 flies flawlessly.

Just curious if there has been any news on this? Will we possibly see a fix in 1.0.4?

OMDB- ZBAA EA engines. At FL410 the FMS is commanding .85, but the airplane is flying at .861 in managed mode. Cost Index is 200 I had to insert 150 for CI to make it Fly .85 . I dont think this is correct.

As stated in the question, the lack of clear contrast between PFD and FD has caused significant inconvenience, and it is hoped that adjustments can be made as soon as possible

Hi Kyle, These issues were not fixed in patch v1.0.3.

Hi ive recently experienced a WASM crash on the a380 and tried everything from clearing reserve data to disabling traffic. I was hoping to get a working method here