Systems

Let me frame this one by saying that I am much more familiar with the Honeywell FMGC from my flying days, so I am not definitely saying this is a bug. However... Here the (SPD) (LIM) pseudo-waypoint is shown despite there being a restriction of 250kts on the STAR before the aircraft would normally decelerate to meet the 250kts @ 10,000ft restriction. In this case, the aircraft will never decelerate to met the 250@10000 restriction as it will already have decelerated to slow for the restriction at D356T at FL139. Therefore, I would not expect the (SPD) (LIM) pseudo-waypoint to be shown on the F-PLN page, nor a magenta change of speed dot to be shown on the ND. I w…

Hello, this problem is also present on the A350, but it wasn't the case in its earlier versions (I don't remember which version). After takeoff, there is always a sudden abrupt pitch movement and I think it coincides with the moment at which the FBW transitions from Ground law to Flight law. Could you please fix this on both aircrafts ? Thanks.

This state is typically used, if you start APU by batteries. Provided they are both selected AUTO, batteries supply the : ‐ DC ESS BUS ‐ DC BAT BUS ‐ DC LAND RECOVERY (whatever the position of the LAND RECOVERY pushbutton) And, through the static inverter, the : ‐ AC ESS BUS, and ‐ AC ESS GND ‐ AC LAND RECOVERY (whatever the LAND RECOVERY pushbutton position is) The AC ESS SHED, the DC ESS SHED and the SHED LAND RECOVERY are not supplied. ———————————————————— Systems: - RMP2 and 3 shouldn't be powered - ACP3 shouldn't be powered - MCDU3 should be powered———————————————————— ECAM: - missing amber lines between BATs and DC E…

Hello, creating a time marker creates a "weird" waypoint at hundred miles away. Is it normal ? Does the simulated firmware allow Time Markers to be created ?

WASM crash while approaching and mid flight the aircraft Freeze i cant take control of the aircraft at all this happend in a 7 hours flight and a 10 hours flight please help as soon as possible this happens also in the a350 for both MSFS2020 and 2024

Hello, Please find in this message my bug report with video evidence. Video: https://medal.tv/nl/games/microsoft-flight-simulator-2024/clips/lvqkZwrEJuQbgbhgD?invite=cr-MSxiWVcsMzA1Mzc3ODA2&v=210 How to recreate: A340 on ILS 25L in EDDF, initiate a Go-Around, then direct CHA (Charlie). WASM crashed completely, no response in MCDU, PFD and ND stuck. Autopilot kept the aircraft in a left bank while descending into the ground. Hope it helps. Kind regards, William Arnauts

When setting a Preselect speed in the PERF CLB page, it seems to respect it (per the FMA) but as soon as you enter climb mode, it gets replaced/overridden by the Managed FMS speed.

Company MSG should only be displayed for anything inside AOC. ATC messages (like CPDLC) shouldn't trigger that Memo.

Hello, the aircraft doesn't respect the acceleration altitude when entered manually in the PERF / TAKEOFF page. It always accelerate at the same time as the thrust reduction. In the following case, it accelerated at 2000ft instead of 3500.

- EFOB and EXTRA for VERT REV of Destiantion are not matching FUEL PRED/INIT B during preflight - LSK2L has to show a magenta default small font 250/10000 for CLB and DES SPD LIM. You show it in the F-PN but have it not in the VERT REV page...that's not logical ! - LSK3L SPD CSTR brackets have to be large font - LSK2R is missing RTA>s

Hello, after a 10 hours flight, it is impossible to get 0 GS displayed on the NDs. There should be a residual 2-3 Kts because of the IRS drift. So I investigated further and checked the DATA / POSITION MONITOR page and it shows 0.1 NM error for the 3 IRSs which is also totaly impossible after 10 hours of flight. Could you add some drift to the IRSs to reflect more reality ? Below is a table of the acceptable drifts vs flight time.

Users like Der Michel, Hélène or Dectenor2 (I forget other good ones) make a great job with reporting bugs. Let me please advise all users to precise on their reports if the bugs are also concerning other IniBuilds aircrafts. By this way we can expect that a dev will apply the same correction on the fleet.

Hello, did a FAOR -> FACT and return without powering down the aircraft. Everything fine during the first flight. However, during return flight preparation, the FMGS displayed a weird total FPL distance (screenshot attached). Distance went back ok during initial climbout.

Hello, please review the Flight Directors ground engagement logic. First, as I said in a previous post, they should be always ON when the FMGCs are powered up. Also, in normal "managed" conditions, before applying takeoff power, the FMA should display "CLB" blue instead of V/S 0 green. The FCU windows should all display "dashes". See FCOM 1.22.30 for more details. SIM : REALITY:

Hello, during a HOLD, pressing LSK 1R "IMMEDIATE EXIT" should turn the aircraft directly to the Holding Fix while remaining within the protected area. Instead of doing this, the aircraft continues the Hold normally and exits when reaching the fix. See the below screenshot taken after pressing IMMEDIATE EXIT. I draw in blue what the aircraft SHOULD do and draw on the ND, but instead it continued to fly the HOLD until the fix.

When loading the aircraft, even without GSX and just using Instant Load, the aircraft does not import the correct planned ZFW. You can see the difference between PLAN and LIVE.

There is a discrepancy between the target speeds on the F-PLN page and the PERF pages. For example here, The F-PLN page shows the descent and .76 and then 288 on conversion, whereas the DES page shows .79 and 289 on conversion.

Hello, there is no trans alt/std alert ?

The PRED TO values on the CLB PERF page is incorrect. As can be seen on the ND we are just under 40nm away from TOC (FL400), but the PRED TO FL400 on the CLB PERF page is showing 560nm, basically same distance as the entire route. And also the predicted UTC time, is the same as the destination. It seems to work for custom entered altitudes, but when left at the default FCU selected Altitude it is just showing the total remaining flight distance and time.

The constraint logic needs some work. Here you can see the aircraft is indicating it will be at FF24L at 2500ft. You can see in the second capture, that the constraint here is AT 2500. So it is incorrect that the aircraft should indicate this constraint will not be met.

1. Dashes have to be ALWAYS !!! white (large font) and the correct format is: ----.--/-----.-- 2. LSK6R: SEL has to be in small font 3. Line 5: OFF, ALIGN, NAV x.x has to be in small font 4. LSK3L label depends on availability of GPS

1. LSK3L remove the space behind ILS

Hello, I noticed the FDs are always OFF after powering the aircraft from a Cold and Dark state. According to the FCOM 1.22.30 it should not be the case.

Hello, This happens after every pushback with GSX with the A340. Who can help me?

Hi, this will be the start of a series of topics regarding issues with the FMS pages. Still the work assumes that ini switched from P4 to P3 since update 1.02. Please change the menu layout. You already replaced ACARS with ATSU at LSK2L. But if ATSU is used it has to be at LSK6L. Also add LSK5L SAT for airplanes equipped with SAT.