Systems

Inibuilds A350 Master WASM Crash Thread 1.2.5 FS2020 This thread will be the new location for all WASM Crashes relating to the Inibuilds A350-900/1000 for Microsoft Flight Simulator 2020 Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A350. NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo. All WASM Crashes existing in this thread will be removed following the r…

So I have A350 for a long time now, but I have a big problem with it, coas every time after klicking FLY,a nd loading for like 5 or 10 min, it crashes, but not game. My howl PC without any warning it just turn off. My temps on CPU and GPU are good, I have flown a lot of times in A350, but now I can`t can any one help me??🙏

Hello All, After flying the iniA350 for a while, I noticed that the number 9 in both the EFIS and FCU is displayed incorrectly. It should have one more line at the bottom, exactly as the 6 does, but upside down. The number nine should end with the bottom horizontal line, not with the right most vertical line. Image 1 shows iniBuilds A350 Image 2 shows real A350

Hello All, After having recently flown on the jumpseat of an A350 twice and having some conversations with the crew about the aircraft, I learned something funny about it. Due to the A350's huge fuel lines, when fuel travels from the tanks to the engines, an amount of fuel becomes "unaccounted for", as this fuel has not been used by the engines yet nor being weighed by the tanks. This causes the "( FOB + FU ) - Block = X " window in the System Display to display negative values, rarely 0 as is common on the iniBuilds A350. From what I understood while talking about this with the crew, it is usually between 100kg to 800kg of fuel that can be "unnacounted for", depending o…

As the title says, I am unable to use the "Sim Default" Nav Data or at least confirm I am using it. On the OIS I have the "Sim Default" Nav Data selected, and on the FMS is saying I am using SJ6192002 which is ARINC 2303 revision 1. I can confirm this because on my WASM file fo NAVDATA and OIS part of settings at 3RD party says "Cycle:2303R1". This was not the case a couple of months ago, and it isn't on other planes (Default MSFS 2020 A320 neo v2 and Flybywire A32NX). I have cleared my WASM folder multiple times (in fact, 3 times just today), and nothing has resolved this issue. This error begun when I wanted to see what would happened if I switched the Nav Dat…

Hi, I just started to use a350 bundle ver1.2.6 on XBOX. But, I cannot start the engines only for A350-900, -1000 and 900ULR was confirmed that the engines started by same procedure. Why the engines for a350-900 only cannot be started....

Hello, I'm having a problem with nosewheel steering after landing during taxi to the gate: The nosewheel can only be steered slightly by a few degrees - and that's not enough for the necessary turns. During taxi before takeoff, full steering is available as normal. My setting in the OIS: RUDDER CTRL TILLER: YES AUTO TILLER DISCO: YES I'm using Thrustmaster-TCA-Airbus / MSFS2020 / A350-900 version 1.0.5. It seems to me that the nosewheel steering isn't reset to 'normal' steering after landing and N1 < 70%. Normal steering is only available again after restarting the engines. What other setting is important in this context? Greetings from Germany …

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’m new to the IB A350 having had it only a few days. I can’t get the forward cockpit panel flood lights to work. The PDF guide shows the flood lighting knob to be in a cluster of four lighting knobs on the pedestal, which are easy to find and operate. However, the forward instrument panel floods do not actuate and only the overhead down-lighting flood seems to operate. Of the four rheostats under the coaming, the centre pair operate the MCP lighting and the others illuminate for the tray tables (I forgot to try these out). However, when I start the aircraft C&D at a gate, the flood and dome lighting don’t always work as the bulbs (dome & …

I don't know why but in all my latest flights the ATIS/METAR wouldn't load for some airports.

Hi Your autosave functionality is great! Restore brings everything back except...time. Also restoring the sim GMT when the flight was saved, would be great. Currently the saved files are named by the real world time when it was saved, which is pretty handy, so donät change that. Mats MSFS2020

Whenever I perform an S/C during cruise the aircraft automatically engages the AUTO-DERATE option and it doesn't allow to change it into CLIMB mode.

I'm flying the A350, and using FLS for approaches (Airbus' recommend method for all approaches). I'm using the Navigraph database. For approaches that is not aligned with runway, RCSS RNP Rwy 28 for example, the final course is 272, and the runway is 277. It seems that inibuilds show the runway heading as the FLS course which is wrong. The FLS course should be the final course until the MAP, as shown in 350 FCOM: For the game screenshot below, the F-LOC is not captured when passing Final Fix which is an incorrect behavior. Is there a possible fix on this?

I hadn't updated navdata for a couple of months, so I've only just come across this issue. With cycle 2509 released, I went into the OIS to update it (I already had NAVIGRAPH data selected and linked). I did this with the aircraft on external power, no engines running. I downloaded the latest revision (2509r1) and that showed up correctly in the OIS with a green success banner and an updated revision nymber. However the FMS is still on the old revision. I tried powering off the aircraft completely then reapplying battery and external power. That didn't load the new database. I had to go back to the main MSFS menu then reload the A350 to get the new revision loaded. …

The autosave function continues when the sim is in pause state. This means that if you want to reload a flight you have only the same paused sim situation saved a lot of times to choose from, instead of a varirty different flight situations. Skip autosave when the sim is paused. Mats

After a while on the ruway during take offI lose control of the nose wheel. EFB - Aircraft Rudder Ctrl TIller = YES Pedal/Disc = Doesn't matter if it's pushed or not. Joystick Rudder axis not bound (should it?) Joystick nose wheel stearing = Joystick R axis Z ???? Mats

Dear Inibuilds community, I have been trying to update the AIRAC cycle for my A350 Airliner on MSFS2020. The Navigraph creditial has been successfully connected to the aircraft. However, when I click on UPDATE NAVDATA button on the OIS, the update never start (which suppose to appear the download progress bar, followed by green bar when completed). Please see the screenshot in the attachment below. Is there anyone encountering the similar problem as me? I have tried following different tutorials on different forums but all unsuccessful. Thank you in advance!

It used to work, but recently it stopped working. I make sure brake isn't engage at all by assigning a key instead of on the pedals, also i am also sure ground spoilers are deployed. I am so confused.... please advice. Thank you. Kenneth

Hi! I am having an issue with a350-900 1.0.8. Every time when I am in final approach and I disconnect AP, the plane goes pitch up and I have to manually correct it for not losing landing. The 1000 version is OK, without this issue. I have already tried to uninstall, but the problem persists in msfs2020. Is anyone having this same problem?

Quite possibly one of the weirder bugs I've seen in recent times. Here's a breakdown of what I've gathered thus far: When the circumstances for occurrence are triggered, the aircraft will begin moving forwards at pushback speeds and ignoring collisions The only solution is to trigger a backwards pushback via OIS (Won't have any change on direction of movement) and then triggering the stop pushback button. If first go does not work, try again until it does. Eventually, it will stop the pushback The conditions are quite weird, too. You must have GSX and the tug must be connected. If you have auto GPU disconnect enabled but you don't disconnect GPU before G…

Hi. Should I be able to send position reports via CPDLC via the ATC COM Menu under "POSITION/REPORT" page. I am currently doing a flight across the Indian Ocean and Brisbane Radio advised that I should do CPDLC position reports and they thought I should be able to but that does not seem to be the case. I know ADS-C reporting works but in this case Brisbane Radio are not able to receive those reports. Is this supposed to be a feature of the A350 or does that page just help with voice based position reports?

Good day all, When I fly A350 on MSFS2020, i found that the Oxygen Test Button is not completed on Captain side, there should be three buttons i can press but there’s only one. However, it’s correct on the FO side. Additionally, both sides are good on MSFS2024. So would you please fix it? It’s a small issue but makes sense to players who want to make realistic operations like me 🙂 Yours Charles

The T/C ETA was original :30 Over time it then bumped to :35 actual acheived was :42 Is the aeroplane climb performance correct? Or just an issue with the predictive function of the FMS? (I am unable to upload 3 images but I will try in replies below.) I can replicate this in every flight. The aeroplane, despite THR CLB is never close to it's initial (<10000ft) prediction.

I've been using the Turtle Beach Velocity one flight stick for a while now, and there wasn't any issues at all when I first used the A350, but after another load the a350 throttle malfunctions, but on any other aircraft in MSFS 2020 the throttle works perfectly fine. I also tried to recalibrate my controller but it just doesn't work. On the EFB it shows that the throttle works perfectly fine. My settings are on default, so there shouldn't be any problems with my settings. On MSFS 2024, the aircraft works perfectly fine but the settings are still the same. Any idea how to fix this issue?

I've discovered two issues in the current version of the A350 model: 1. Pitch trim indication during touch and go training During a touch and go, when initiating a continuous take‑off, the pitch trim indication should appear on the PFD as soon as the thrust levers are moved out of idle. However, the iniBuilds A350 does not behave as expected. As a result, the aircraft does not automatically pitch trim to the take‑off position, and it begins to auto‑rotate before reaching Vref speed without any sidestick input. According to the real‑world A350 FCOM, the pitch trim indication on the lower right PFD should appear during a continuous take‑off under any of the foll…