Systems

Hello, I flew at FL400. I noticed that the GNSS data displays 40.000ft: When I changed the barometer setting, the GPS altitude would change as well: I would have expected the value to be the geometric altitude as measured by the GPS, which in this case would have been 41450ft, instead of a baro corrected altitude. Again, this issue was present in the A300, but quickly fixed and is now back in the A350.

Flying an SLS approach is not described in the manual, so I'm not sure if I'm doing something wrong here. I tried two approaches, which have LPV minima (one at LFPO, one at EDDH). In both cases, only FLS engaged (for non-precision approaches to LNAV/VNAV) minima. I would have expected to see SLS here for LPV minima. Is there something specific one has to set up (other than selecting the approach in the FMS) for SLS to work? I see others had issues with this as well, but I don't see a solution there: Few issues with 350 SLS lpv approach

When changing the altimeter unit between hPa and mmHg, the ISIS unit remains unchanged. The only way for ISIS to follow the altimeter unit selected is to sync all 3 altimeters in options. Aircraft: A350-900 / -1000 Version: 1.0.12 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related WASM Error: Not related Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: Not related

When I move the throttle smoothly with my Thrustaster TCA the throttles are 'shaking' Who can help?? ini A350 throttle.mp4

Aircraft: A350-900 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: attached to post. WASM Error: Specs: CPU - 12th Gen i7-12700F, GPU - GeForce RTX 4070, RAM - 32GB, Nvidia Driver 576.80 Autosave File: none forgot to turn on Autosave after the update, cause we have to constantly clear the wasm folder for each update. Which is getting annoying at this point #rantover Was about an hour +/- away from Copenhagen, went into MCDU and was able to input the runway 04L and then choose the ILS then boom WASM crash, 2nd time within 48 hours, this is getting ridiculous, i even restarted the PC before this flight... 😕 KSFOEKCH_PDF_17522844…

Hello, I am regularly getting this alert (usually when flying at 30 000), but I have no idea why and how to resolve it except descending to lower altitude. I always start using default panel (No cold n dark) and hardly change anything manually on the overhead panel etc... Appreciate if anyone can help point me to if there is any button that need to be set/ changed to resolve the alert while cruising at 30000 or higher? PXL_20250713_060921053.mp4

Hello ini Team! I just made my first flight with v1.1.1 on MSFS 2020 and it was great flight, this was the best flight since last couple updates. Thanks for the effort! I had 1 issue: During the cruise, I got direct from ATC to initial approach fix and applied it, but after speed setpoints changed from mach to knot and it was 200 knot at FL410, which does not make any sense. I also attached a screenshot for it. It was showing the .85 mach again at T/D. Other than that HUD was very good but I suppose it needs small position adjustment, bottom line is not visible at default looking position. And also, please bring back the "autobrake off" cal…

Hello, Encountered a new issue only started today. After flying for some time, all the buttons in the cockpit stopped working (frozen) even though aircraft is still flying. In video you can see the altitude button turning animation but the altitude is not changing accordingly. Also, I am not on any beta program of FS2024. PXL_20250710_122446132.mp4

As title implies, landed at LOWW, when BTV came off due to landing completed, I had a WASM crash Aircraft: A350-900 Simulator: FS2024 Navdata Method: Navigraph WASM Error: WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005 Specs: i5-13400F, RTX 3060 12G, 2x16 3200 MT/s Autosave File: Included below Video of issue happening included as well MomentsclipfromJul122025.mp4 1752342843.bin

Today I want to fly from EDDM to KCLT. Seven hours all was ok. Then... Throttle frozen, alt sel frozen, autopilot frozen. so way to land the aircraft! SEVEN HOURS FOR NOTHING!!!! I'm SO frustrated!!!!!!!! Find a solution NOW!!!!!!!!

Hello, When I turn on batteries to the aircraft, the EFB does not initialize (I have sat and waited long enough for the IRS to align, still nothing). I have tried clicking, etc.. did a re-install of the plane and still have the issue. Any thoughts on a fix for this? Was working fine before the latest update.

Hello, I was using SayIntentions AI. I have updated my aircraft to the latest version. When receiving messages from CPDLC, pressing wilco does not acknowledge the instructions. Also, when I request for Pre Departure Clearance, pressing SEND does not transmit the message. Everything else work, I am able to ATC and receive messages from CPDLC. Also, it was working perfectly fine on the previous version. Thank you.

Hi guys, That said I realy did a lot of flighs with older builds and the Autoland works realy well, but with this new build it dosent work as before ??? The story begins at around 1500 to 1000ft ( plus-minus ) before the landing Airport runway ( that sayed LOC seems fine ) the GS pointer goes down fast and the AP tries to catch the pointer what brings the speed of the plane up high so the plane goes up and down trying to hold GS what ends in a jumping bag and so the plane hits the runway like a stone and you just can`t do nothing if you don`t shut off AP and AT and handle it your self - but that could be the thing from an Autoland !! I did a same flight wti…

