Systems

Hi, the flight time is not correct on the FMC. I did a 6 hours flight and it says that my flight time is only 2hours... i did use sim rate x8 for the flight. any work around for this? or is there a fix coming up for this?

Hello, I just blew past my approach to 33L (ASOBO default CYYZ). I did my approach usual approach checklist, ILS frq, barometer, etc. etc. all good. The flight display did show the correct information for the approach (LOCALISER captured, G/S ARMED. However, when I flew into the glideslope, the plane did not capture and descend as expected. I have successfully landed the inbuilds A350 before at other airports, so I have no idea what's changed/broken. As I also fly my PMDG, Fenix, and FSS, airliner models I can't say for sure if the latest update broke it or even if its because of the airport. I did a full go around, and again, the glideslope came and went. …

With V1.0.5 GSX couatl crashes at any service. Jetways, calling for refueling, etc. Of course pushback won't work neither. Okay, let's use the OIS-Pushback ... but, it doesn't work too. And i'm still not ably to connect navigraph again, ois doensn't react. At the current status, the airplane is not useable.

I performed a go around procedure at EDDP. After having retracted the landing gear and re-enabled auto thrust and AP1, the plane took an right turn off the caluclated route, the ETP was somewhere in the middle of nowhere, although NAV mode still had DO55U as the next waypoint and estimated to be off the route about 30 Nmls to the left....

I have found multiple autopilot / FMS bugs: 1. Although at the target altitude (3000ft), the ND still shows the level off arrow along the planned route (being fully automated flight with NAV and ALT active): 2. ETP calculation: I found the ETP being falsly recalculated on two occasions: One after I inserted an "Direct to from P. POS" the ETP show up in the middle between the P. POS and my destination, the other one strangely more or less on the thrashold after having performed a go around. 3. The level off arrow showed up even behind a --MANUAL-- Discontinuity - how would it know when I was going to turn und hence when to reach the target ALT?

Hello, When I start the plane, a message screenon the CPT Inner Display Unit screen, it says "T.O THS OUT OF RANGE". Help!!!

Hi Guys, Just wondering what I am doing wrong. I turn on my VFR radio and can receive ATIS but clicking on request IFR clearance does not work. No response. Regards, Steve.

I had a WASM crash when trying to insert holds into my flightplan. Steps to reproduce: Everything is on video, but to summarize: - Inserting a HOLD at REQIN - Trying to change hold config (turn, leg defining parameter) - Hold was not displayed on the ND, so i tried to enter an other HOLD at BOURI (waypoint before REQIN, without removing the HOLD at REQIN) - Trying to modify the HOLD at BOURI - Inserted HOLD into flihgtplan, flightplan diapered and the WASM crash occured I have it it on video, watch it to reproduce (first hold at 1:53, second at 3:31, no flightplan & crash at 3:50, after that i tried to resolve crash without success, showing console…

Hi all, Unable to step through Flightplan one waypoint at a time I used to be able to but now it steps through a page at a time. Thanks Jon

I think I'm getting confused with the right thrust calibration for keyboard use. Now I get reverse on F1 (idle), And when I want to taxi, it almost sets TOGA. I did set the steps on calibration, but somehow it doesn't appear to be right. Can anyone show a right way or is there a general "reset" function for this? The rest is really fine now, great to fly, even with smaller system specs like mine on FS20! When I read most of the recent posts here I think I am lucky somehow

ANF not drawn correctly on F/O's ND. Ok on Captain's side. - v1.0.4 on '24 SU1.

Dear Developers, I found multiple references that the C/L menu and its items should be scrollable by the scroll wheel located on the KCCU. Also there seems to be a problem with the blue selection box NOT jumping to the next checklist items once validated. There are also Lvars available that indicate that this should be able to be done but no matter what I tried and bound it to, I was unable to scroll with the scroll wheel on the checklist. Please see my references from an FCOM below. 1) Reference for scroll wheel - should work for the checklist too. 2) Blue Selection Box - Should jump to the next item on the checklist automatica…

Hi, It seems that I'm encountering a bug in the step climb process during my flight. Here are the step I did to encounter this problem : - Load OFP with simbrief. Two step climb were planned as followed : From FL350 to FL370 @DASPA, from FL370 to FL390 @MOGDU - Everything was setup during the flight but ~1h before the step climb, I have the message STEP DELETED - Only the last one MOGDU is still there. - Managed to delete it and re-enter the other one but everytime it gets deleted. When I enter the two steps, only the last one remains. I also searched for different way to keep it but none of them seems to work. However I checked the wind data and only the on…

Dear iniBuilds Team, After activation of SEC1 F-PLN the Waypoints are not visible on the ND. They're only visibile during insertion of FROM P.POS DIR TO. (See Pictures).

The Ailerons banks the aircraft to the right side when the Autopilot is engaged. It is following the cours normal but with a right bank of a few degrees bank. I had disengaed AP and engaged it again already and restarted SIM und PC but it comes always back.

Was trying to inser pilot waypoint ETP1 as per attached route. When clicked Store Waypoint it crashed. Navigraph airac2503 A350-900 FS2020 i9 14900K rtx 3060 32GB RAM OMDBVRMM_PDF_1742457740.pdf

Hello, The STANDBY NAVIGATION DISPLAY isn’t working. No action is possible via the buttons. The ISIS on the left is slightly better, but it’s definitely not a hardcore modelization or study-level simulation. Could you please fix this? Thanks

Hi While enjoying my first nightflight i dimmed the main center display (engine indicating etc) to much but can not find the knob to increase the brightness again. All the other display have one knob to decrease and on to increase the brighness but on the center one is only one that decreases?

I have assigned Secondary- and Tertiary Action from Cockpit Interaction Controller Setup to VR-Controller Buttons to enable Push/Pull Functions of MCP Knobs in MSFS2020. The Push/Pull works fine for HDG but does not work at all for Speed/Baro/Altitude/VS Knobs. Mouse is working correctly.

Hello, Yes I have my rudder pedals set to control the tiller in the options menu. The nose gear turns left and right but the aircraft will not. My A350 continues in a straight line regardless of the amount of input and the directional angle of the nose wheels. I am using MSFS2020. Regards, Steve.

(1) Airway W34 ORAVA-UNSEK Route generated strangely

What is the purpose of these doors? are these supposed to be opend during fligth? Please refer to the doors right at the letter "E"

The A350 is in many ways a switch in FS simulation. Going from the solid, old-school aircraft to a seriously modern sophisticated airliner. Difficult to simulate and replicate. I am mighty impressed by the Inibuild team. Yes, there will be teething problems initially. Feedback and information will assist in enhancing this product. The FMS on the real thing has over 70 pages, they got most of them working. That by itself is impressive. With time, feedback from the community and tweaks will undoubtedly mark this as one of the best and advanced products ever created for MSFS. Keep up the good work Inibuild. Tweak it, listen to the feedback and make this thing shi…

Hi, when I started descending, when turning the nose t.o light, just passing to taxi, the cabin glow, as you can see in the picture added. I'm not sure what happened, but after some miles, I guess below 10k (but I'm not sure), the cabin glow disappeared and started looking normal. I don't think it's normal behavior, but I'll let you know about this issue. Note: not sure if related, but in the same flight (I'm running the latest update installed today), without any reason, I have several overspeed warnings)

In the pic below, the MORA appears to be inconsistent between the captain's and f/o's NSs. Captain's side has range of 320nm, and is showing 1000, whereas F/O's range is 40nm and showing 1800. Shouldn't the captain's side show 1800 as well? edit: Oops - should be in 2024 forum.