All Activity

Hi Pilota459 Thanks for jumping in. Yes, I've already gone through all the usual steps, plus several others I found mentioned across this forum: Full reinstall of the A350 (multiple times, both via Content Manager and clean manual install) Cleared the WASM cache folders (wasm and wasmFolder under both LocalCache and the rolling cache location for MSFS 2024) Started MSFS with a completely empty Community folder only the A350 present, no other add-ons loaded. Crash still happens. Rebuilt the rolling cache and disabled it entirely as a separate test Verified file integrity through the Content Manager Reinstalled Navigraph data and also tested with no Navigraph data at all Tested different liveries, including the default one, to rule out a livery-specific issue Disabled all developer-mode options and any third-party tools that hook into SimConnect/WASM (FSUIPC, GSX) Tried different airports and short flights (including very simple cold & dark starts at default airports). crash still occurs within ~10 minutes Updated GPU drivers and verified MSFS 2024 itself is fully up to date Reviewed MSFS.log around the time of the crash, the only relevant entries point to the inibuilds-A350.wasm module failing in the MFD gauge Kind Regards,

Yes, I have it through the default sim marketplace. I will try to uninstall and re-install the aircraft and see if that works. Thanks🙏

Hi, That sounds really weird. You've said you attempted a couple different steps to trouble step the aircraft. Do you have the aircraft on the IniManager or through the Marketplace in Sim? Have you tried uninstalling and reinstalling as this sounds like a corruption issue which usually occurs during the install process. Let me know, thanks.

What have you tried so far? Reinstall, cleared WASM folders, startign with empty Community folder etc.?

Hi iniBuilds team, I'm writing to report a critical, ongoing issue with the iniBuilds A350 in MSFS 2024 that has made the aircraft completely unusable for me for over four months now. The problem: All MFDs crash with a "WASM module crashed" error, every single flight. It happens consistently within the first 10 minutes of the session — sometimes during taxi, sometimes shortly after takeoff — and once it occurs, the entire cockpit is unusable (see attached screenshots). Error details from the screen: Package: inibuilds-aircraft-a350 Module: /SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm Gauge: MFD Topics: The latest update made things worse. Before the most recent patch the crashes were already frequent, but now they are happening even faster and more reliably. This is isolated to the A350. I fly other complex add-ons (including the Fenix A320, PMDG 777) on the same system, on the same flights, with the same scenery and add-on environment and none of them have this issue. It has been more than 4 months. I purchased this aircraft and have not been able to complete a single normal flight in it for that entire period. That's extremely frustrating, especially given how prominently this aircraft is marketed. Could you please confirm whether this MFD WASM crash is a known issue currently being tracked? Is there any workaround, beta build, or rollback I can try in the meantime? If a fix is in progress, do you have any indication of a timeframe? I really want to enjoy this aircraft — that's why I bought it — but at the moment it is simply not flyable. I would appreciate any response. Happy to provide MSFS version, system specs, full add-on list, or log files if that helps your team reproduce or diagnose the crash.

If they can’t successfully make a stable cabin on the 350 i dont see why they will be able to on the 380.

Hi, These issues are known to the team and being investigated. Thank you all :)

I shall pass this along to the team, thank you :)

Hi, another user raised this on the discord as well and the team is aware of the changes. No ETA for when these changes can make it into the sim however. Thank you :)

Hi, Lately I’ve been trying to do regional flights in my Airbus A300-600 and when I load into a ramp I can load my cargo etc. But when I push back and start my engines my fuel which was originally at 70%, which is what I set it to before I loaded into the flight instantly goes straight to 11% fuel which can hardly get me a few NM out of the airport. I have tried many solutions to attempt to fix this problem but none of them have seemed to work. Any suggestions?

Actually, in this last case, the fuel truck never showed up, so I had to use the instant fuel load option.

Started a new flight just now and confirmed - after choosing "Import all from Simbrief" and then "Load with GSX", the GSX menu still wants me to manually request refueling, even though that option is set to Auto in the EFB. And even after that, it takes forever for the fuel truck to show up.

Those are awesome news. Why not release that fix you have and we can help with testing? Thanks in advance.

