Systems

Hello I just installed the A350 yesterday. Everything is up to date. I use Navigraph Navdata. The UTC times looks really weird. And it happened midflight. I think it was around Munich at the waypoint KUNOD but I'm not really sure, I just noticed it around this point. Looks like the problem is present for a long time. I found a thread from March of this year. Anyone knows a workaround? Thanks all! Patrick EDFHHEGN_PDF_1767118671.pdf

PDC requests sent from the A350 (MSFS24, v1.1.1) don't reach SayIntentions, after xfering to mailbox and pressing send the message disappears without being sent. Its available when pressing recall in the mailbox, but pressing send again does the same thing. This isn't a problem on the part of SI, messages sent through other aircraft like the Fenix 320 are processed normally

Has anyone had, or have a fix for, the ECAM handing on the 350? I have a problem where after clearing the initial failed system, each secondary failure page immediately gets 'ticked' off without giving me time to run the procedure correctly. It subsequently speeds through the ECAM procedure until it gets to the status page.

After take off with Flaps 2 at about 500 ft above ground, the airplane suddenly pitches up to about 40° pitch up. Countering that with stick full forward doesn't work. After a few seconds, the aircraft starts responding to stick inputs again. This only happens in MSFS 2020, I have never seen such behavior in MSFS 2024.

Perhaps coincidence, but since the update two days ago to 1.2.0 on Xbox the OIS no longer computes takeoff performance to be sent to FMS. Anyone else experiencing this?

Hi @iniBuilds, I noticed, that when setting up the plane from cold&dark, and the IRS is already aligned, then during QNH afjustments the sim is freezing. It doesn't happen to me being on the ground before IRS is aligned or when setting up plane before decent being airborne (when it's set to STD). I've checked that on 1.1.9 version (MSFS 2024 / XBOX Series X)

Hi iniBuilds team, I’d like to report an issue with the A350 HUD alignment. On the ground, the HUD appears correct and properly aligned with the horizon. However, once in flight, the HUD does not seem to compensate for the aircraft’s pitch attitude. When the aircraft tilts, the HUD symbology—especially the artificial horizon—does not remain aligned with the real horizon. This becomes much more noticeable during approach and landing, when the aircraft is flying at a higher angle of attack. At that point, the HUD horizon is clearly offset and does not reflect the actual aircraft attitude, which makes HUD-guided approaches unreliable. Could you please con…

Just received a 4GB update tonight to a350 on Xbox - what’s new in this? edit: 1.2.0 just installed. edit2: still no spinning fan blades.

Hi! I am experiencing a number of “gamebreaking” bugs in the A350 on Xbox. A350 1.1.8 (according to library - however in the OIS it says 1.1.4 (Xbox) • Navdata doesn’t update properly - Leading to issues with F-PLN and “airport not in database” etc. • Terrain doesn’t show on display after downloading it, and restarting flight from main menu. • No engine animations. - Engines are animated as idle when spooling up, on, and in the air. • Printer prints unreadable sized textures • Fully broken displays • Fuselage is transparent on exterior model, when looking through hatch…

Dear all, I have an issue with the auto step climb feature. I programmed the step climbs in the FMC - I could see estimated times and altitudes, as well as S/C in the flight plan. Question - what is the altitude I set on the MCP? I assumed that I always set the current cruise altitude, and when step climb waypoint is reached, the plane will automatically change it to the new cruise level. Is that correct? Or do I have to enter the altitude "after" step climb? The reason I ask: When the plane was supposed to step climb, it simply told me "STEP DELETED" and did not do so. I ran out of fuel during my overnight longhaul and crashed.

Hey @iniBuilds , I’m really enjoying the a350 but I have encountered an annoying issue/bug. Whenever I start the engines the blades don't move at all, I can hear the engines spooling but the engine blades remain still. I have heard it was supposed to be fixed in update “1.1.9” but its now 1.2.0 yet it hasn’t been fixed. Please try and fix this ASAP.

Always freeze all instruments halfway, even without any operation or background consumption. The WASM error claims no picture file found. I have uninstalled and clean the WASM remains and reinstalled without Windows defender on, as well as other protective software, but I cannot find these pictures in the main folder. WASM ERROR LOG.txt

I read in the FAQ about how to do a direct-to(B. Aircraft Icon Method), but it doesn't work. In that post there is a video and I made the same but doesn't work.

The OIS is quite inconsistent. Sometimes it loads almost instantly when I turned the plane on, sometimes it takes time to boot up, and in other times like in the case of the screenshot, it just stays blank for the entire flight. The FO side works however, meaning I'm just locked out of the options section. Why?

Unfortunately, this has become commonplace on the A350 and A340... they're almost unflyable. Is there a way to fix this?

Any idea what is going on when zooming on the airport? It seems like the resolution is way too low.

Fresh install, running for the first time, can someone tell me what on earth is this...?

Hello, I hope you are doing well. Since Update 4 of Microsoft Flight Simulator, I had not touched the Airbus A350 until recently. After several updates, I honestly started wondering whether this aircraft has actually been improved at all. Unfortunately, after testing it again, the situation is still unacceptable. Basic interactions are still broken: buttons that should work with a single click require two clicks to respond, which completely breaks immersion and usability. The SimBrief integration is still not working properly — it is impossible to correctly import payload and weight through the tablet. Worse than that, the aircraft feels even more unst…

New to the A350. Is weather and /or terrain meant to work or is this INOP on Xbox?

Whenever I try to taxi the A350, the nosewheel will turn left and right 90 degrees but the aircraft will not go left or right, only straight. I have set up all the options in the OIS but to no avail. Any ideas on how to fix this?

I just put my Simbrief ID in the third-party options and when I try to import my flight plan from Simbrief by clicking in request company flight plan in the FMS 1, nothing happens, it don't import the flight plan that I created in the Simbrief, I wonder if it's a bug or if I am doing something wrong because I was some months without flying this airplane.

In spite of a full flight plan with arrival/departure details entered, the ILS for the arrival airport never automatically populates. According to the Inibuilds A350 manual, ILS should populate within 300nm. Is this a bug on Xbox?

Xbox x - is there no glare shield lighting in an A350 or is the Xbox version missing them? No light projected from underside of glare shield currently.

During filling in my appr i suddenly got a WASM crash. I had my MSFS debug active,so i was able to find the ofllowing two errors: WASM: Error during HUD_gauge_update execution. Error code : 0xc000001d WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty

I got this message on ND after 6h Flight. What happened?