Systems

Hi guys, I had my reverser correctly configured before the update. I followed your instructions and recalibrate it. However when I landed for my surprise it did not work. And I opened the configs, did everything again as before and still I cannot get my reversers to work. Any idea?? Thanks

Not sure how easy or hard it would be to implement better fuel temperature simulation example: full wing tank on ground temperature @ 12c 15 mins into the cruise fuel temperature @ -20C matching tat. As real world airline pilot i expect much slower fuel temperature cooling, also with solar heating would be really welcomed. Secondly my thoughts why this would a great update, is the fact this aircraft is for long haul, and low fuel temps may happen with extremely cold air masses over long durations where pilot action will be required. over all this fantastic aircraft, and im sure it will become even better over its life span. Let my know what you g…

I have it happen that on longer routes, although the enroute winds are listed in the simbrief flight plan, many do not appear in the MFD Wind CRZ page. Even after forcing downloading the winds (CPNY WIND REQ -> *insert). Anybody else having this issue?

Route: KMIA-EDDM TOW: 226 t LW: (screenshot) *LMAO*

One question, with the latest version, on ground, without APU running, if I turn the Beacon ON for testing purposes... it cuts the ground power automatically,even if in the Options the Auto GPU disco is on NO. Is this normal?

Hello iniBuilds Team, this is a WASM Crash Report. I flew from OMDB to OKKK and inserted KUA VOR in VOR1 in FMS and then the monitors froze. I used the MSFS 2020. I wrote the Crash Codes down here. I hope it helps you. - Assertion failed: IsNumber() (E:\iniBuilds\MSFS SDK\WASM\include\rapidjson/document.h - WASM: Exception c000001d CommBus callback in module m178088ef2d4800fa - WASM: callback execution for event NAVIGRAPH_FunctionResult, in module m178088ef2d4800fa, failed Thank you! Felix

Help i have flown this aircraft 3 times now and everytime without incident, but everytime i have ILS sw on LOC sw on but it does not capture the localiser or glide path, pls help

Bug report of two related issues: 1. Checklists don't automatically close a few seconds after all items green as in real world. Have to click C/L COMPLETE to close them. 2. Hitting the C/L MENU button doesn't automatically bring up the next checklist. Instead, it always opens the checklist menu, and I have to manually select the next one from the list (completed ones are greyed out in the menu).

I had a WASM crash when I entered the arrival into the KCCU (clicking INSERT TMPY) Happened when: VABB, Arrival, entering RWY 27, Entering ILS Z 27, Entering Insert, Clicking INSERT TMPY -> Crash Information: A350-900 MSFS 2020 SIM Default Navdata WASM Error: WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Specs: RTX 4080, I9 12900k, 64 GB Ram

After update now the AP keeps disconnecting itself and I go into a steep left hand dive which have to manually try and recover from. First it was on climb and then was on cruise. New flight did the same again.

Hey, just had a WASM crash when I chose "New Destination" on the arrival airport and entering my new destination (LFPO). It froze right after I clicked "INSERT TMPY*" Original route was KLAS-EGLL. Aircraft: A350-1000 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: attached. WASM Error: attached. Specs: 5900X, RX 6900XT, 32GB KLASEGLL_PDF_1741016168.pdf

In my first attempt for a flight from EBBR to EDDM, i was not able to select runways and access the SID for EBBR. Same problem for STAR in EDDM. the available runways do not display the runway labels 25L, 25R,...there are only some technical data & figures that do not match....

The input freezes when I try to enter VOR 2 in the FMS. Always needs a restart. Every attempt to enter the frequency fails MS2020

Hello! I bought the A350 today. I'm playing on FS2020. Unfortunately, the plane cannot be operated. I have the following problem: It doesn't matter whether I start on the runway or at the gate in the cold and dark state. The buttons in the cockpit just don't work. I have no way to operate the buttons. There is just no clickbox on several cockpit buttons. I tried everything. Uninstall the plane, install the plane again. Changed the departure airport and switched from -900 to -1000 I have here a link to a Video in my Google Drive account, since the Video is to big to upload it there. https://drive.google.com/file/d/1rTfqhjCMInm1XK3i…

With everything set up for landing at FYWH (elevation 5641'), the LDG ELEVN shows 0 on the SD: As shown in the screenshot, the cabin happily descends below landing elevation. Could this be fixed?

Shows the plan on the standard map, but should be able to display flight route from Navigraph?! When is this operational?

Hey, did a manual step climb from FL390 to FL410. After that it seemed, the aircraft started loosing speed and went in an uncontrollable pitch, yaw and bank movement. Even pushing TOGA didn´t brought the plane to react. It just got worse. I only could "fix" it after disconnecting AP and manually brought the plane in the correct position (heading). Is this a known issue? Unfortunately i couldnt load more pictured due forum limitations.

Hey guys, my flightplan disappeared mid flight and i only could resolve it with Dir to another waypoint. Is it just me or a already known issue. I saw in older posts, that it already happened in your A320Neo. I didnt set up this "toggle autostart". KR Robert

Hello, how do I open doors? Can only find cargo door controls, no entry/ service doors.

Left side is correct: AT SAVRY STEP TO FL400 Right side is not correct: GOMUP was the last STEP CLIMB from 380 to 390, but the distance and time readout to SAVRY is correct. There should be "AT SAVRY STEP TO FL400".

What on earth is going on with this plane. In 2020, 4 hours into flight, simply going in to select BTV and all screens freeze!! Sim is still running, I can interact with all sim menus and the EFB, button animations work but nothing is functional. I can't even take over and fly manually. I can't disconnect the autopilot. MFD is frozen and the airplane is no longer flying along it's route but the plane is physically moving still. So this is not a sim crash or an issue with MSFS. This has to be the buggiest plane I've ever flown which is unacceptable for the cost.

Aircraft: A350-900 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: NA WASM Error: WASM: Exception c0000005 CommBus callback in module m178088ef2d4800fa, WASM: callback execution for event NAVIGRAPH_FunctionResult, in module m178088ef2d4800fa, failed Specs: Ryzen 9 5900X, Nvidia RTX 4080, 64Gb DDR4 3200 Steps to reproduce: Swich ND range to airport map during descent into KATL

When flying an offset non-precision approach with FLS, the F-LOC beam projected by the FMS presents a straight runway extension instead of the offset approach path as described by the FCOM. See the following pictures for an example from EBBR on the VOR 07L, which is offset by 15°. Note the difference between the magenta-dashed FLS beam and the solid green NAV path. According to the FCOM however the FLS beam should extend from the MAP (recoded as EPxxx, here EP07L) on the reciprocal of the final approach course, see the FCOM reference below: This makes FLS basically useless for offset approaches in the current implementation. Behaviour is consisten…

Future feature?