Systems

Updated to V1.0.5 and now when I disconnect the AP using the AP Disc on sidestick I get master warning chime in additonal to the AP Disconnect aural warning... Anyone else seeing this?

I regularly receive flap config and F/Ctl flap/FMS disagreement warnings when pushing back and starting an engine after a turnaround. This never happens on a first flight, but only on subsequent ones. Does this relate to checklists, state of aircraft or something else? The aircraft is prepped completely each flight. To stop the warnings, I can lower flaps but this is not a normal procedure during pushback, or clear the messages. Is this a common occurrence?

The title says it all: I cannot set the ground spoilers by pulling the handle up (works on other aircraft) and there is apparently no option for this in the MSFS menus. With the little white hand I can move the spoiler handle forward or backwards, but not up. I use legacy cockpit interaction.

After my WASM crash, I tried to resume my flight by loading the Autosave. However, the ALT*/ALT/ALT CRZ function does not work, the aircraft would overshoot the target altitude and keep climbing/descending. Aircraft: A350-1000 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related WASM Error: Listed Below Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: Attached 1745217633.bin

Hi! After upgrading to 1.0.8 I cannot use keyboard input anymore! Anyone else is having this issue!?

I noticed that braking on the ground doesn't work on 4X sim rate no matter how long I hold the brake button on my joystick. It is also acting strangely. Sometimes the pressure goes up a bit and it drops a second later. On 2X sim rate it works perfectly. This issue was not present earlier.

I apologise if this is user error but I can't seem construct a fresh secondary flight plan while in flight. After filling out the INIT page with the basic details, I try to input the airways and points of my back-up route and, when I do, it takes me to the active flight plan page and starts messing with the active plan. SEC page allows for inputting SIDs and STARs just fine but as soon as I start trying to input waypoints and their corresponding airways, I get kicked onto the active flight plan page. Thought it worth mentioning in case it's a bug.

Hello, I encountered a WASM crash during entering "MNW" (at EDDM Airport) in the ADF-Field at the NAVAIDS-Page. I had the exactly same crash during entering some stuff to the NAVAIDS-Page yesterday as well. I wanted to fly EDDM-EDDM (wanted to do some landing training), therefore created a short Simbrief flight plan, but entered another own routing (EDDM08L - MIQ - ILS08L without transition/STAR) Specs: MSFS2020 with A350-900 (Lufthansa D-AIVA) NAVIGRAPH NavData GSX active AMD Ryzen 7 5700X NVIDIA GeForce RTX3050 8GB 32GB DDR4-3600 RAM

I've noticed that in 1.0.8 I'm not able o change the STAR or the approach once I've programmed them. If get assigned a different STAR or approach midflight my flightplan will disappear and send me direct to the initial waypoint of the STAR or the approach. To fix it I've had to reload the flightplan in the MCDU, load in the new arrival and approach and then go direct to the waypoint I was going to before it all disappeared.

On the NAVAIDS page under the LS section, when manually entering the approach identifier into the IDENT field or the channel number into the FREQ/CHAN field for GLS and SLS approaches, an error message saying “NAVAID NOT IN DATABASE” appears and the input is rejected. Additionally, even when selecting GLS or SLS approaches in the F-PLN page, the LS page does not auto-populate the corresponding data as it does for ILS approaches. I have already tried unlinking and relinking Navigraph, clearing the WASM folder, and uninstalling and reinstalling the add-on, but none of these steps resolved the issue. This behavior is observed on both the A350-900 and A350-1000…

My aircraft is now freezing after implementing the latest update 1.0.8 Even after clean install and deleting WASM file as recommended . Specifically when trying to input information into the FMC, then all buttons freeze in the cockpit.

Hi inibuild team, I flew the a350 for a few months now. Overall really good and gorgeous modelling.😉 I understand that the a350 FMS is very complex and has many pages. I just like to point out a few bugs and suggestions regarding the FMS. 1. DECEL pseudo waypoint calculation too close to runway. There would be insufficient time to deccelerate and configure if followed. for comparison: VHHH to RCTP ILS 05L on TONGA1A STAR inibuild a350: 1400' flat panel training device: 3790' 2. Pseudo waypoint like (SPDLIM) (DECEL) (T/D) should not have TRK info shown. Same of ARC leg 3. No Flaps Pseudo waypoint. 4. CNPY F-PLN REPOR…

Dear Support Team, I am writing to report an issue with the A350’s braking system following the v1.0.7 update (MSFS 2020). Setup Details: Hardware: I do not use rudder pedals. I own a Thrustmaster throttle quadrant with a paddle lever behind the throttle axis. In MSFS, this paddle is configured as an axis input. The paddle remains at a neutral position when untouched and can be pressed left/right manually. Software Configuration: FSUIPC Settings: The paddle’s axis input is mapped to the brake axis in FSUIPC. A 50% deadzone is applied in FSUIPC to eliminate unin…