Aircraft: A350-1000 Simulator: FS2020 1.39.5.0 Navdata Method: Navigraph OFP: ZSPD/34L N0513F330 LAM92D LAMEN A593 SADLI Y590 BEDAR Y591 FUE Y23 KASTE Y81 TASOT Y57 POROT OTR11 LEPKI/N0502F350 DCT 42N160E 45N170E 47N180E/N0496F370 47N170W 47N160W 47N150W/N0484F390 45N140W 41N130W DCT FATMO DCT PAINT DCT PIRAT DCT BURGL DCT IRNMN IRNMN2 KLAX/25L WASM Error: WASM: Exception c000001d in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-1000/panel/inibuilds-A350.wasm Specs: R7-9700x, RTX 4070super, 32G RAM Autosave: Not engaged P.S.: It frequently happens on a cross-Pacific flight. As shown…

As titled. No input at the time of screenshot. Aircraft: A350-900 Simulator: FS2020 1.39.5.0 Navdata Method: In-sim OFP: N/A WASM Error: N/A Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: N/A

Good Morning, Display Clickspots not working correctly. Have to click around 10 times until something happens. BTV selection is also a thing to go crazy. It's like everything in the Displays is very laggy but there are no Lags. And i can say for sure it's not my system. Otherwise really nice aircraft. Greets from Vienna

Aircraft: A350-900 Simulator: FS2020 Hello Inibuilds Team, As per the title, arriving into EDDF, either I via user error or the aircraft had erased the active flight plan (I suspect it was my own doing as I was trying to add a transition and must have forced the loss of the active FLP. This is not the issue/bug, however, maybe useful for context). I then attempted activate the SEC Flight Plan as the active had nothing in it, upon pressing "CONFIRM*" the FMS and all screens froze. I was able to manually fly the pitch and roll axis of the aircraft, although the aircraft claimed to still have A/P 1 engaged, however, had no control over the throttle which…

WASM crash in latest 1.1.0, screens all frozen but the sim kept running. Aircraft: A350-900 Simulator: FS2020 1.39.5.0 Navdata Method: Navigraph OFP: RJTT/16L ROVER2B INUBO Y808 NOLAX Y812 ADNAP DCT KALNA DCT 44N164E 46N171E 49N176E DCT EYWAK DCT CURVS DCT CHUUK R341 ODK DCT 58N150W 58N140W 58N130W DCT IKPAM DCT KAVDA DCT MEETO DCT DUKPO DCT IKLUG DCT 48N095W DCT KP15G DCT TVC DCT JHW J70 LVZ LENDY8 KJFK/22R WASM Error: WASM: Exception c000001d in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-1000/panel/inibuilds-A350.wasm Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: 17513123…

Hi all, I recently switched from FS24 to FS20 for unrelated reasons, and since then I have not been able to provide electrical power to the A35K. The green AVAIL light is on but when pressed nothing happens. Same with the battery switches.

Hi there. After updating my A35K, there was no response when I pressed BAT1 to BAT2. However, the A359 works normally and responds as expected. The OIS can’t display because the BAT isn’t connected. And there is no ENG cover when the plane is loaded into the airport.

Hello When I try to calibrate in the A350 efb settings regarding the thrustlevers, my TCA Quadrant Airbus Edition always show 50% even though my physical thrust levers are on idle. When I move my physical thrust lever to idle, it goes to 50% instead of idle. When moving the thrust levers to max reverse, it shows idle which is not correct for the TCA Quadrant. Any help appreciated. /Amir Khatibi

Extremely dissatisfied after just downloading the 350. As per the title, upon spawning in on runway or gate, no buttons work. The battery and ext power buttons are clickable but doesn’t do anything. Ext power shows AVAIL but clicking does nothing. I spawn in -> straight into cockpit -> turn on all batteries but this does not do anything. Same story with the external power. Cannot access the EFB due to no power. Tired: Restarting sim; trying different liveries/airports; restarting sim; clearing WASM folder; uninstalling and reinstalling; spawning on runway; etc. Spawning on runway spawns cold and dark. Any fixes for this? Was exited to fly th…

I tried to input an ifr route from rjtt haneda to vhhh HK, and 2 airways are missing. A1 and Y50 are missing. The way point works fine, just the airway didn’t register. Not sure if the database is up to date or maybe I am doing something wrong. So I am curious to whether all the airways are in the fmc or only partial airways are available. I did fine registering routes flying from vhhh to kjfk.

Since the last inbuilds update the interaction with the mouse is disturbed. Rotary switches work, but no push buttons. Batteries, GPUs etc. cannot be switched on.

Hi, New to A350. I created a flight plan in Simbrief. When I import the route into the FMS, the FMS displays a message "Airport not in database". My route is OMDB > LTFM. I read that recently some folks had an issue importing after an update. I am wondering if anyone has encountered this error and what they have done? Thanks Matt