Pilot2ATC does not import altitude from the following flightplan. It seems that .000 in the <CruisingAlt> tag is treated by the program as invalid data. 

 

Full flightplan I used:

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

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>EETN to ESSA</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>28000.000</CruisingAlt>
        <DepartureID>EETN</DepartureID>
        <DepartureLLA>N59° 24' 48.00",E24° 49' 57.00",+000135.00</DepartureLLA>
        <DestinationID>ESSA</DestinationID>
        <DestinationLLA>N59° 39' 7.00",E17° 55' 7.00",+000138.00</DestinationLLA>
        <Descr>EETN to ESSA created by SimBrief</Descr>
        <DepartureName>Lennart Meri</DepartureName>
        <DestinationName>Arlanda</DestinationName>
        <AppVersion>
            <AppVersionMajor>11</AppVersionMajor>
            <AppVersionBuild>282174</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="EETN">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N59° 24' 48.00",E24° 49' 57.00",+000135.00</WorldPosition>
            <RunwayNumberFP>26</RunwayNumberFP>
            <ICAO>
                <ICAOIdent>EETN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PETOT">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N59° 30' 40.00",E23° 8' 31.00",+022000.00</WorldPosition>
            <DepartureFP>PETO1T</DepartureFP>
            <RunwayNumberFP>26</RunwayNumberFP>
            <ICAO>
                <ICAORegion>EF</ICAORegion>
                <ICAOIdent>PETOT</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LUPET">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N59° 38' 25.00",E19° 52' 35.00",+028000.00</WorldPosition>
            <ICAO>
                <ICAORegion>ES</ICAORegion>
                <ICAOIdent>LUPET</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="XILAN">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N59° 39' 33.50",E19° 4' 33.80",+019900.00</WorldPosition>
            <ATCAirway>L77</ATCAirway>
            <ICAO>
                <ICAORegion>ES</ICAORegion>
                <ICAOIdent>XILAN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="SA570">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N59° 36' 16.00",E18° 41' 42.30",+013700.00</WorldPosition>
            <ArrivalFP>XILA5T</ArrivalFP>
            <RunwayNumberFP>26</RunwayNumberFP>
            <ICAO>
                <ICAORegion>ES</ICAORegion>
                <ICAOIdent>SA570</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="TEB">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N59° 31' 54.10",E18° 12' 11.90",+005600.00</WorldPosition>
            <ArrivalFP>XILA5T</ArrivalFP>
            <RunwayNumberFP>26</RunwayNumberFP>
            <ICAO>
                <ICAORegion>ES</ICAORegion>
                <ICAOIdent>TEB</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ESSA">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N59° 39' 7.00",E17° 55' 7.00",+000138.00</WorldPosition>
            <RunwayNumberFP>26</RunwayNumberFP>
            <ICAO>
                <ICAOIdent>ESSA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>

 

Thanks for the report.  It will be fixed in the next beta update.

Dave

Hi Dave, thanks for continuing updates.

With the beta3, the altitude from the flightplan file loads correctly. But if I import directly using the new feature "Import Simbrief", then the cruise altitude does not match. Simbrief shows FL340, while the imported plan shows FL300 in P2ATC. 

Yes.  This will be fixed in the Beta 4.

Dave

Works now, thanks!