Bug - MCDU-created flight route doesn't display properly after landing

[linguisticmind]

Describe the bug
Similar to #324, but this seems to be purely a display issue.
Create a flightplan through the MCDU, fly it and land at the destination airport. Then, within the same session, create a new flightplan in the same way.
The new route doesn't show up on the navigation display or in the FlightGear's built-in map. However, the way points are still visible on the FlightGear's built-in map, and the aircraft is able to fly the route.
I recorded a video to demonstrate: https://youtu.be/vI6nnu0-5kc

To Reproduce
Steps to reproduce the behaviour:

1. Start up the aircraft (e.g. with the "Ready for Takeoff" preset)
2. Create a flightplan though the MCDU
3. Fly the route and land at the destination
4. Without ending the session, INIT a new FROM/TO in the MCDU, and create a new flightplan
5. Take a look at the navigation display and the FlightGear's built-in map to see the issue

Expected behaviour
The new route showing up correctly.

Screenshots
I recorded a video: https://youtu.be/vI6nnu0-5kc

System (please complete the following information):

• OS: Debian Stable (12, Bookworm)
• FlightGear version: 2020.3.19
• A320 Version: dev, 5264569

Additional context
I also noticed that even though the "Ready for Takeoff" preset now fills in the V1/VR/V2 speeds for you, they get erased if you press INIT in the MCDU. I don't know if that's intentional.
Also, in the video mentioned above, after I landed and created a new flightplan, I forgot to fill in the speeds (the "T.O. SPEEDS NOT INSERTED" ECAM message showed up), but the audible V1 announcement was still heard. Link to the part of the video when that happened: https://youtu.be/vI6nnu0-5kc&t=8m54s

[Octal450]

Hmm noted.