Systems

Does not work. Does not accept any inputs.

After the last update I thought the flight computers and displays crashing was a thing of the past. Unfortunately I must just have gotten lucky for a while. I have tried to fly the route below for 3 times now with the A35K and every time experienced a crash. 1st time on the ground while setting up the plane. 2nd time after 3 hours, 3rd time after 6 hours. Before I have made multiple (also very long) flights without issue, also with the same livery for that matter. This leads me to believe there is an issue with the route and the interaction with the systems. DALO1Y DALOL V631 ENVAR M750 MUKEP Y891 OVSUN Y893 IGMIS Y57 POROT Y809 IDLAN Y812 ADNAP R591 ADGOR AGEDI …

The ETAs for waypoints are calculated in a false manner, and are in the past. only when opening the TIME-Page in the POSITION tab they are updated. After leaving the page the ETAs gradually work their way down into the past and become wrong again. the first screenshot shows an ETA in the past (compared to the current time) The second screenshot shows updated and correct times after opening the TIME-Page MSFS2020 A350 v1.1.6 nothing particular to recreate the behaviour, just occurs every flight. in this case from KLAS to LSZH tested WX ON/OFF on the EFIS, different PERM DATA SETUP modes, but to no avail noticed it in the version before, …

Hey, how to solve the issue, when planning the BTV point during the approach (or before), there is like 2-second FREEZE of the sim, before the map is loaded? After that it works instantly if I try to do it again, but only during the first use. Freeze during the departure as well, if I want to see the map of taxiways. When I go ZOOM, it freezes up on this page with MAP LOADING text.

Flight vector on the HUD is way off, and totally unusable. If I fly with the HUD the way it's designed; I'll end up about 500ft short of the runway threshold. This is a constant issue that I've experience on every approach since the first update incorporating the HUD into the A350.

The estimated arrival time is incorrect; the time shown in the picture is from an hour ago. Adjusting to the time interface restores it temporarily, but the problem reoccurs after a while.

Hello @iniBuilds Team. I am extremely disappointed with what just happened as I was nearing my destination after a 9-hour flight. While updating the STAR to change the arrival runway at my destination airport, everything was set and ready, until I clicked to insert the changes into the flight plan. At that moment, all the data on the screen disappeared (as if it had been wiped), and all the aircraft displays (except the EFB) became frozen and completely unusable. The result? Nine hours of flight wasted, with no way to recover or continue due to this issue. I find this completely unacceptable for a product that has been on the market for such a long time. I …

God afternoon, Using Thrustmaster TCA Airbus. I calibrated multiple times but the thrust doesn't go into reverse. Reverse on axis is clicked and also tried multiple dead zones values. No issues with MS2024

I communicate with ATC by sending text through the buttons in the ATC panel, and the simulator then gives me the text response that I see. However, when ATC responds, I only receive text responses and no audio feedback or spoken reply. The responses appear as text in the ATC panel, but there’s no audio output or spoken reply from ATC. I’m wondering if I’ve missed a specific setting, or if there’s a known issue with ATC audio responses not working properly in MSFS 2020 in connection with the iniBuilds A350.

Flying EGLL to KJFK. A little over 3 hours into the oceanic portion of the flight and for whatever reason, the heading selector switched out of managed mode and into selected mode but not really. I could turn the heading dial but the aircraft didn't respond. I tried pushing the heading select button in and the ND would blink for a moment but it would not go back to managed mode. I tried DIR to the next waypoint but that didn't work either. Tried turning AP off and back on, still didn't work. No WASM crashes in debug console. The only option was to fly the remaining 3+ hours manually which is obviously not going to work. Nothing had changed in the flight, no recen…

I had this WASM crash when I tried to import route data on the MCDU. The button changed to REQUEST PENDING... and then WASM crashed To reproduce Load at gate Power on aircraft (Battery, GPU) Request Flight Plan Systems freeze Information Aircraft: A350-900 Simulator: FS2020 Navdata Method: NAVIGRAPH Specs: Nvidia GeForce RTX 4060, Intel(R) Core i7-14700F, 32GB RAM Autosave: Attached latest .BIN file before crash Aerosoft One MSFS Utilities WASM [info] Initializing module... Aerosoft One MSFS Utilities WASM [info] Attempting to establish SimConnect connection... Aerosoft One MSFS Utilities WASM [info] …

