Hello everyone!

First of all I want to congratulate the iniBuilds team for such an achievement. The A380 is fantastic…from system depth, visuals, modelling, flight dynamics…it is a true piece of art.

I didn’t manage to enjoy the full journey on its maiden flight as I have encountered a WASM crash right throughout my descent but decided to be a little more productive (instead of throwing my PC out of the window😂) and offer some, hopefully, constructive feedback.

1. ND Direct-To WASM Crash: Attempting to execute a ⁠DIR-TO⁠ command using the cursor directly on the Navigation Display (ND) via the KCCU triggers a fatal WASM module exception, causing a complete system freeze and displaying an avionics BSOD.

2. Annunciator Light Test Rendering Glitch: Zooming the camera view out in the cockpit causes all overhead annunciator and push-button lights to fully illuminate (as if the ANN LT switch were set to TEST), likely triggered during interior LOD model transitions. It also happens intermittently when switching from an external view.

3. AOC / Datalink Weather Query Failure: SayIntentions AI fails to return METAR/TAF weather data via the ATC COMM menu or the OIS AOC interface—even though the data is actively received and displayed on the main EFB interface. The API keys are set up correctly in the EFB and I am 100% sure that SIAI is selected as the CPDLC provider.

4. Spontaneous Autopilot Disconnection: Unprovoked AP1 disengagements occur during cruise (likely caused by external weather injection or sudden wind/temperature shifts exceeding flight envelope limits). I am not entirely sure this is the culprit but it’s worth a look.

5. The aircraft just pauses mid-flight. Toggling the active pause ON and OFF seems to undo the sudden mid-air stop but I do not have a better idea about what it’s caused by.

I am aware this is the very first version and so far, I loved every single minute inside this aircraft. Looking forward to flying it every single day for an undetermined period of time😂

Edited Tuesday at 10:14 PM2 days by drepilot

Hi,

Thanks for your feedback. I'm sorry to hear about the WASM crash. We are monitoring all WASM related issues on our end.

Thanks again!

I'm also having problems with AP1. After takeoff, it disconnects and won't reconnect. AP2 is the only one that works.

3 hours ago, Miguelbor90 said:

I'm also having problems with AP1. After takeoff, it disconnects and won't reconnect. AP2 is the only one that works.

Hi,

I haven't seen any other reports of this behaviour. Please ensure you do not have any keybinds set that could be causing issues.

Thanks!

Hi,

I just the same issue with AP1. Is there logs/info we can provide that could helpful?
Best regards.

5 hours ago, Miguelbor90 said:

I'm also having problems with AP1. After takeoff, it disconnects and won't reconnect. AP2 is the only one that works.

I have no issue engaging it back. On my side, being a binding issue is highly unlikely because it happened during cruise, I didn't touch anything and I was briefly away from the PC, but when I returned, aircraft drifted off the NAV path. Also double checked my bindings and there aren’t any conflicts.

14 minutes ago, drepilot said:

I have no issue engaging it back. On my side, being a binding issue is highly unlikely because it happened during cruise, I didn't touch anything and I was briefly away from the PC, but when I returned, aircraft drifted off the NAV path. Also double checked my bindings and there aren’t any conflicts.

Are you using any 3rd party weather software?

2 minutes ago, iniKyle said:

Are you using any 3rd party weather software?

Yes, I am using ASFS. I think that might be the culprit as I experienced the same AP disconnection in the Fenix just today

2 minutes ago, drepilot said:

Yes, I am using ASFS. I think that might be the culprit as I experienced the same AP disconnection in the Fenix just today

Yes, I believe that is the issue. The sudden/abrupt weather updates are causing the AP to disconnect.

I will test this further on my end.

Thanks!

1 minute ago, iniKyle said:

Yes, I believe that is the issue. The sudden/abrupt weather updates are causing the AP to disconnect.

I will test this further on my end.

Thanks!

Thanks for the help!🙏🏻

I'd like to add, that if you activate the ARPT Button too many Airports are shown in the ND. Usually only bigger airports are and, forgive me the language, every cornfield airport around. Or am I wrong? Is it a setting?

