All Activity

I've switched to in-sim navdata and I can fly for longer periods without WASM crash.

I let the plane climb to cruising altitude and leave. I come back and the plane is at cruising altitude but on the verge of stalling from low airspeed. The attached video is after I descended a bit to claw back some speed but it does not want to climb back up even with TOGA thrust. vlc-record-2025-07-04-21h43m01s-2025-07-04 21-40-41.mp4-.mp4

same here on SIA ULR

Same here. And all cockpit functionalities freeze until the episode is over. https://imgur.com/a/bq9z9H8

Hi there, I am currently experiencing the same issue, meaning that it hasn't been solved in the meantime. I checked the Navigraph forum and it seems that the issue was reported there as well: https://forum.navigraph.com/t/navdata-problem-in-defult-airplane-in-msfs2024/20002 As it seems, the guys at Navigraph have concluded that the problem relates to the A320neo V2 using the "old WT framework" - I am not sure whether the other default aircraft such as A310, A321 and A330 are also affected by this. Since the FMC is messing up almost every SID or STAR I load in, needing painstaking manuel editing which then again seems to destroy things like T/D calculation, I would really appreciate a fix for this. Is there any effort underway?

I am with you on this (and somehow this topic was used for all IniBuilds MCDU topics - I think.

Hello, I have something strange happening, it looks like it started after a recent Steam update. I'm using MSFS 2020 and had only installed the A350-900 for the 2020 version, but the A350 for 2024 keeps installing itself automatically. When I delete it, the A350 no longer appears in the aircraft selection menu. On top of that, after uninstalling and reinstalling it, the electrical power only works every other time.

Hi iniBuilds Support Team, My name is Elijah. I recently purchased your Airbus A350 after experiencing it at Flight Sim Expo and was truly impressed with its level of detail and immersion. However, since installation, I’ve been unable to operate the aircraft successfully in Microsoft Flight Simulator 2024. Despite repeated attempts and extensive troubleshooting, the A350 always loads in a cold-and-dark state, and I’m unable to activate any systems. Below are the full details to assist your technical team in diagnosing the issue. ISSUE DESCRIPTION Aircraft loads with no power, regardless of starting at gate or runway. Battery switches do not activate any systems. All cockpit displays (including MCDUs) remain off. No throttle response via mouse or hardware. Engines do not spool, even when loading "ready on runway." This occurs at all airports tested. 🔧 TROUBLESHOOTING STEPS ALREADY TAKEN Reinstalled the aircraft 3+ times via the iniBuilds Installer. Deleted all residual files in: Community folder WASM folder (MSFS2024) Installed A350 into an empty Community folder (only aircraft installed). Verified Microsoft Flight Simulator was cleanly reinstalled 2 weeks ago. Tested both gate and runway spawns — same cold-and-dark issue with no response. NVIDIA GPU drivers updated (latest Game Ready drivers). Windows and Xbox App updated. Confirmed other payware aircraft (e.g., PMDG 737, Fenix A320) are fully operational. Developer Mode checked in MSFS — no visible errors related to the aircraft. WASM modules are enabled. INSTALLATION DETAILS Microsoft Flight Simulator Version: 1.4.20.0 (Microsoft Store/Xbox App version) Install Path (Community Folder): D:\WpSystem\S-1-5-21-2522608883-2117060061-7209756-1002\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community WASM Path: D:\WpSystem\S-1-5-21-2522608883-2117060061-7209756-1002\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024 SYSTEM SPECS OS: Windows 11 Pro Version: 24H2 Build: 26100.4484 CPU: Intel Core i9-13900K GPU: NVIDIA RTX 4080 (Driver: Latest Game Ready) RAM: 96GB DDR5 Motherboard: ASUS ROG Strix Z790-E Gaming WiFi II Storage: 2TB Corsair MP700 Pro Gen5 NVMe SSD (MSFS installed on D:) Monitor: 27” G-SYNC 240Hz QHD Display Additional Notes Virtualization is enabled in BIOS. DirectX 12 is selected within MSFS. No third-party utilities (e.g., SimBridge, GSX) were active during testing. I appreciate your time and hope to reso lve this soon — I’m very eager to fly this aircraft. Thank you again for the care and detail your team puts into every release. Warm regards, Elijah

As we know, the second and third columns of the FMA indicate the currently engaged or armed vertical and lateral guidance modes. These indications should remain visible as long as either the autopilot (AP) or flight director (FD) is active. However, in the iniBuilds A350, the vertical and lateral guidance modes disappear from the FMA when the FD is turned off—even if the AP remains engaged. As a result, there is no way to know how the autopilot is attempting to fly the aircraft, as if it's in some kind of "God-knows-what" mode. This behavior is clearly incorrect.

Fix the approach lights. They are made incorrectly. According to the diagrams Jeppesen, all runways should have CALVERT2, and here ALSF2. I'm surprised the developers missed it.

While everyone here was super helpful with - I know people who fly the plane and its normal - and always land manually- none of that is correct - fact - its FsRealstic causing the issue. Your welcome Inibulids - solved a similar problem with Captain SIm and Rex a decade ago - they gave me the next plane for free. Just saying.

Finger crossed they won't go that route... this is by far the single most expensive purchase for flight sim but I really loved the A350 being one of the longest plane flying. but then the issues plagued since day 1 is so frustrating...

Is it correct only 161 passengers max?

That's a good sign and would enhance the immersion quite further in the cockpit. 🙂

I just want to report that maybe the error was caused by a tool i use to deactivate some screens on the plane in order to save GPU as is limited, the tool is called Taboo, i use with 777 PMDG and 787 Bravo as well and of course with A320 Ini and never have had a problem before, i just set on all the screens again and now is working. In case this can help other with the same problem, my version in MSFS 2020.

I has had the same problem and found that was caused by a tool i used called Taboo to deactivate some screens that i don't use on the plane, I mean i don't know if that was, but I just reactivated all the screens and now plane is working.

Same problem here on MSFS 2020 since last update with all 3 variants, inop.

Is this what you want?

Had the update, but the floating object on 34L is still there, deleted the scenery and reinstalled also deleted everything in the scenery index folder, but it still shows the floating objects on the runway.

So, from my perspective, it would be better to revert to the original version, as at least that looked realistic.

Same issue since 1.1.0

To be honest, I started to lose confidence. I was very worried that in terms of aircraft add-on creation ini would end up being another AxxxxxxT.

Every time i want to use, this how the plane load every single time after last update, how i can delete that version go back ? PLEASE HELP!