[A350 1.0.11] [Navigraph] Incorrectly drawn flight paths, incorrect waypoints, loss of nav data & Unable to enter Departure & Destination.

[Liamr685]

All,

There seems to be an issue with the Navigraph data that is downloaded through the OIS.

Firstly:

When entering route LEMG/13 BLN5H BLN N865 VTB N867 BLV P87 BELEN DCT DIDIG UP87 MOKOR UN873 OLEBA DCT ROGPU DCT DIKRO UM185 TELTU TELT1N EGGW/25.

The route uses incorrect waypoints and draws a crazy flight path.

As you can see below;

However, the flight path is supposed to look like the below.

 

Whilst fault finding this, I changed the nav data source from Navigraph, back to sim default Which, as updated via Navigraph hub, is also the same cycle (2505r1)
After changing the nav data source, and entering the above route, it draws the correct route, with the correct waypoints.

 

As shown in both cockpit images, you can see that I have swapped between Navigraph, and sim default, with both being cycle 2505r1.

 

To further test this, i entered the exact same route in the iFly 737 MAX, which is updated directly from Navigraph Hub, to the aircraft, and doesnt utilise the sim default cycle.

As predicted, it drew the correct routing.

 

This leaves me to beleive there is an issue with the way Navigraph data is implemented within the A350 via the OIS.

 

This would also explain the inability to enter flight data or request routes from simbrief, that I, and others have been experiencing in this thread;

 

Because, when I load the aircraft, and i am unable to enter the data, if i switch back to sim default in the ois...it then allows me to enter the data that was previously vanishing.

 

I have mentioned this a couple of comments down on the navigraph forum here;

https://forum.navigraph.com/t/2505-blv-sim-freeze/19803

Who directed me to post here, as this issue is an inibuilds problem with the way the A350 draws data from Navigraph, and not themselves.

[Liamr685]

1.0.12 still has this issue with the latest cycle.

 

some places it isn’t drawing the flight path on approach to airports, and giving incorrect vertical profiles on approach.

For example, ELVO1M into 23R at EGCC, has a profile that will cause a CFIT around 15 mile before turning onto final and intercepting the ILS.