BoeingSpeedbird

My solution (or this might be normal procedure?) is to not select the activate approach phase on MCDU if intending to use selected speeds through flaps 1-2. I suspect if you activate approach phase on MCDU before selecting ‘selected’ speeds through flaps 1-2 that the ‘selected’ speeds disarm the prior activation phase on MCDU, which you can’t reactivate later. So, what works is this: selected speeds and flaps 1-2; gear down; activate approach phase MCDU; then command speeds to follow flaps 3-full automatically.

Do you have a flight plan loaded and nav green in the FMA and flight directors on?

Am I missing a volume control or does the cabin call button make no sound? Also, what is the function of the loud speaker volume dial beside the avionics brightness dials?

I only ask as there are some videos of approach mode being activated but not approach phase.

Did you activate approach phase in MCDU and make sure flight plan is sequenced?

Noticed tonight that if you start cold and dark then the pedestal lighting on the FO’s side does work (no other lighting does as identified in other threads). Conversely, if you load in and start on a departure runway, then the FO pedestal lighting doesn’t work.

Using selected speed and flaps to initiate initial approach, then with gear down and selecting flap 3 I’ll then go back to managed speed to reduce workload (this is what I’ve seen in videos). However, flaps 3 and 4 don’t ever reduce speed to Vapp speed as shown in MCDU, so unless I go back to selected speed I’ll come in too fast. What am I doing wrong? Is this something to do with the timing of when you activate approach phase on the MCDU - if activate and then go selected (for flaps 1&2), can you then not get back into approach phase on MCDU to coordinate speeds and automatically manage speeds for flaps 3&4?

When the FMA commands Thrust Climb are you moving the throttles into Climb detent?

Sorry - didn’t read that bit.

Toggle GPU in the EFB?

Can happen if FD isn’t selected.

I have similar problem, except on Xbox with A320 and mostly on short final. I’m suspecting either a problem with the new airac cycle (no problems prior to last update) and/or some conflict with addon airport data and sim software. Other possibilities are sudden insert of weather data that throws the plane out of AP or drift on your flight controller that suddenly registers beyond a critical point and might require some increase in dead zone. Still working the problem at this end.

Loaded into EGPH at departure gate. Started to load flight plan into MCDU from Simbrief and MCDU frozen - cannot select or input anything. Having to restart MSFS2020 again. Frustrating.

PTU?

Engine manual start buttons?

Speed brakes won’t fully deploy in flight with AP on, they will only go to half way.

I’ve experienced this. They do eventually start (at least this was my experience), but take far longer than normal cold and dark start time.

On final approach to EGPH the plane made a sudden and extreme bank to the left, which was non-recoverable. Never happened before. Seems to correlate with numerous bugs over last two weeks (e.g., screens freezing in flight; mouse freezing in flight), which are things that haven’t happened before. Could this be related to latest airac update?