Flight Plan Structure

[hanksterman00]

Noticed with the later versions of P3d v5 and now v6 that their are additional xml tags in flight plan files that populate when a plan is loaded. I have always used LittleNavmap to create plans and have never seen these tags before. On search I have found no info. In that they are not there when the plan is first created, they are there after the plan is loaded from P3d flight planner thereafter. Also, the index values of these seem to randomize on each load a seem to be the source of long loading times. I have p3d v6.0.30.30926 professional installed. Looking for definitions for these tags and what values they should be populated with. Latest P3d help file makes no mention of these. All tags in question are highlighted yellow

<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="6,0">
<Descr>AceXML Document</Descr>
<FlightPlan.FlightPlan>
<Title>KBFM to KMSY</Title>
<FPType>IFR</FPType>
<RouteType>LowAlt</RouteType>
<CruisingAlt>10000</CruisingAlt>
<DepartureID>KBFM</DepartureID>
<DepartureLLA>N30° 38' 29.901714",W88° 3' 57.300000",+000026.00</DepartureLLA>
<DestinationID>KMSY</DestinationID>
<DestinationLLA>N29° 59' 35.792929",W90° 15' 32.490000",+000004.00</DestinationLLA>
<DeparturePosition>18</DeparturePosition>
<DepartureName>Mobile Downtown</DepartureName>
<DestinationName>Armstrong New Orleans Intl</DestinationName>
<DepartureIndex>-1</DepartureIndex>
<DepartureTransitionIndex>-1</DepartureTransitionIndex>
<DepartureRunwayTransitionIndex>-1</DepartureRunwayTransitionIndex>
<DepartureNextPoint>-1</DepartureNextPoint>
<ArrivalIndex>-1</ArrivalIndex>
<ArrivalTransitionIndex>-1</ArrivalTransitionIndex>
<ArrivalNextPoint>-1</ArrivalNextPoint>
<ApproachIndex>-1</ApproachIndex>
<ApproachTransitionIndex>-1</ApproachTransitionIndex>
<ApproachNextPoint>-1</ApproachNextPoint>
<AppVersion>
<AppVersionMajor>6</AppVersionMajor>
<AppVersionMinor>0</AppVersionMinor>
<AppVersionRevision>30</AppVersionRevision>
<AppVersionBuild>30926</AppVersionBuild>
</AppVersion>
<ATCWaypoint id="KBFM">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N30° 37' 35.240393",W88° 4' 4.800000",+000026.00</WorldPosition>
<ICAO>
<ICAOIdent>KBFM</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="HAGMO">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N30° 23' 58.028605",W88° 56' 1.070000",+004000.00</WorldPosition>
<ICAO>
<ICAORegion>K7</ICAORegion>
<ICAOIdent>HAGMO</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="IWDEG">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N30° 16' 18.838963",W90° 9' 34.910000",+004000.00</WorldPosition>
<ICAO>
<ICAORegion>K4</ICAORegion>
<ICAOIdent>IWDEG</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="SHORE">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N30° 2' 16.910301",W90° 14' 3.750000",+002318.69</WorldPosition>
<ICAO>
<ICAORegion>K4</ICAORegion>
<ICAOIdent>SHORE</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="YERUB">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N29° 57' 43.048626",W90° 15' 30.900000",+000661.65</WorldPosition>
<ICAO>
<ICAORegion>K4</ICAORegion>
<ICAOIdent>YERUB</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="KMSY">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N29° 59' 21.559787",W90° 15' 5.360000",+000004.00</WorldPosition>
<ICAO>
<ICAOIdent>KMSY</ICAOIdent>
</ICAO>
</ATCWaypoint>
</FlightPlan.FlightPlan>
</SimBase.Document>

[Rob McCarthy]

Hello,

We added support for departures, arrivals, and approaches in the flight planner for v6. These entries are to save that information into the flight plan. Procedures can be selected in the Flight Planner UI after selecting the airport. As far as loading times these should not impact them. Are you seeing differences when loading different pln files?

Regards,
Rob McCarthy

[hanksterman00]

Thank you for the reply. Without assuming , I have noticed that when any flight plan is loaded I seem to get different behavior each time. One thing that is consistent is that after selecting a plan from my saved plans that all select buttons lose focus and are not select able until the departure and destination fields populate with a value of none after some period of time. Other times I will get a finding route with a progress bar that varies in it's time of completion. I have not experienced a quick load of any plan since noticing these tag additions. That's the only reason I mentioned it initially.

[Martyson]

Hello hanksterman00 ,

“Noticed with the later versions of P3d v5 and now v6 that their are additional xml tags in flight plan files that populate when a plan is loaded.”

P3Dv5 is a different flight planner. No SIDs/ / STARS etc.

If you create a new flight plan in P3D6 and save it do you see any problem(s) the next time it is loaded?

