The logic for the behavior of the speed bugs and FMA during takeoff are not matching the real plane.
Expected behaviour
This all applies BEFORE FMS SPD is engaged.
White airspeed selection in FMA and the bug on the tape should only show when the V2 speed is manually overriden/entered by pilot (white V speed boxes) as shown:
In this case, LHC has the pilots enter the speeds overriding what the MCDU is showing, hence the white boxes.
When the V2 speed is calc by the FMS and confirmed (magenta boxes), magenta indications are used similar to FMS speed:
I apologize for the poor quality picture. You can see the FMA speed target is magenta, and the filled magenta circle appears next to the V2 bug. The boxes are shown as magenta here, showing pilot confirmed FMS calculations.
Evidence
Here is TFDi version 59.02. Speeds calculated by FMS and confirmed by MCDU, magenta boxes. But the FMA speed target is white and the selected bug is appearing instead.
Describe the bug
The logic for the behavior of the speed bugs and FMA during takeoff are not matching the real plane.
Expected behaviour
This all applies BEFORE FMS SPD is engaged. White airspeed selection in FMA and the bug on the tape should only show when the V2 speed is manually overriden/entered by pilot (white V speed boxes) as shown: In this case, LHC has the pilots enter the speeds overriding what the MCDU is showing, hence the white boxes.
When the V2 speed is calc by the FMS and confirmed (magenta boxes), magenta indications are used similar to FMS speed: I apologize for the poor quality picture. You can see the FMA speed target is magenta, and the filled magenta circle appears next to the V2 bug. The boxes are shown as magenta here, showing pilot confirmed FMS calculations.
Evidence
Here is TFDi version 59.02. Speeds calculated by FMS and confirmed by MCDU, magenta boxes. But the FMA speed target is white and the selected bug is appearing instead.
Simulator
Microsoft Flight Simulator 2020 (MSFS)
Crash
No
Agreement