The A32NX & A380X Project are community driven open source projects to create free Airbus aircraft in Microsoft Flight Simulator that are as close to reality as possible.
In fact, I have encounter several problems during this flight:
LFKJ SID LONS5H20 to LSGG ILS22 STAR FRI2T
This is what FS2020 flight planner give:
LFKJ>D1>IS>LONSU>EBOLA>PIGOS>FRI>ROMOM>SPR>GG811>PETAL>GG808>LSGG
The following image show the flight plan into MSFS editor
ERRORS INTO FBW FLIGHTPLAN
On next image, you can see that 2 waypoint are missing: EBORA and PIGOS
On next image, you can see that PETAL is duplicated, that SPR has a wrong altitude (It should be 7000), that GVA has nothing to do in this flight plan.
On next image, you can see the drawing flight plan path anomalies, generated by the previous problems.
DURING THE FLIGHT
On next image, you can see a strange event I never had before. While I was flying to "IS" from "D1", I had a strange double turn drawing a "S" with the two circular parts growing, until I got this "MAP PARTLY DISPLAYED" warning, with the lost of my guidance (aircraft continued straight forward).
Using DIRECT TO, I was able to restore my normal flying to LONSU and the good news is that I was able to fly the rest of the flight without any further FBW problem. I respected the (DECEL) and even the FLAP1 and FLAP2 indication. To my taste, it was hot. I mean no much margins and I had to use airbrakes, but it worked. Great !
Of course, before takeoff, I have suppressed all anomalies described before.
Expected behavior
A correct flight plan into the MCDU
No "MAP PARTLY DISPLAYED" disconnection.
Aircraft Version
Experimental
Build info
Describe the bug
In fact, I have encounter several problems during this flight: LFKJ SID LONS5H20 to LSGG ILS22 STAR FRI2T This is what FS2020 flight planner give: LFKJ>D1>IS>LONSU>EBOLA>PIGOS>FRI>ROMOM>SPR>GG811>PETAL>GG808>LSGG The following image show the flight plan into MSFS editor
ERRORS INTO FBW FLIGHTPLAN On next image, you can see that 2 waypoint are missing: EBORA and PIGOS
On next image, you can see that PETAL is duplicated, that SPR has a wrong altitude (It should be 7000), that GVA has nothing to do in this flight plan.
On next image, you can see the drawing flight plan path anomalies, generated by the previous problems.
DURING THE FLIGHT On next image, you can see a strange event I never had before. While I was flying to "IS" from "D1", I had a strange double turn drawing a "S" with the two circular parts growing, until I got this "MAP PARTLY DISPLAYED" warning, with the lost of my guidance (aircraft continued straight forward).
Using DIRECT TO, I was able to restore my normal flying to LONSU and the good news is that I was able to fly the rest of the flight without any further FBW problem. I respected the (DECEL) and even the FLAP1 and FLAP2 indication. To my taste, it was hot. I mean no much margins and I had to use airbrakes, but it worked. Great !
Of course, before takeoff, I have suppressed all anomalies described before.
Expected behavior
A correct flight plan into the MCDU No "MAP PARTLY DISPLAYED" disconnection.
Steps to reproduce
Probably, just redo the same flight
References (optional)
No response
Discord Username (optional)
No response