Most of my flight I was "in conflict" even when the supposed conflict airplane was 30 miles away or so. This one here had me in conflict when it was 10k ft over me already. Never got closer than 20 miles either... Nothing in particular done with the TCAS, only that I had it set for "ABV" from departure. forgot to reset.

Tried the A350 on Vatsim after a longer time. I am having issues with uncommanded frequency changes on VHF1 radio. I could not discern any particular trigger on my side. Frequencies seem to match the default ATC? and it did an automatic transmission to the ATC? But I have AI ATC comms assist turned off.

Hello, I have received the CRZ ABOVE MAX FL message: How is this message possible? I have not yet entered any weights yet: The message was obviously correct, but at this point, the aircraft could not yet know its maximum FL. The display was correctly dashed on the PERF page. Is the message secretly using the actual weight instead of the weights entered into the FMC? I reported this issue a long time ago for the A300 and it was quickly fixed, I'm surprised to see it reappear here for a completely new product.

We just want to fly the plane right? KR, Eric

Flying around and into super typhoon Ragasa...A350 handled it like a piece of cake? PXL_20250923_123003758.mp4

As titled. Aircraft: A350-900 Version: 1.0.10 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related WASM Error: Not related Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: Not related

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. …

I flied from KSFO to KLGA, everything was smooth and normal until after I started descend and inputting the D-Atis info, then I turn the distance display to zoom to try load the airport map for BTV selection, instant hangs all WASM and the plan is not responsive to any inputs nor the FD have any movement.

A350-900, MSFS2020. When clicking "send request" under D_ATIS it turns to "pending request" and stays there. Forever. No WX is being displayed. Why?

Hello, I now encounter issue whenever I opened the efb from top panel inflight. The performance went from smooth to literally unflyable with constant stutters. Closing the efb did not restore the fps or resolve the issue. Anyone else encountered similar problem? I did not have such before SU3 update. So am not sure if this is a issue with IniA350 or SU3/ Microsoft. PXL_20250828_131631877.mp4

Hello, flew a couple of flights in the VATSM with the A350, but it appears that when there is another aircraft within 20nm of my aircraft, even if they are 2000 feet apart and not climbing/descending and is flying away, it would trigger the RA, and the RA in the PFD won't clear even if there is no traffic in the vicinity. If there is a workaround it, it would be wonderful Attached a picture of the PFD still displaying the RA after being offline with zero traffic for the past 8 hours

When will the iniA350 in the Microsoft Flight Simulator 2020 have cabins?

Cabin altitude should change at a rate that equal to the cabin vertical speed. It is far slower than that and so cabin altitude is usually well behind the commanded cabin altitude. This has been a problem since initial release of the A350. In a steady managed climb the Cabin VSI shows 400 ft/min, which is a reasonable value. However the indicated cabin altitude only climbs at 100 ft/min, 25% of the rate it should be. This means that as you get close to cruise altitude the cabin altitude is far too low and cabin differential pressure is in the amber or red range, which should never happen under normal conditions. On my last flight, as I reached cruise level (FL39…

Still in search for an answer about STEP CLIMB, MANAGED, TOD, ALT, DESCEND... 1- ISSUE: STEP CLIMB: Flight Plan loaded, all setting configured, 3 step climb profiles shown enroute and once in the air, and climbing, I set altitude to FL150 as per ATC instructions, once I am cleared to CRZ, example: FL360, FL380, FL400 (STEP CLIMB), I set FL400 and then, the STEP CLIMB gets DELETED and will go straight to FL400 which sometimes is HIGHER than MAX ALT. QUESTION: How do you properly set to CLIMB STEP to follow the climb profile? 2- ISSUE: MANAGED: When do you know if it is MANAGED or not? the A350 does not display the MANAGED light on the MCP, like the A320 does. …