Just to verify:
Are you loading previously saved P3D5 plans into P3D6 and seeing the problem(s).

[Martyson]

Hello hanksterman00 ,

As a quick test I copied a saved plan from the P3D5.4.9.28482 folder to P3D Personal Patch3 6.0.30.30926 folder (C:\Users\MyNamehere\Documents\Prepar3D v6 Files).

Started P3D6 Personal Patch3.

Selected the plan and it loaded in 1 second (screenshot).


I also loaded a recently created P3D6 plan into P3D6 and it loaded in one second (screenshot).

No problems noticed so far.
No buttons lost focus.

[hanksterman00]

I can confirm that when a flight plan is created with V6 that it loads quickly, about two seconds on my machine. If I try and use a flight plan that was previously created for V5 and then modified to match the xml structure of a V6 plan, that slow loading and button focus behavior occurs. The flight plan that I originally posted is an example of a plan that has been modified from V5 to match V6 structure.

[Martyson]

As I posted my flight plan from P3D5 loaded ok in P3d6..

I never modified any plan created in P3D5 before loading in P3D6.

[hanksterman00]

I have loaded flight plans created for V5 into V6 and they will automatically get the additional xml tags that V6 now uses. Same behavior, slow loading, button focus loss and finding route.

[Martyson]

I have loaded flight plans created for V5 into V6 and they will automatically get the additional xml tags that V6 now uses. Same behavior, slow loading, button focus loss and finding route.

Are you loading a P3D5 plan into P3D6 then saving it ?

Then inspecting the new plan to see the additional xml tags?
Then testing / loading the new P3D6 plan into a new P3D6 flight?

In my usage (screenshot) I just loaded a previously saved P3D5 flight plan into P3D6, nothing else.

[hanksterman00]

Yes. Loading and saving, exactly as you stated, then on inspection the new tags are present. When I load the plan again it exhibits the same behavior.

[Martyson]

Yes. Loading and saving, exactly as you stated, then on inspection the new tags are present. When I load the plan again it exhibits the same behavior.

Will need more information on what you are doing. Problem recreation steps.

I just tested and cannot save a flight plan from P3D5 when initially loaded into P3D6 (like my previous screenshot example).
No option to save it as it has not been modified.

My test:
P3D5.4.9.28482
P3D6 Personal Patch3

I started P3D6
Flight planner
Load
Browse to P3D5 files (or just select the P3D5 plan if previously moved from P3D5 to the P3D6 files folder).
Select and load the P3D5 plan. No option to save it at this point.
OK
When P3D6 finishes loading then save the new flight which also saved the new plan and weather files.
Exit P3D6
Reboot PC
If I now inspect the new flight plan in P3D6 it does have the new SID/STAR etc data as expected.
No editing required.
Start P3D6
Load the new flight (new plan included).
Load fast (10 seconds).
No problem.

[hanksterman00]

Confirmed. I cannot save a previously saved plan from v5 either. Going to give it my best shot so you can try and recreate what I am seeing. For the purpose of uniformity please try and use the plan example in this post. I start out by creating a plan in LittleNavmap which looks like this. Notice not even close to what a v6 plan looks like but has always worked up to v5

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="AceXML" version="1,0">
<Descr>AceXML Document</Descr>
<FlightPlan.FlightPlan>
<Title>KBFM to KMSY</Title>
<FPType>VFR</FPType>
<RouteType>Direct</RouteType>
<CruisingAlt>10000</CruisingAlt>
<DepartureID>KBFM</DepartureID>
<DepartureLLA>N30° 38' 29.91",W88° 3' 57.30",+000026.00</DepartureLLA>
<DestinationID>KMSY</DestinationID>
<DestinationLLA>N29° 59' 35.80",W90° 15' 32.49",+000004.00</DestinationLLA>
<Descr>KBFM, KMSY created by Little Navmap 2.8.12</Descr>
<DeparturePosition>18</DeparturePosition>
<DepartureName>Mobile Downtown</DepartureName>
<DestinationName>Armstrong New Orleans Intl</DestinationName>
<AppVersion>
<AppVersionMajor>10</AppVersionMajor>
<AppVersionBuild>61472</AppVersionBuild>
</AppVersion>
<ATCWaypoint id="KBFM">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N30° 37' 36.40",W88° 4' 5.10",+000026.00</WorldPosition>
<ICAO>
<ICAOIdent>KBFM</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="HAGMO">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N30° 23' 58.04",W88° 56' 1.07",+010000.00</WorldPosition>
<ICAO>
<ICAORegion>K7</ICAORegion>
<ICAOIdent>HAGMO</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="IWDEG">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N30° 16' 18.84",W90° 9' 34.91",+007046.72</WorldPosition>
<ICAO>
<ICAORegion>K4</ICAORegion>
<ICAOIdent>IWDEG</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="YERUB">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N29° 57' 43.06",W90° 15' 30.90",+000629.12</WorldPosition>
<ICAO>
<ICAORegion>K4</ICAORegion>
<ICAOIdent>YERUB</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="KMSY">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N29° 59' 35.80",W90° 15' 32.49",+000004.00</WorldPosition>
<ICAO>
<ICAOIdent>KMSY</ICAOIdent>
</ICAO>
</ATCWaypoint>
</FlightPlan.FlightPlan>
</SimBase.Document>

