All Activity

I am not even able to start a flight, most of the flights the plane spawns direct with a crash.

Also when loading in, Pitch Trim 1 & 2, Yaw Damper 1 & 2, and ATS 1 & 2 are already switched on. Turning on all three Battery switches does nothing.

Looking forward to the update. Trying to do a very soft landing with the collective as it is at the moment is really tough.

Did 4 long haul flight this weekend and every flight had a crash. Have all the updates installed. Latest crash is when I was entering the arrival for Munich. A350-900 MSFS2024 NAVIGRAPH Intel i7-14700K 32GB DDR5 RTX 5060

I think it may be probably related to data between msfs and navigraph. Most reports i seen are using navigraph. And I also encounter the first time WASM crash after I subscribing navigraph and using it as navadata method. Before subscription, I never encounter any WASM crash in A350, even after 1.2.1 update. So I hope dev try to figure out whether this point is the problem.

I have installed, uninstalled and then reinstalled. Every time I load into the 600F Premium, I have to service both engines, hydraulics and the APU even though I have the option turned off. If I don't, everything is at 0%. I turn all 3 batteries on but can't get the External Power button to illuminate even after servicing the APU and attaching the GPU, although that button doesn't stay lit when I click it. There are other problems too like sunshades and the instrument panel is illuminated every time I load in. I'm at a loss and don't know what to do.

INIBUILDS A330 reverse thrust door issue/bug and not true to life, When reverse thrust is on idle the door is barley open and hopefully can be fixed as it’s unrealistic, it’s supposed to be fully open regardless of idle or max reverse thrust

Still an issue

2026 it’s still an issue smh

INIBUILDS A330 reverse thrust door issue/bug and not true to life, When reverse thrust is on idle the door is barley open and hopefully can be fixed as it’s unrealistic, it’s supposed to be fully open regardless of idle or max reverse thrust, Bug has been an issue since 2024

Since the latest batch of updates, it seems the only cabin textures available are the inibuilds blue, not individual airline livery colours inside. The SIA A350-900ULR has (yes a custom cabin), but has SIA colours. I feel that losing the individual cabin colours is the biggest loss of emersion of the A350 now. I am not talking abut the custom cabin packs, I am simply talking about the default cabin, but painted in airline cabin colours.

"Polished" is not a word I would use to describe this aircraft, unfortunately. It's getting into decent shape with a years' worth of dogged work, which tells me it was released a year too early. They're diligent and they've fixed a lot, and I appreciate that. But I worry that we're reaching the "product sustainment" phase of development, and major fixes will become fewer and farther between. At this point I'll assume that they will fix probably 50% of the remaining bugs, but that some will persist indefinitely, and missing features (ALT flight plan STILL doesn't work) will never be added.

A350-900MSFS2024NAVIGRAPH, latest AIRAC 2601Specs: Ryzen 9800X3D, RX7900XT, 64GB of RAM WASM crash when I tried to change the runway at the destination airport (KORD).

Only msfs2024

Just wondering why, after all this time, the issue of no pilot in the exterior view has been ignored. The lack of a pilot in the exterior view dates back to the "pre-FS9" days. When will it be corrected and if not, why not?

I've discovered that a faulty yoke profile was preventing the engines from starting properly. So, try creating a new yoke profile.

Dear Inibuilds Team, are you able to fix the A300-300 P2F main landing gear wheels as they are sinking into the ground? I mean to slightly raise the main gear wheels. As you did create the aircraft I kindly ask you to do that. If you are not able to do so, please forward my request to Asobo/ MS thru your "channel". Thanks in advance Chris

WASM Crash Report As many reported before. Approach into LOWW, insert rwy 16, ils 16, BUDE2W. Select NERDU7L transitition and there you go "orange" Aircraft: A350-900 Simulator: FS2024 Navdata Method: NAVIGRAPH WASM Error: WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005

I’ve reported this since the initial release… One would have thought it would be an easy fix. Fingers crossed for the next update. It’s little details like this that do make in a difference in how the user perceives how polished the aircraft is.

I believe this will not get addressed in the short or even medium term. Simply put ini’s design decision to group multiple instruments into one popup instead of single popup’s for single instruments. This means that WinCTRL has only one data stream for six or so instruments. Lots of opportunities for collisions and connections to be lost. Single popups mean singular data channels. No Collisions, much less chance of connectivity failures. This is my understanding of the situation based upon months of working to get a resolution for the WinCTRL MCDU screen freezing when used with the iniBuilds a340-300. Identical hardware MCDU, FCU and EFIS and the WinCTRL software, SimApp Pro (any recent version). The Fenix and FSLabs planes both use one popup for one instrument. Both Fenix and FSLabs airbuses perform flawlessly 99% of the time. IniBuilds not so much. The a340-300 is the only ini plane that can talk to external MCDU (FMC/keyboard), unfortunately it keeps losing it’s voice. When that occurs the screen locks up. Notably the keyboard and LSK’s still function and can be witnessed on MCDU in virtual cockpit but the screen locks up. Unplugging and reconnecting fixes it or switching off/on with a switched hub OR changing focus of MCDU from Pilot to co-Pilot in the SimApp Pro software all fix the freeze, until the next one. Very random, sometimes 10 minutes into flight, sometimes 30 but always it will freeze. No matter what your perspective there is no denying it totally kills the immersion of the external hardware. The fact that WinCTRL and/or iniBuilds remain completely silent on this well known bug is telling. Make of it what you will -A

Yeah I always have to adjust the OIS and the lower MFD separately as well. Annoying.

when i move the controller the plane doesn’t move i even turned on the engines and went to full power but still

Pc. And where can I find the WASM folder? 😕

As seen in the attached screenshot the display brightness of all cockpit displays isn't coherent at the same brightness setting. This issue is very noticable when selecting lower brightness settings via the DU master switch.

İs İnibuilds A380 coming for just msfs 2024? Or with 2020?