I purchased AS (for use with MSFS 2024) but I'm unable to load a flight plan that is made with the onboard EFB or flight plans made with the https://planner.flightsimulator.com/ .
I can see the flight plans made with the latter in the EFB, save them in *PLN format but when I try to load these into AS I get the following message:

Unable to parse the requested flight plan

Before posting I did do some search, found a few messages with the same error but either they are for another sim or are not helpful.
I also didn't find much of a help/manual that points to possible solutions for this error.

Flight plans made with Simbrief work fine though but I'm more interested in the in game flight plan option.
If it doesn't work with the in game flightplanning AS is a bit of a waste of money for me since I have no real desire to use Simbrief.

Edited December 27, 20241 yr by Lange_666

You need to post this on the AS official forums. Asobo made changes to the flight plan file format for MSFS2024. AS may have missed some of the changes.

Its also possible that there's a bug in the way that both the EFB and the flight planner website create flight plan files.

I posted there before I posted here and I only posted here afterwarts because I noticed the low traffic on that forum.
But I got a response/question from a developer in the mean time.

I have the same problem in some of my apps (= that MS24 flight plan files can't be read). 

The reason is, that the flight plan (*.PLN) files created by MSFS 2024 are different than before. At least the airliner routes no longer contain lat/lon for the waypoints, but only their ICAO code and region (plus the procedure codes for departure, arrival and approach, also without coordinates). Any application trying to read them for GIS purposes would have to have a database of all existing waypoints to figure out their geographical location. Or use the MSFS scenery API to request that data over SimConnect. I went for the latter, but implementing that is a real pain in you know where.

Legacy flight plan format up to MSFS2020 (last I checked)

       </AppVersion>
       <ATCWaypoint id="EDDM">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N48° 21' 13.646074",E11° 47' 9.909468",+001487.00</WorldPosition>
            <ICAO>
                <ICAOIdent>EDDM</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MUN">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N48° 10' 49.180555",E11° 48' 57.660241",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>ED</ICAORegion>
                <ICAOIdent>MUN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BAVAX">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N48° 15' 46.009810",E11° 40' 32.000542",+000000.00</WorldPosition>
            <ATCAirway>M867</ATCAirway>
            <ICAO>
                <ICAORegion>ED</ICAORegion>
                <ICAOIdent>BAVAX</ICAOIdent>
            </ICAO>
        </ATCWaypoint>

New MSFS 2024 flight plan format:

       </AppVersion>
        <DepartureDetails>
            <RunwayNumberFP>26</RunwayNumberFP>
            <RunwayDesignatorFP>LEFT</RunwayDesignatorFP>
            <DepartureFP>OBAX6S</DepartureFP>
        </DepartureDetails>
        <ATCWaypoint>
            <ATCWaypointType>Intersection</ATCWaypointType>
            <ICAO>
                <ICAORegion>ED</ICAORegion>
                <ICAOIdent>LUXEK</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint>
            <ATCWaypointType>Intersection</ATCWaypointType>
            <ICAO>
                <ICAORegion>LO</ICAORegion>
                <ICAOIdent>ALILA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        

 

Edited December 28, 20241 yr by Lorby_SI

CruisingAlt is wrong in those MS24 files too btw. 

        <FPType>IFR</FPType>
        <CruisingAlt>1300000.000</CruisingAlt>
        <AppVersion>
            <AppVersionMajor>12</AppVersionMajor>
            <AppVersionMinor>1</AppVersionMinor>
            <AppVersionBuild>282174</AppVersionBuild>
        </AppVersion>

Edited December 28, 20241 yr by Lorby_SI

Looks suspiciously like MS telling Asobe if they want to include a free flight planner it absolutely must NOT be used with any other product than 2024. Or any addon not sold by Microsoft. 

I could be wrong it could just be basic coder incompetence or the complete lack of any kind of testing whatsoever (file under hubris /incompetence). 

9 hours ago, Lange_666 said:

I posted there before I posted here and I only posted here afterwarts because I noticed the low traffic on that forum.
But I got a response/question from a developer in the mean time.

I made a small tool that converts the MSFS2024 flight plan files into the legacy FSX format using the MSFS 2024 scenery API.

Anybody interested in trying that, drop me a PM here on AVSIM.