Doyler

Looks like you’re running into the classic AP in Prot situation that comes up when the A350 logic is forcing alpha protection, usually triggered because the aircraft is flying too close to stall speed relative to its weight and altitude. From what I’ve seen, this often isn’t about the AP failing, but about the climb profile itself: if the managed climb keeps you at too high a pitch for the current gross weight, the system basically prioritizes avoiding a stall over holding your climb. What helped me in similar cases was stepping the climb instead of trying to go straight to FL380, and manually monitoring speed so it doesn’t fall into that protection zone. It feels less like a bug and more like the FMGS being a little too rigid with heavy loads

I ended up switching to the PC version just to see if 1.1.6 really fixed those issues, and it did which makes it even more frustrating that the Xbox marketplace is stuck on 1.1.5. At this point it’s less about the aircraft itself and more about how unreliable the whole update pipeline feels on console.

Sometimes the issue isn’t the button itself but the flight plan integrity so if there’s a discontinuity or the next waypoint isn’t properly sequenced, NAV mode won’t capture even if you re-press it. I’ve had to clean up the MCDU first before the managed mode would respond again

Hi, If you still need a fix, the issue isn’t the PFD itself but the ND sources not drawing. On the Airbus setup those layers (WX TCAS TERR) only show on the Navigation Display, so if you’re seeing different black on the PFD it usually means the display unit mapping or brightness/gain controls on the pedestal aren’t aligned. Double check that the radar panel has WX/TERR switched to ON and that TCAS is set to TA/RA. Otherwise the overlay just stays blank regardless of what the PFD background looks like

Hi, I’ve run into the same on RNAVs, and what helped me at least partly was double checkin if the aircraft actually switched from NAV to FINAL APP mode on the FMA, sometimes it looks armed but never transitions if managed speed isn’t active