drepilot

I can confirm the same. Using both iniBuilds A380 and iniBuilds Manchester. I have no issues capturing with any other aircraft

Sorry about misleading you…yes, quite right, it doesn’t solve it😐

Just uninstall them and re-install via iniManager

Hey guys, I can now confirm that my WASM crashes were related to adding and/or tampering with the SEC F-PLN. I usually use it for EO procedures on departure. Whether mid-flight or close to the destination, whenever I modified the main flight plan or performed any action that required the FMS to recalculate data, the WASM module always crashed if the SEC F-PLN had been used. I am aware that the WASM module runs in a sandbox and you guys did your best to squash all these crashes, but this particular flight plan-related crash is quite annoying since it is still present in the A350 and now in the A380. I hope it gets fixed in a future update. Since Friday, I’ve flown the A380 for over 30 hours with zero WASM issues simply by leaving the SEC F-PLN untouched. I tested the aircraft thoroughly with last-minute arrival changes, holds, and DIR TOs via both the ND and MCDU, and it all ran completely smoothly. SIAI Issue Fix: For the SIAI issue, I managed to fix it by selecting a different CPDLC provider in the EFB, clearing the SIAI API key, closing the sim, re-opening it, re-inputting the key, and selecting SIAI as the provider again. I believe certain SIAI updates break the communication between the SIAI addon and the aircraft, but this reset fixes it.

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.

Thanks for the help!🙏🏻

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

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.

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. 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. 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. 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. 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. 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😂

Sometimes the LOC ident doesn’t autotune and that could be due to some scenery problems, nav updates or even sim updates. Cross check your NAV IDENT page in the KCCU as part of your approach briefing and make sure you have the LOC IDENT, frequency and course on the ILS field. If you don’t, then that’s why you can’t intercept the LOC. But the good news are that you can always insert the IDENT and it will automatically populate all the necessary fields (ILS frequency, course)

Most likely. I’m wondering if it behaves like the A350 in terms of updating. Like everytime you update, you need to clear up the WASM. I found the folder and emptied it and now I’m gonna give it a try and get back

Hello, I’m having quite a difficult time starting a flight in the A340. First of all, the GSX integration is not as smooth as it should be. I import the flight plan via the EFB, as well as the SimBrief Payload, yet, GSX seems to use some default values. For example: My planned fuel is 80.0, pax 252, but GSX imports 105.0 fuel, 237 pax everytime I use the automated menu. The second problem is the pushback. After the pushback, I get the “Landing Gear Malfunction” prompt in the sim and it’s very difficult to taxi with a broken landing gear. Also, “refuelg pnl” pops on the ECAM after every engine start, even though the boarding and refuelling are completed. The WASM crash when using a hold in the SEC F-PLAN still persists, but it only happens if I use a saved pilot waypoint. If I delete those before creating a new one there is no problem

Hey, first of all I wanna congratulate you for bringing this amazing machine to our sims. It’s amazing how great it performs with no visual quality drop. Honestly , I’m speechless. However, I wanna point out a quirk. It seems that it acts like the A330 used to back when the initial version of the MSFS2024 came out. And I want to pinpoint the exact same issue, and that is the WASM crash whenever editing the SEC F-PLAN page. I want to create an engine out procedure and whenever I’m trying to edit HOLDS for instance, the aircraft becomes unresponsive. Tried 3 times, the aircraft freezes at the exact same point. I also want to mention that I’ve tried this with FSLTL traffic injection on. It might have something to do with it, it might not, but regardless, the aircraft should be fully usable in parallel with tools like traffic injection. I know this is the 1.0 version and things like this are expected. I hope you guys will be able to reproduce it. I’m gonna try it without FSLTL and Volanta and if it keeps repeating, I guess I’ll just fly it without touching the SEC F-PLAN page. Anyway, thank you for bringing this beautiful, magnificent bird into our sims!😊