I then modify this plan to mimic a v6 plan exactly in it's structure. The only exception is I have placed the index values as -1 in the additional xml tags that v6 uses in a plan. This is the plan that I end up using after modifying the original. When loading this plan, be patient and watch how long the loading process takes and it's behavior in terms of lost button focus, finding route, only somtimes and the abilty to select ok after it is fully loaded. At least this is the behavior I experience. It is my sincere hope that you come back and say that this loads fine on your system, then we will know it's just me.

<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="6,0">
<Descr>AceXML Document</Descr>
<FlightPlan.FlightPlan>
<Title>KBFM to KMSY</Title>
<RouteType>LowAlt</RouteType>
<CruisingAlt>10000</CruisingAlt>
<DepartureID>KBFM</DepartureID>
<DepartureLLA>N30° 38' 29.91",W88° 3' 57.30",+000026.00</DepartureLLA>
<DestinationID>KMSY</DestinationID>
<DestinationLLA>N29° 59' 35.80",W90° 15' 32.49",+000004.00</DestinationLLA>
<DeparturePosition>18</DeparturePosition>
<DepartureName>Mobile Downtown</DepartureName>
<DestinationName>Armstrong New Orleans Intl</DestinationName>
<DepartureIndex>-1</DepartureIndex>
<DepartureTransitionIndex>-1</DepartureTransitionIndex>
<DepartureRunwayTransitionIndex>-1</DepartureRunwayTransitionIndex>
<DepartureNextPoint>-1</DepartureNextPoint>
<ArrivalIndex>-1</ArrivalIndex>
<ArrivalTransitionIndex>-1</ArrivalTransitionIndex>
<ArrivalNextPoint>-1</ArrivalNextPoint>
<ApproachIndex>-1</ApproachIndex>
<ApproachTransitionIndex>-1</ApproachTransitionIndex>
<ApproachNextPoint>-1</ApproachNextPoint>
<AppVersion>
<AppVersionMajor>6</AppVersionMajor>
<AppVersionMinor>0</AppVersionMinor>
<AppVersionRevision>30</AppVersionRevision>
<AppVersionBuild>30926</AppVersionBuild>
</AppVersion>
<ATCWaypoint id="KBFM">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N30° 37' 36.40",W88° 4' 5.10",+000026.00</WorldPosition>
<ICAO>
<ICAOIdent>KBFM</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="HAGMO">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N30° 23' 58.04",W88° 56' 1.07",+010000.00</WorldPosition>
<ICAO>
<ICAORegion>K7</ICAORegion>
<ICAOIdent>HAGMO</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="IWDEG">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N30° 16' 18.84",W90° 9' 34.91",+007022.67</WorldPosition>
<ICAO>
<ICAORegion>K4</ICAORegion>
<ICAOIdent>IWDEG</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="SHORE">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N30° 2' 16.94",W90° 14' 3.75",+002196.69</WorldPosition>
<ICAO>
<ICAORegion>K4</ICAORegion>
<ICAOIdent>SHORE</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="YERUB">
<ATCWaypointType>Intersection</ATCWaypointType>
<WorldPosition>N29° 57' 43.06",W90° 15' 30.90",+000626.99</WorldPosition>
<ICAO>
<ICAORegion>K4</ICAORegion>
<ICAOIdent>YERUB</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="KMSY">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N29° 59' 35.80",W90° 15' 32.49",+000004.00</WorldPosition>
<ICAO>
<ICAOIdent>KMSY</ICAOIdent>
</ICAO>
</ATCWaypoint>
</FlightPlan.FlightPlan>
</SimBase.Document>

[Martyson]

"I start out by creating a plan in LittleNavmap "

No, not for an initial test.

Start by creating a plan with P3D5.
Then test it in P3D6.

[hanksterman00]

I do not have an instance of v5 loaded and as stated have always used LittleNavmap to create plans which have worked perfectly up to v6. The second plan example is in the correct structure for v6 unless I am missing something. I do not believe I have though as I created a plan with v6 and
compared it to the second example. Not to get snarky here but the way I understand xml is that the application software looks at the tags and and uses the values that are within those tags.

[Martyson]

How long would it take to create a plan in P3D5 then reboot PC and test it (load it) into P3D6?