Besides that and the other things mentioned it is a great plane worth the money! Great work!

Just adding another WASM crash report here.

Rather ironically, about 10 minutes earlier I had just told my friends that after 2–3 flights in the A380 I hadn't experienced a single WASM crash and that the aircraft had been very stable for me so far. Then I loaded another flight and got this almost immediately. 🙂

This happened shortly after loading the A380 at Warsaw (EPWA, Drzewiecki Design) in MSFS 2024. I was still on the ground and had barely started setting up the aircraft when the A380 WASM module crashed and all displays showed the red WASM crash message.

Unfortunately I closed the simulator before checking the Developer Console and INI_CRASH variables, so I don't have the complete diagnostic information for this occurrence. I have attached the screenshot showing the actual crash.

I was also running several external applications at the time, including FSLTL traffic, Cabby, FS-ATC-Chatter, Landing Rate Monitor and its traffic component, so I can't say whether any of these contributed to it.

I had completed my previous A380 flights without a WASM crash.

If it happens again, I won't close the simulator and I'll collect the Console error, INI_CRASH variables and the other information requested in the WASM reporting guide.

1 hour ago, pizzamonster said:

Just adding another WASM crash report here.

Rather ironically, about 10 minutes earlier I had just told my friends that after 2–3 flights in the A380 I hadn't experienced a single WASM crash and that the aircraft had been very stable for me so far. Then I loaded another flight and got this almost immediately. 🙂

This happened shortly after loading the A380 at Warsaw (EPWA, Drzewiecki Design) in MSFS 2024. I was still on the ground and had barely started setting up the aircraft when the A380 WASM module crashed and all displays showed the red WASM crash message.

Unfortunately I closed the simulator before checking the Developer Console and INI_CRASH variables, so I don't have the complete diagnostic information for this occurrence. I have attached the screenshot showing the actual crash.

I was also running several external applications at the time, including FSLTL traffic, Cabby, FS-ATC-Chatter, Landing Rate Monitor and its traffic component, so I can't say whether any of these contributed to it.

I had completed my previous A380 flights without a WASM crash.

If it happens again, I won't close the simulator and I'll collect the Console error, INI_CRASH variables and the other information requested in the WASM reporting guide.

I’ve just had another WASM crash last night when I got an arrival runway change and modified it accordingly in the F-PLAN. Can I ask you , when you encountered the crash, what specific action did you take that led to it? Also, did you use the SEC F-PLAN by any chance?

Asking these questions because these crashes seem to have the same triggers as the A350.

2 hours ago, moeliw said:

I'd like to add, that if you activate the ARPT Button too many Airports are shown in the ND. Usually only bigger airports are and, forgive me the language, every cornfield airport around. Or am I wrong? Is it a setting?

Besides that and the other things mentioned it is a great plane worth the money! Great work!

Hi,

This issue has already been logged and fixed by the team.

Thanks!

14 minutes ago, drepilot said:

I’ve just had another WASM crash last night when I got an arrival runway change and modified it accordingly in the F-PLAN. Can I ask you , when you encountered the crash, what specific action did you take that led to it? Also, did you use the SEC F-PLAN by any chance?

Asking these questions because these crashes seem to have the same triggers as the A350.

In my case, the crash happened very early during pre-flight, so it doesn't seem to match the arrival/runway-change scenario you described.

I had started the aircraft and GSX. GSX integration was disabled in the A380, and I started GSX separately through the Asobo tablet. I also had my usual external programs running, including FSLTL, FS-ATC-Chatter and CABBY.

I had imported the flight plan and completed the basic departure setup, including the FMC performance data, but I hadn't made any subsequent changes to the flight plan. I was simply waiting for GSX passenger boarding to finish when the WASM crash occurred.

I did not use the SEC F-PLAN at any point.

So unfortunately I can't identify a specific button press or F-PLAN modification that triggered it. In my case it appeared to happen spontaneously during the pre-flight/boarding stage.

24 minutes ago, iniKyle said:

Hi,

This issue has already been logged and fixed by the team.

Thanks!

Nice, are we getting an update today?