Hi there. Today, I had the first WASM crash on v1.0.8. The WASM crashed during cruising from RCTP TO KLAX. All crash details are on the video attached below. Unfortunately, the A350 became unflyable again before the WASM crash was solved! I also can't believe WASM crash has not been solved in 8 times of updates! Simulator: FS2020 Navdata Method: Navigraph i9-13900k RTX 3090 RAM 32GB Route: ROBIN1A ROBIN R583 BORDO Z29 GAKIA Y293 YULIA Y57 POROT/N0482F370 Y809 IDLAN Y812 ADNAP OTR5 KALNA DCT 42N160E 43N170E 45N180E/N0485F390 47N170W 48N160W 47N150W 44N140W 40N130W/N0476F410 DCT DACEM DCT PAINT DCT PIRAT DCT BURGL IRNMN…

When the cover is automatically removed, it will also be removed chocks

If you select the GLS-Y approach for EDDF for any of the runways, it'll load the GLS-Y approach procedure, but incorrectly load the GLS-Z GLS frequency and identifier. This is an issue because the two have a different G/S angle and if ATC expects you to fly GLS-Y and you fly GLS-Z, issues may arise. On top of this, it breaks immersion as noise abatement procedures can no longer be applied unless you explicitly ask for the GLS-Z approach To reproduce incorrect GLS channel: Select EDDF as arrival airport Select GLS-Y for any of the runways Note the GLS channel will be for the GLS-Z approach To reproduce inability to select new GLS channel: C…

On initial startup in the OIS page I check to make sure that my throttles for my joystick are calibrated. According to the page they are, but when I go to the throttle on the sim when I move them they immediately go to full power with the slightest touch. This also occurs when I use the keyboard input to control them. Also once I have started the engines they are in full reverse and when I try to take them out of full reverse they initially go to idle but then immediately return to full reverse. I am using an older joystick (Logitech extreme 3D pro). I have no issues with this joystick on any other aircraft. Also all other inputs (Flaps, brakes, spoilers) work fine o…

Hi everyone, Im struggling to turn off the main panel lights at night. I can't seem to find where to do it? Pedestal and overhead are fine. Thanks Jon

Just like the title. RJAA / RWY16R / PIGOK2 departure Direct to PIGOK after passing 3000 feets, it didn't continue the way to next waypoint but slightly bank to the left when AP still actived with THR DCLB / CLB / NAV mode. Autosave files attached. 1745233816.bin 1745234960.bin 1745236253.bin

Hello, After 1.0.8 update, auto time compression is not usable at 4x. Everything is OK with 2x but the moment I switch to 4x aircraft starts rolling left and right really hard, I am not even able to disable time compression because of the movement (FL410 with very stable and calm wind). I had to pause the simulator from top menu and then recovered it. Tried many many times, every time it is doing this behavior. It was working very well on previous versions but not with 1.0.8 and it is making really hard the long haul operations

After updating to version 1.0.8 the aircraft works ok but during landing, after touchdown, the A350 starts turning left or right all of a sudden and I find myself off the runway. This has never happened on previous versions. Any help is appreciated.

The continual updates for the 350 are excellent and clearly reflect Inibuild's commitment to change and improve the aircraft in many ways. This is fantastic and welcomed. The one omission I have with the 350 is the lack of integration with the Saitek Radio Panel. Is there any way of creating LVARS that enable these frequencies to be changed ? I have tried with Simconnect with very limited success. If Simconnect is the accepted way to go, can improvements there, in terms of direct impact for the 350, still be made?

I had this crash while changing the origin airport of SEC2. General Information: Aircraft: A350-900 Simulator: MSFS2020 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 Specs: I9-10900K, RTX 2070 super, 32 GB RAM Steps to reproduce: A350-900 Start a normal flight Complete FMS setup (in my case EDDM-KSAN) Enter a custom SEC3 F-PLN (in my case EDDM-KLAX) Enter an arrival for SEC3 Change the origin of SEC3 (in my case from EDDM to KSAN) See the WASM freeze…

Hello, After loading into the aircraft the camera freezes. I cannot move around anymore. Normally this happens with holding the right mouse button and moving the mouse so you can 'move your head around' or zoom in and out. That does not work on the inside nor on the outside view. With other aircrafts I do not have that issue. Makes the aircraft not usable... Can anyone help?

I posted this twice already, with no replies, nor a fix. The crash actually happens when entering the letters L I P Z. Should be an easy fix.