Interesting plan.
It does not crash for me (using 3.2.0) when entering an alternate in PF3, but most of the waypoints don't show up.
I assume this is because they don't have an <ICAOIdent> value, for example:
<ATCWaypoint id="DUTUM">
<ATCWaypointType>User</ATCWaypointType>
<WorldPosition>N63° 52' 01.20",W67° 0' 00.00",+000000.00</WorldPosition>
<Descr>DUTUM</Descr>
</ATCWaypoint>
<ATCWaypoint id="6465N">
<ATCWaypointType>User</ATCWaypointType>
<WorldPosition>N64° 0' 00.00",W65° 0' 00.00",+000000.00</WorldPosition>
<Descr>6465N</Descr>
</ATCWaypoint> |
If I create own waypoints with PFPX, they look like this and work fine with PF3:
<ATCWaypoint id="52N008E">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N52° 17' 00.00",E007° 49' 00.00",+000000.00</WorldPosition>
<ICAO>
<ICAOIdent>52N008E</ICAOIdent>
</ICAO>
</ATCWaypoint>
|
Other software doesn't seem to like such flight plans either, see e.g.
http://www.tasoftware.co.uk/forum/index ... pic=1979.0
Jeff, can you adjust the .pln file to have ICAO and ICAOIdent (or just don't use user waypoints for this test)?
Does it still crash with 3.2.0?
Dave, can you make PF3 fall back to using <Descr> if <ICAOIdent> isn't available?