Systems

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

I have set my f-plan with department and arrival info properly and computed the stop margin as well. But when I want to set the btv exit there’s no stop line on my ND as the picture shows. I have subscribed navigraph and turn to PLAN mode. Is there any step I missed? Or how can I solve this problem?

During my flight, the sim suddenly lost all sound and froze. After few seconds, the audio returned but was very choppy, and then the game crashed to desktop, it has happened more than three times , they crashed around 4-5 hours after departure. However, It happened more frequently after 1.1.4 upate. It happened on many people too. By checking the Winows Event Viewer, the erro code is 0x80000003, which a Breakpoint error. My platform: 9950X3D 5090 48G RAM MSFS2020 DX12 TAA NO OVERLOCKING 350-900 1.1.4 I hope the team can find out the reason cause this error Crash.xml

now every flight over 5 hours will have WASM crash and cannot handle the plane, so frustrating for a long haul airliner

Hi there! I tried to test out the SATCOM on the radio communications display but it was greyed out so I tried selecting it but nothing happened and it just stayed in the selecting page to get into the SATCOM system, I already activated it on my EFB but it is still greyed out.

Hello All, I am experiencing problem engaging reverse thrust consistently for each landing since SU3 update. E.g.,When in cockpit view during landing (without throttle quadrant in view), the reverse thrust sometime engages but not other time after touchdown. Strangely though if I positioned my view to look at the throttle quadrant in the cockpit, the reverse thrust immediately engages... Anyone else encountered such or has a solution that works?

Hi everyone, Sharing some issues I’ve discovered on the A350: 1. Unable to scroll down on a SID/STAR selection menu. 2. Reverse logic when inputting an average wind component. The user places -XX for tailwind and +XX for headwind in the simulation. 3. SPD SEL XXX not displayed on FMA row 2 when preselect is programmed and takeoff thrust is applied. 4. Auto emergency descent - no automatic countdown. 5. Auto emergency descent - heading mode should engage on a parallel track after offsetting 3 miles to the right. (It engages on a divergent heading and maintains this in the inibuilds) 6. Fix page has limited radius range input. I haven’t t…

A350-900 in MSFS2020 FMS and MCDU frozen in flight. Please see the attached.

Hello, I must say that I do like the A350, however, on two recent flights, I have lost steering response on the tiller after landing. The tiller jumps around and snaps back to centre when fully deflected, this did not happen on departure after calibration. Could this be linked to being unable to unlink the tiller and rudder? When will that issue be addressed? This jumpy tiller issue is not seen on other MSFS2020 after-market aircraft nor in X-Plane, so I know it is not the hardware. Cheers, MapleFlyer

Flying into UKCC and as it's not an actually present airport with active navdata, I have to manually program the STAR. Just for convenience, I decided to create a custom waypoint on the touchdown zone with the constraint of the airport elevation, partly to allow a theoretical RNP approach, and partly to act as an estimate for what time I land However, it seems that the aircraft handled that in a really odd way. In the autosave you can see the result, it decided to ignore other constraints and put the VNAV path in outer space Dunno what exactly caused it but it's quite an odd issue to say the least And to add extra details: Navigraph navdata, MSFS …

Since the latest Update, i have a Fuel Flow, but no "ignition" the spool up stops at 10.4 N1/ 31.2 N2/ 51.1 N3 (N3 with grey backround). I cleared the WASM Folder, reinstalled the A/C several times, but nothing helps... maybe someone from the community can help...

Hello, I have version 1.1.4 and flew from EGLL to KJFK yesterday. While approaching KJFK at approximately FL220, the autopilot failed for no apparent reason and wouldn't reengage. Since navigation using the manual heading and altitude also didn't work, I aborted the flight. Perhaps someone has had the same experience and has a solution. Best regards, Guidschi

Two issues in one go: First, after departure from EBBR, I suddenly received a TCAS overlay on the VSI. I didn't get any explicit climb or descend instructions, nor did I see any traffic on the ND. There was also none in the SURV TRAFFIC page. To fix this, I tried recycling TCAS, disconnecting and reconnecting from VATSIM, and nothing worked. Even offline it continued to show the overlay. This is shown in image 1 Second, I had 2 conflicts with aircraft that I would never have a conflict with as I was climbing out and at cruise. This is shown in image 2 and 3 Autosave file included for the first situation in case it helps TCAS.bin

fixed

1. In the middle of the bird the FPD is the inner circle. It should not exist with FD off. 2. Delta speed and synthetic runway function on HUD are missing 3. Flight path angle sometimes incorrectly shown on HUD and outright missing on PFD (-3 selected by approach). in the image below, while already descending at 2400fpm, the -3 path is suggesting 12 degrees pitch down. also, manual selection of FPA on AFS CP has no effect! (for example, in the first image, the selected FPA is -2.3 pulled) FPA -3 shown above horizon

Hi, I just want to address if this is an issue for anyone else other than me. Whenever I hit "Direct with Abeam" to a way point, I get two weird lines and it also messed up the ETA and fuel prediction stuff. I tried to fix this issue by hitting a normal "Direct" afterwards, but to no avail. This issue was not apparent if I hit "Direct" to a waypoint normally, and only happen if I use "Direct with Abeam" to a waypoint. This was also not an issue in previous releases and this is not the second time that has happened to me while using V1.1.1. If you need any other information, please let me know. Thanks for the help.

BKPR Pristina (Kosovo) is showing up as “Not in Database”. I get get the charts up on my iOS app, and the FMGC is accepting it as a valid airport. But when I try to select it in the Nav Display, it says it can’t find it. I’ve searched by ICAO, IATA and City name, I’ve also used the old ICAO code LYPR. Is this an iniBuilds "thing" or a Navigraph issue?

Morning All, Just tried requesting a PDC at EGLL + logging onto EGTT in the air (above FL100) and nothing happens. It says 'last notified........1320z' when I do so but doesn't actually log on. Any suggestions? I have got all the correct fields filled out in the EFB (S.I. Hoppie and Navigraph API keys). It does however work on Flight Sim Messenger (web based) but it's like the A350 isn't talking to the S.I. servers. I have spoken to S.I. and they have confirmed the A350 isn't talking to their servers. Help?