Loading P3D flight plan pln file does not work correct

[pumsti 0]

Hello,

I have imported the P3d .pln file below into Pilot2Atc by the "Impt" button.

I have loaded the same file into p3d and all waypoints are displayed correct there

(LOAV,SV001(user waypoint),TF(NDB),LOGP)

Result in Pilot2Atc after loading the file (showing only the airport waypoints and a generated TOD)

LOAV VOSLAU

TOD PT ----

LOGP PINKAFELD

(I did not found an option to upload a screenschote or attachment here)

 

This is a user waypoint created within P3D V4.4 and can not be read by Pilot2Atc

 <ATCWaypoint id="WP1">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N47° 40' 57.422706",E16° 12' 21.330246",+005000.00</WorldPosition>
  </ATCWaypoint>

This is a user waypoint created by my hand and is reading by Pilot2Atc

<ATCWaypoint id="SV001">
            <WorldPosition>N47° 53' 49.671163",E16° 13' 48.039600",+005000.00</WorldPosition>
 </ATCWaypoint>

P3D v4.4 will also read coordinates in decimal format

Application which writes their exports with decimal coordinates to the ".pln" format will not work in Pilot2Atc

 

It would be great if you are able to improve the compartibility to the pln format.  If so I would like to write a tool for exporting and importing flight planes for the Flight1 GTN using "pln" format as intermediate format, so i can create my short flight plane within Flight1 GPS and exporting it to Pilot2Atc, getting ATC

 

Thanks and best regards

 

LOAV_LOGP.pln

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="AceXML" version="1,0">
<Descr>Import plan from Skyvector</Descr>
<FlightPlan.FlightPlan>
<Title>
</Title>
<FPType>VFR</FPType>
<RouteType>LowAlt</RouteType>
<CruisingAlt>5000</CruisingAlt>
<DepartureID>LOAV</DepartureID>
<DepartureLLA>47.964444 , 16.259444,+765.0</DepartureLLA>
<DestinationID>LOGP</DestinationID>
<DestinationLLA>47.387778 , 16.110833,+</DestinationLLA>
<Descr>LOAV, LOGP</Descr>
<DeparturePosition>08</DeparturePosition>
<DepartureName>LOAV</DepartureName>
<DestinationName>LOGP</DestinationName>
<AppVersion>
<AppVersionMajor>10</AppVersionMajor>
<AppVersionBuild>3000</AppVersionBuild>
</AppVersion>
<ATCWaypoint id="LOAV">
<ATCWaypointType>AIRPORT</ATCWaypointType>
<WorldPosition>47.964444 , 16.259444,+765.0</WorldPosition>
<ICAO>
<ICAORegion>LO</ICAORegion>
<ICAOIdent>LOAV</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="SV001">
<ATCWaypointType>User</ATCWaypointType>
<WorldPosition>47.897133 , 16.230011,+5000</WorldPosition>
<ICAO>
<ICAORegion>
</ICAORegion>
<ICAOIdent>SV001</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="TF">
<ATCWaypointType>NDB</ATCWaypointType>
<WorldPosition>47.840997 , 16.281731,+5000</WorldPosition>
<ICAO>
<ICAORegion>LO</ICAORegion>
<ICAOIdent>TF</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="LOGP">
<ATCWaypointType>AIRPORT</ATCWaypointType>
<WorldPosition>47.387778 , 16.110833,+</WorldPosition>
<ICAO>
<ICAORegion>LO</ICAORegion>
<ICAOIdent>LOGP</ICAOIdent>
</ICAO>
</ATCWaypoint>
</FlightPlan.FlightPlan>
</SimBase.Document>

 

 

 

 

Spoiler

 

 

Edited January 3, 2019 by pumsti

[pumsti 0]

It seems the tag <AtcWaypointType> is ignored by Pilot2Atc. If Pilot2Atc  has found a valid Waypoint id into the tag <ATCWaypoint id> it use it even though completely different from the defined world position and defined Waypoint type

I also created a minimal flight plan with two user points by Pilot2Atc and exported it as .pln file.

This created "pln file" can not be read by P3D.

Should the import and export to .pln files work, even there are user defined waypoints in it ?

Thanks and best regards

Edited January 3, 2019 by pumsti