Andrew M

I think the most significant screen we want to be clickable is the MFD. Why is the OIS clickable but the MFD is not, and/or how is the MFD a WASM gauge?

Thanks. Any AFS selection should be cancelling the EMER DES, or activation and subsequent deactivation via the PB SW should stop it too.

Thanks for a response. Yes, I just tried again. The aircraft is unflyable in this condition where a high grid MORA is preventing a descent below 10000ft, such as over China on the Y1 airway. Auto emer descent can't be turned off, and subsequently can't initiate an appropriate diversion to lower terrain. It's not following the real-life system logic.

Bumping for a response from inibuilds

Bumping for a response from inibuilds

Braking issues still remain.

Anyone?

Minicockpit FCU and EFIS control, Winwing stick, MCDU and AGP. Several Stream Deck units. This has been an issue for me ever since I purchased the A350 on day one of its release.

Has anyone had issues getting the aircraft to brake when all engines are inoperative? Brake pressure shows on the system display however the aircraft doesn't slow down, even with autobrake. There's no indication showing either in this scenario of whether the braking is in normal, alternate or emergency modes either, nor does the braking pressure really indicate whether the braking is being modulated through accumulator pressure.

I've noticed issue with the auto emergency descent logic where I'm unable to disarm the function. Usually by pressing the arm function twice (if automatically activated) or once (if manually activated) I should be able to disarm the function and complete the emergency descent manually and as desired, but the auto function keeps activating and prohibiting me from manually selecting a desired heading and altitude. Has anyone else been having issues? WhatsApp Video 2025-12-26 at 8.10.58 AM.mp4

I have found that by mapping a key to the ECAM tick release can prevent the issue, provided the tick release is actuated prior to any checklist. If the release hasn't occurred at least once prior, the issue remains.

I've checked hardware binding and confirmed that it's not an issue with the ECAM item being ticked unaware, also demonstrated that activating the item in the Abnormal checklist requires it actively being ticked. A re-install also has not resolved the problem either.

Also tested on v1.2.0 and the issue still exists.

Has anyone had similar issue?

GIF of the issue Additionally, unable to deactivate abnormal ECAM's, therefore leaving incorrect deferred ECAM procedures.