P3D5.4 Does Not See/Follow GPS Flight Plans

[howellerman]

Hi Tim.

Not sure if this is your bailiwick or not, but I thought I would draw upon your expertise.

The second bullet of the release notes for P3DV5.4 says:

Three additional backend flight plan GPS systems can now be integrated into aircraft allowing for staging, secondary, and offset flight plan systems.

This is all well and good, except that more than half my pre-defined Plan-G *.pln files appear to be "broken" in P3DV5.4. I can provide multiple examples if you need, but the synopsis is that instead of the GNS430 or G1000 indicating the selected from-to airports, I now have waypoints interjected. They are VALID waypoints for the target airport. However, I did NOT ask for them, and they make my flight plan unusable. They do NOT create a flight plan!

Is this something you have seen? Do you know how I can "select" the "staging, secondary, and offset" flight plans to pick the right one? I have seen ZERO chatter about this on the Prepar3D forums. There is one discussion from me that falsely indicated the problem was solved, but that was premature.

Thanks, Tim.

[Tim]

Could you attach a broken plan, and show a screenshot maybe of what the problem is?
Thanks

[howellerman]

Hi Tim,

Thanks for the response. I have attached the "broken" plan and two screenshots: one using the stock GNS430 and the other the stock G1000. The GNS430 view includes a screen shot of the freeware "GPS 1.4" facility (available on AVSIM) and it mimics the stock interpretation. Both show the magenta active flight plan coming in from "somewhere", whereas it should be coming from Reid Hillview along the white line.

This is all brand new with V5.4 - never had a problem with previous versions. Note that the second bullet of the Prepar3D V5.4 release notes says "new ways to manage active flight plans". Hahahahaha...

Thanks for the help, Tim!
John Howell

[Tim]

Thanks, but the flight plan is not attached. It should be an allowed extension, but if that fails you could try zipping it, or worst case, open it in notepad and paste it into the message body.

[howellerman]

Well, buggar all!

Here we go, brute force copy-and-paste.

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

<SimBase.Document Type="AceXML" version="1,0">
<Descr>AceXML Document</Descr>
<FlightPlan.FlightPlan>
<Title>KRHV to KTVL</Title>
<FPType>VFR</FPType>
<CruisingAlt>10600</CruisingAlt>
<DepartureID>KRHV</DepartureID>
<DepartureLLA>N37° 20' 10.97",W121° 49' 20.89",+000131.00</DepartureLLA>
<DestinationID>KTVL</DestinationID>
<DestinationLLA>N38° 53' 37.97",W119° 59' 43.21",+006263.00</DestinationLLA>
<Descr>KRHV, KTVL</Descr>
<DeparturePosition>13L</DeparturePosition>
<DepartureName>Reid-Hillview</DepartureName>
<DestinationName>Lake Tahoe</DestinationName>
<AppVersion>
<AppVersionMajor>10</AppVersionMajor>
<AppVersionBuild>61472</AppVersionBuild>
</AppVersion>
<ATCWaypoint id="KRHV">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N37° 20' 10.97",W121° 49' 20.89",+000131.00</WorldPosition>
<ICAO>
<ICAOIdent>KRHV</ICAOIdent>
</ICAO>
</ATCWaypoint>
<ATCWaypoint id="KTVL">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N38° 53' 37.97",W119° 59' 43.21",+006263.00</WorldPosition>
<ICAO>
<ICAOIdent>KTVL</ICAOIdent>
</ICAO>
</ATCWaypoint>
</FlightPlan.FlightPlan>
</SimBase.Document>

[howellerman]

Hi again, Tim.

Looking at the HTML from my copy-and-paste, it looks pretty much as expected.

What I was *really* looking for was if you had any insight into what Lockheed Martin meant with the second bullet of the release notes for P3DV5.4, i.e., "three ways of interpreting flight plan information". I have not found ANYTHING but in my ignorance am perhaps looking for the wrong thing.

Everything was good until V5.4, and the new flight plan "capabilities" blew everything all to hell...

Thanks again, Tim, for your support!

[Tim]

Honestly no idea. The only 3 ways of interpreting a flight plan I could think of were
- correctly
- incorrectly
- not at all

I mean, it's basically a list of waypoints. What's to "interpret"?

I'll look at your plan though, and see if I can figure out what's going on.

[howellerman]

Hi Tim,

Just to close this thread. It appears that SimLauncherX, for which Maarten Boelens dropped support at Prepar3dV4, which I kludged into supporting V5, has reach its end of life, and something in 5.4 broke it. It's really too bad, because it was a really nice simulation... well, launcher!

Thanks for the support, Tim. When Chase Plane gets integrated into MSFS then I will have new Plan-G challenges!

John Howell