I used to plan my VFR flights in Plan-G, export them (.pln for FSX/P3D), then import into P2A.

In 2.6.2.3 R2 this isn't possible, I get message "Unable to import flight plan. Please ensure it is the proper form".
So I did some tests exporting and importing between Plan-G, Littlenavmap, P2A.
While I could import anything in Plan-G and Littlenavmap (the last with warnings about "missing starting point" = runway),
I could import no newer flight plans in P2A.

I thought to create a topic in the Plan-G forum, but then I created a short flight plan with three points LFMR - LFNA - LFNC in P2A,
exported it there as P3D .pln and did a re-export of this .pln in P2A and got the same error.

In the P2A_2020_Trace files, I see entries of the same type:

Error in BuildFPRoute
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at P2A_2020.FltPlan.BuildFPRoute(Boolean CalcTOD)
Error in FltPlan ImportFromP3DFile RteType
System.NullReferenceException: Object reference not set to an instance of an object.
   at P2A_2020.FltPlan.ImportFromP3DFile(String filePath)

More strange: I can import older Plan-G flight plans into P2A

So where to look what's wrong ? P2A, Plan-G, Littlenavmap ?
Or a mixture of all of them as they get new functionalities with each release ?
But in P3D (4.5 HF2), I can import all of my test exported .pln files.
Is P2A a little bit to harsh while checking the import ?

(I prefer Plan-G for VFR initial flight plan creation because of its bigger OpenTopo map).

If you email some of the files that are not importing into P2A to [email protected], I will have a look and see what might be going wrong.

Dave

After I found that .pln files are simple xml files, I was able to do some research on the generated .pln files with Notepad++.

If I add an airport as an intermediate waypoint, importing the .pln file in P2A results in an error, no matter what flight planner I used to export (loading the native P2A format .vbs works indeed). Just a sample:

LFNC - LFNA (airport as intermediate waypoint) - LFNC throws error:

...
<ATCWaypoint id="LFMR">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N44° 23' 14",E6° 36' 33",+003714.00</WorldPosition>
<ICAO>
<ICAOIdent>LFMR</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="LFNA">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N44° 27' 14",E6° 2' 12",+001966.00</WorldPosition>
<ICAO>
<ICAOIdent>LFNA</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="LFNC">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N44° 42' 1.99",E6° 35' 57",+002963.00</WorldPosition>
<ICAO>
<ICAOIdent>LFNC</ICAOIdent>
</ICAO>
...

LFNC - OKTET (waypoint) - LFNC works:

...
<ATCWaypoint id="LFMR">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N44° 23' 14",E6° 36' 33",+003714.00</WorldPosition>
<ICAO>
<ICAOIdent>LFMR</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="OKTET">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N44° 29' 6",E6° 34' 10",+000000.00</WorldPosition>
<ICAO>
<ICAOIdent>OKTET</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="LFNC">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N44° 42' 1.99",E6° 35' 57",+002963.00</WorldPosition>
<ICAO>
<ICAOIdent>LFNC</ICAOIdent>
</ICAO>
...

I proofed this against more complex flight plans in which I replaced the intermediate airports by navaids (manually in Notepad++, afterwards in several flight planners and P2A itself), the generated .pln files are taken by P2A import as soon as the last intermediate airport is replaced by a navaid or waypoint.

I remember that I was able to import such flight plans with "intermediate airports" formerly in P2A, but I don't know in what version as I didn't install every update.

 

If you email me the actual flight plan file, I will have a look.

Dave