Hello. We are working on a code update to release soon (actually soon, not "dev speak", you'll get it in 6 months, soon) Good news is we have been trying to reproduce the reported WASM crashes with approaches with little success. We speculate the main issue causing these is outdated/bad nav data. In over 40 attempts in the last 24 hours we've had exactly 0 crashes when spamming approaches including all these ones called out here with the latest sim default and Navigraph replacement datasets. While I wont say it's outright fixed, I will say the results are promising.

I know a lot of focus has been on msfs2024 however my current computer specs aren't ideal for running 24 hence I'm still operating on msfs2020. I enjoy flying the inibuilds a320. Is there or will there ever be a version either paid or freeware of inibuilds a321neo for msfs2020?

This would be useful yes, along with exactly the airport at which you tried and with what approach. Normally if you're in ALT mode already, arming LOC then ILS should properly set the aircraft up for a GS intercept from below.

Just had the same thing - Didn't realise there was such a thing as a "Ghost WASM Crash" but this is exactly what I just encoutered. I haven't touched the A350 in months and after two from four flights ended in this Ghost Crash I'm going to park the A350 back in the hanger and stick with aircraft that don't suffer the issue, i.e Fenix and PMDG.

Add me to the list of unhappy customers with the same issue. A 15 hour flight from KLAX to VHHH and at TOD the aircraft just stops responding. Dials spin, buttons press but nothing happens. The sim continues to run just fine but nothing out of the aircraft. WHat a complete bucket of junk.

I have an odd problem that I don't Understand. I can create a flight in Simbrief from EGCC to EIDW for example. I load up beyond ATC and whichever Aircraft I try, I just cannot get the option to request IFR clearance. I can select clearance from the options in BeyondATC and request IFR clearance pops up and disappears. This also happens in the sim ATC, no option to tune in to get clearance. I can pop across country to Liverpool or down to Luton and everything works fine. It's just Manchester. Any help/suggestions or advice would be greatly appreciated

Update: I now understand what triggered this situation. There was some turbulence and the AP switched off, I manually brought the plane back on its lateral and especially its vertical trajectory, it had lost around 1000-1200 feet. I presume that had put it in DES mode - at least when I checked the PERF page it showed DES in green. Which then probably also explains why the TOD no longer showed. I fixed that by setting a higher cruise altitude, the plane went back into CRZ mode and the TOD shows again. Still, the time calculations shouldn’t show what they showed. There is no way a plane can just jump back one hour or more. In fact, as I flew further (still in DES mode, without knowing) the ETA was pushed out further, but still with that “time jump” in the FPL. That looks like a bug.

Flight LFPG-SKBO. All well, ETA at 21h18 UTC. Then suddenly over the Caribbean, things become funny. Arrival more than one hour earlier, which isn't possible given the distance. On FPL I see the following times. Also, the TOD point between KIKAS and DOPLO has disappeared, although the correct lower altitides show. I haven't palyed with anything in time display, it's all UTC.

I think I found a way without uninstalling. I just reset the Navigraph credentials for the plane and made a test flight. Seems to have worked. The only downside with that is that I have to use the LIDO charts and the enroute maps don't work. So far, no crash, but let's not be too optimistic. This is definitely just a workaround. This is not a fix. What is the hold up for a fix in this plane? Honestly this is ongoing for too long. At some point, however, it's not even about the time it's taking for you to realise the above. It's the silence around the users complaining about the lack of a fix. Please understand this frustration as a desire to get our money worth. I purchased this plane, I wasn't given when it was launched, made a video/stream and forgot about it. I was invested in using this plane for my livestreams. I still am... as long as you release that fix...

Does anyone know

As the title says, when parking at A1R, the jetways are non-functional and cannot be operated with GSX.

Hello, The last update for the London Luton scenery was released on 10 July 2025. Since then, several significant airfield changes have entered service which are currently not represented in the scenery. The most notable omission is the Taxiway Alpha Extension project, which introduced a new taxiway configuration at the Runway 25 end. The real airport now features an extended Taxiway A layout designed to improve aircraft flow and reduce congestion around the runway access points. Changes currently missing or requiring updating include: Taxiway Alpha Extension at the RWY 25 end. New and relocated stopbars. Updated taxiway signage, particularly along Taxiway Alpha between A2 and A6. Updated centreline lighting and lead-on/lead-off lighting arrangements. Taxiway edge lighting changes introduced during the project. Runway lighting upgrades completed during the 2025–2026 resurfacing programme. Various ground markings associated with the revised taxiway infrastructure. Thank you for considering an update.