Systems

I ran into an issue where the flap indication says it's at Flaps 2, but the flaps are stuck in the external model. Slats work fine. I rolled back to 1.1.0 which I backed up, no issues on previous version. Aircraft: A350-1000 Simulator: FS2020 1.39.6.0 Navdata Method: In-sim OFP: N/A WASM Error: N/A Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: N/A

When I click the insert option it doesnt insert the FP in to the system. the flight number, departure and arrival are not imported in to the flight computer. What am i doing wrong?

Hello! I was flying the -1000 earlier today and was using the auto step climb function for the first time. I had auto-step climb enabled. But prior to departure from Heathrow, I entered the step altitudes manually into the MCDU and eventually when I woke up - like about an hour away from TOD. I realised I was still at my initial altitude (FL340) - I'm not sure if this is useful information but I was using the miniFCU and I had it set at FL340 after my initial climb and didn't change it to any higher. Thanks in advance

Something seems to happen with that setting ( Auto Derate-CLB ) it was other in the last build.. Had a climb ( A350-1000 ) to 33000ft from Honkong VHHH and this took with around 250000kg 205nm and this was with Auto Derate. So i did this twice than with CLB and had the same NM so my Question, should that be not much faster, i mean 200nm seems not realistic with CLB the plane wasen´t near full ?? cheers 😉

Hi, I've been having this issue since many updates and have put a message in the Discord numerous times and no-one has acknowledged this? When you are using the MCDU to input something or insert something or press one of the buttons you are having to press nummerous times for anything to happen. This didn't used to happen when it was first released? It's some sort of lag and I've seen many people mention it. Can this be looked into please Thanks

I'm doing the corect procedure by selecting plan and then the zoom then wait for the map to load. Once loaded the map just moves around the ND display eventually you can stop it, then when clicking the relvant runway to SET LDG RWY it will not work again this has been an ongoing issue since various updates have been published? THanks

Is the HUD still not available in FS2020? I updated to v1.11 but the HUD is not clickable and is not usable.

Today I made flight from KCLT to EDDM. One hour before TOD I set the approach (RWY/STAR/VIA) for EDDM. I checked the flightplan and saw I used the wrong STAR. The runway was 26R ,the VIA was MIQ but the STAR was BETO1B. So I went back to the arrival page on the FMC. I didn't change the RWY neither the VIA only the STAR to ROKI1B. Then the plane partially frozen. No sidestick command, no throttle command and some other functions didn't work. I tried to save my flight. So I pushed the "save now" button and entered a text but the flight wasn't saved. Next I restart the flight by using the last autosave on a runway near the frozen point. At the first try …

Newest version installed, flew from KSFO to VHHH in the A359 B-LQA Cathay livery. Following Route: KSFO/28L N0497F340 GNNRR3 ALCOA DCT CEPAS DCT COBAD DCT 40N140W/N0496F360 41N150W 40N160W 38N170W 37N180E/N0487F380 35N170E 33N160E 31N150E/N0482F400 DCT NOGAK DCT BIXAK DCT RYUKI Z34 TETTA Y342 IGURU G581 ELATO V522 ABBEY ABEY4A VHHH/07R When I inserted the STAR (Runway 07 - ILS07 - ABEY4A - TMPY INSERT), it lagged for a minute and my whole ND was messed up. Checked the KCCU and saw that parts of the STAR and the Standard Go Around Procedure were inserted multiple times. Never had this before, might be VHHH ABEY4A Specific.

freeze at the gate. initial starts ok. wen receiving the FP puffff all frezze, FS2020 - A359 console error: Aircraft: A350-900 Simulator: FS2020 Navdata Method: NAVIGRAPH WASM Error: WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm

On newest A350 build ( 1.1 ) At a last flight landing at OMDB ( inibuild ) and traveled to my Gate and there goeing to shot of my engines. After reaching my gate i would goeing to shot of my engines which i did with the two cut off levers at the pedalstal but the engines did not go off so i tried to load a panel save ( APU and or at GPU ) but this didn`t work either - no engine shot down so what.. ?? 🤣 Bug or WASM crash ?? Help..🤪 cheers 😉

Hi Every time I start a flight, the external power does not show 'avail'. I then I have to close the game, clear the wasm folder and try again before it works. This happens constantly, please help.

I had the WASM crash on v1.1.1. The plane was not at all installed on MSFS 2020 when this update was released, so it was very fresh. I was using it on MSFS 2024 though and had held off on installing it on MSFS 2020 hoping that 2024 would work but it has not. The WASM crash occurred about 500 miles outside of Seattle, or about 8 and a half hours into this flight. When it crashed, I was specifically changing the runways, approach and the STAR prior to reaching them due to a runway change at the field. I have tried MSFS 2024, now MSFS 2020 and I can not use this plane in its current state. I can't wait to come back to it and I wish you all the best in getting everything squa…

I had the WASM crash on v1.1.1. The WASM crashed after landing in RJFF from RJTT. I cleared the WASM folder before updating the A350! Simulator: MFS2020 Aircraft: A350-900 Navdata Method: Navigraph i9-13900k RTX 3090 RAM 32GB Route:TIARA3B GUSRO Y20 KIRIN KIRINE

When the ACFT TIME REF is changed to MANUAL and a new time is set, the predicted times for waypoints in the active flight plan (F-PLN) do not update. The times appear to remain based on the previous time reference, rather than being recalculated relative to the new manual time. Steps to Reproduce Ensure an active flight plan is loaded. Navigate to the TIME page in the F-PLN INFO menu Change the ACFT TIME REF from AUTO to MANUAL. Enter a new time that is different from the previous AUTO time. Return to the FPLN page to observe waypoint times. Observed Result The estimated times of arrival (ETA) …

hi there, i have the issue with the Airbus TCA sidestick, every time, whe i only touch or move a bit the sidestick the Autopilot disconnect and needs 5 or more klicks to get the AP on. I have in the Options the AP Disconnect Protection on and it dosent work correctly. i hope anybody kan help to solve that Problem few details A350 v1.1.1 MSFS 2020 AIrbus TCA Captains Pack

I updated the aircraft and deleted WASM, but after landing the aircraft all systems stop. This issue was already present in V1.1.0 and is not fixed yet. Why does this aircraft keep having serious bugs every time I update it? Does iniBuilds have any intention of fixing this bug?

So far, I've found 2 airports that have a broken ATIS, EKCH and LOWW. Both on the ARR and the DEP variations Screenshots below display this issue, hoppie logs attached to show that the data is sent to the aircraft correctly To reproduce, wait for EKCH or LOWW (Or potentially other airports too) to go online on VATSIM, when they are on attempt to pull a D-ATIS from those airports via Hoppie's ACARS and observe the missing data

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…