OnCourse Software

Welcome to our Product Support Forums

Advanced search
Board index » PF3-ATC at its best

Flight plan problem

PLEASE NOTE:

If you are reporting an issue with PF3 please remember to Zip and attach the Debug_Monitor.log file from your PF3\Logs folder. Thank you.

Post Reply   Page 1 of 1  [ 5 posts ]
Author Message
Alixe91
Post subject: Flight plan problem
Posted: Thu Nov 17, 2022 12:34 am
Offline
 
Posts: 28
Joined: Tue Nov 15, 2022 11:42 am
 
Salut,

I created a flight plan with navigraph saved in .pln format the plan is displayed correctly in the plane's G3000.

PF3 in demo mode : gives me the following error and therefore I can't use your demo.

Attachments
[ attachment ]
2pf3.png (1.02 MiB) Viewed 1205 times


Top
Profile Quote
Alixe91
Post subject: Re: Flight plan problem
Posted: Thu Nov 17, 2022 6:27 am
Offline
 
Posts: 28
Joined: Tue Nov 15, 2022 11:42 am
 
I attach the flight plan.
I wanted to attach the flight plan and it didn't upload! here is the copy if it can help you see an error.
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>LFPG VFR PARIS</Title>
        <FPType>VFR</FPType>
        <RouteType>LowAlt</RouteType>
        <CruisingAlt>3000</CruisingAlt>
        <DepartureID>LFPG</DepartureID>
        <DepartureLLA>N49° 0' 34.92",E02° 32' 52.01",+000392.00</DepartureLLA>
        <DestinationID>LFPO</DestinationID>
        <DestinationLLA>N48° 43' 23.88",E02° 22' 45.98",+000291.00</DestinationLLA>
        <Descr>LFPG VFR PARIS created by Navigraph</Descr>
        <DepartureName>CHARLES-DE-GAULLE</DepartureName>
        <DestinationName>ORLY</DestinationName>
        <AppVersion>
            <AppVersionMajor>11</AppVersionMajor>
            <AppVersionBuild>282174</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="LFPG">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N49° 0' 34.92",E02° 32' 52.01",+000392.00</WorldPosition>
            <RunwayNumberFP>26</RunwayNumberFP>
            <RunwayDesignatorFP>RIGHT</RunwayDesignatorFP>
            <ICAO>
                <ICAOIdent>LFPG</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="VP687">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N48° 53' 14.00",E02° 28' 27.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>VP687</ICAOIdent>
                <ICAORegion>LF</ICAORegion>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="VP679">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N48° 51' 56.00",E02° 24' 49.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>VP679</ICAOIdent>
                <ICAORegion>LF</ICAORegion>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="VP668">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N48° 49' 33.00",E02° 23' 25.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>VP668</ICAOIdent>
                <ICAORegion>LF</ICAORegion>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="VP690">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N48° 54' 15.00",E02° 17' 19.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>VP690</ICAOIdent>
                <ICAORegion>LF</ICAORegion>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="D316E">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N48° 47' 16.57",E02° 18' 29.41",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>D316E</ICAOIdent>
                <ICAORegion>LF</ICAORegion>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="DOPAP">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N48° 42' 7.80",E02° 14' 34.70",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>DOPAP</ICAOIdent>
                <ICAORegion>LF</ICAORegion>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LFPO">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N48° 43' 23.88",E02° 22' 45.98",+000291.00</WorldPosition>
            <ICAO>
                <ICAOIdent>LFPO</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>
Top
Profile Quote
Dave March
Post subject: Re: Flight plan problem
Posted: Thu Nov 17, 2022 10:09 am
Site Admin
Offline
 
Posts: 6178
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
Your flight plan is not in the correct format. As you can see from the error message it's missing the standard end-of-line delimiters (0D0A - carriage return & line feed). Check your Navigraph settings... I don't use it so can't help with that I'm afraid

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]
Top
Profile Quote
MaxStout
Post subject: Re: Flight plan problem
Posted: Mon Apr 24, 2023 3:35 pm
Offline
 
Posts: 15
Joined: Wed Mar 29, 2023 9:27 am
Location: Ilkley, West Yorks, UK
 
Navigraph does not appear to have an option to use the Carriage Return and Line Feed hex code "0d 0a" after each line in a Flight Plan; it only adds "0a". Flight Plans created in MSFS, Little NavMap and SimBrief all contain 0d 0a after each line.

A workaround for users that want to use Navigraph to create their flight plans is as follows:

• Create flight plan in Navigraph and export as .pln file
• Load the .pln file into MSFS 2020
• Before clicking the FLY button, resave the .pln file from MSFS, overwriting the original. This replaces the 0a code with 0d 0a code.
• Open the modified .pln file in PF3

It only one extra step although it is one more thing to remember before you find yourself in the cockpit (you can't go back and save a .pln file once you're in the cockpit without quitting the flight altogether).

Alternatively, before starting MSFS, you could use LNM to do the same processing of the Navigraph .pln file (and add a departure gate) or do a "Search/Replace All" 0a to 0d 0a with a Hex Editor such as Notepad++ (with Hex Editor plugin) - it took me less than 5 minutes to download Notepad++, add the plugin and figure out how to do it. Either way takes seconds once you've done it the first time and I find easier than remembering to do it in MSFS pre-flight.

Given the popularity of Navigraph and that other programs such as MSFS and LNM can load flight plans with either 0d 0a or just 0a code, it would be great if a future release of PF3 could do the same.

_________________

Cheers
MaxStout
Top
Profile Quote
Dave March
Post subject: Re: Flight plan problem
Posted: Mon Apr 24, 2023 4:35 pm
Site Admin
Offline
 
Posts: 6178
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
Thanks for that... I must remember to add it to our FAQ's

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]
Top
Profile Quote
Display: Sort by: Direction:
Post Reply   Page 1 of 1  [ 5 posts ]
Return to “PF3-ATC at its best”
Jump to:
Board index Delete cookies | All times are UTC+01:00

Powered by phpBB® Forum Software © phpBB Limited

Privacy | Terms