MIssing Tag in PLN file that has User Waypoints

Currently, in SU13 bet, and with Navigraph Nav Data installed

With Flight Planes generated from world map, User Waypoints all show to be located at the North Pole.

The same FPL generated by LNM adds in a dummy ICAOIdent for user waypoints that seems to correct this issue.

It seems if the ICAOIdet tag is misssing from a waypoint, that waypoint processing fails, and defaults to a North P0le Coordinate.

SO it is not clear if it is a MSFS issue or a Navigraph issue. but apart from the above, it should be noted that a FLight Plane generated and saved from the World Map, and the reloaded from that saved pln , and then saved again, is NOT the same as the original pln file. !!

From the sdk, part of a pln example with custom/user waypoints

> </AppVersion>
> <ATCWaypoint id="KVNY">
> 	<ATCWaypointType>Airport</ATCWaypointType>
> 	<WorldPosition>N34° 12' 36.57",W118° 29' 24.03",+000775.50</WorldPosition>
> 	<ICAO>
> 		<ICAOIdent>KVNY</ICAOIdent>
> 	</ICAO>
> </ATCWaypoint>
> <ATCWaypoint id="CUST0">
> 	<ATCWaypointType>User</ATCWaypointType>
> 	<WorldPosition>N34° 13' 16.8",W118° 28' 46",+001000.00</WorldPosition>
> 	<ICAO>
> 		<ICAOIdent>xxxxx</ICAOIdent>
> 	</ICAO>
> </ATCWaypoint>
> <ATCWaypoint id="CUST1">
> 	<ATCWaypointType>User</ATCWaypointType>
> 	<WorldPosition>N34° 13' 10",W118° 24' 14",+001000.00</WorldPosition>
> 	<ICAO>                                 <<<<<<<<<<<< ADDED
> 		<ICAOIdent>xxxxx</ICAOIdent>      <<<<<<<<<<<< ADDED
> 	</ICAO>                                 <<<<<<<<<<<< ADDED
> </ATCWaypoint>
> <ATCWaypoint id="KBUR">
> 	<ATCWaypointType>Airport</ATCWaypointType>
> 	<WorldPosition>N34° 12' 2.24",W118° 21' 30.61",+000722.50</WorldPosition>
> 	<ICAO>                                 <<<<<<<<<<<< ADDED
> 		<ICAOIdent>KBUR</ICAOIdent>    <<<<<<<<<<<< ADDED
> 	</ICAO>                                 <<<<<<<<<<<< ADDED
> </ATCWaypoint>
> </FlightPlan.FlightPlan>

added ICAOIdent tags added to correct the North Pole Issue


Even though this issue is Highlighted by adding in the Navigraph Nav Data, the whole Loading & saving from the wold map seems to be flawed, with or without the Navigarph database.

A work around (That should not be necessary) is to process any World Map generated Flight Plans through LNM, to correct this issue, but that is not perfect, as other information can get lost/corrupted in the PLN file by this process.

It probably need looking into by ASOBO a nd the SDK made clear how it should be, and the the World Map code made to work as specified in the SDK, and then hopefully Navigraph can more easily address the issue of North Pole positions with Navigraph.

Also Custom Waypoints ids – CUSTn or WPn ?? (which is better in Hindsight)