I have been trying for a long time to export a flight, complete with approach ILS, runway, selections, etc. into Microsoft flight simulator. I can’t seem to do it. I keep getting that warning then I unselect the options then I don’t get the approach. If I leave the options selected, I still don’t get the approach.

Is there a simple way to do this?

I suppose you use "Export Flight Plan as MSFS 2020 PLN".

More information would help, e.g. the text of the warning dialogs (copy and paste with the mouse).
The flight plan and maybe a screenshot of the plan in MSFS.
What options are checked in menu "File" -> "Export options"? I recommend them all off.

MSFS has its problems importing flight plans an behaves erratically at times.

Alex

 

Everything happens just as you say. The warning I get is the standard warning that says don’t use the options. If I use the options, all three, I get a screwed up looking flight plan. If I unselect all the options, I still get a screwed up looking flight plan.

 

I should tell you that what I’m trying to do is select the approach and the runway in Little NVM, and that seems to be the thing that causes all the errors  

 

is there someway I can send you the actual saved flight plan and you can see what’s actually happening in the application?

 

Thanks for your help.

 

Michael

Hi Michael,

you can insert the plan as LNMPLN and maybe as PLN to directly in a post here. The flight plans are text files. See here how to do this:

See here about common MSFS flight plan issues: https://albar965.github.io/littlenavmap-faq.html#flightplan-msfs

Also make sure that LNM and MSFS scenery libraries are in sync. Check "Select Automatically" in LNM menu "Scenery Library" -> "Navigraph".
Also reload the scenery library database after simulator updates.

Alex

 

Alex:

Here is the text of the file.

Thanks.

Michael

 

<?xml version="1.0" encoding="UTF-8"?>
<LittleNavmap xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://www.littlenavmap.org/schema/lnmpln.xsd">
  <Flightplan>
    <Header>
      <FlightplanType>IFR</FlightplanType>
      <CruisingAlt>13000</CruisingAlt>
      <CruisingAltF>13000.00000000</CruisingAltF>
      <CreationDate>2024-04-10T19:31:15-04:00</CreationDate>
      <FileVersion>1.2</FileVersion>
      <ProgramName>Little Navmap</ProgramName>
      <ProgramVersion>3.0.6</ProgramVersion>
      <Documentation>https://www.littlenavmap.org/lnmpln.html</Documentation>
    </Header>
    <SimData>MSFS</SimData>
    <NavData>MSFS</NavData>
    <AircraftPerformance>
      <FilePath>Beechcraft 36.lnmperf</FilePath>
      <Type>BE36</Type>
      <Name>Example Performance Profile</Name>
    </AircraftPerformance>
    <Departure>
      <Pos Lon="16.242676" Lat="38.909035" Alt="30.00"/>
      <Start>PARKING 4</Start>
      <Type>Parking</Type>
      <Heading>8.0669</Heading>
    </Departure>
    <Procedures>
      <SID>
        <Name>GIRO7R</Name>
        <Runway>28</Runway>
      </SID>
      <Approach>
        <Name>LIBV32L</Name>
        <Runway>32L</Runway>
        <Type>CUSTOM</Type>
        <CustomDistance>3.00</CustomDistance>
        <CustomAltitude>1000.00</CustomAltitude>
        <CustomOffsetAngle>0.00</CustomOffsetAngle>
      </Approach>
    </Procedures>
    <Waypoints>
      <Waypoint>
        <Name>Terme</Name>
        <Ident>LICA</Ident>
        <Type>AIRPORT</Type>
        <Pos Lon="16.241669" Lat="38.908333" Alt="30.00"/>
      </Waypoint>
      <Waypoint>
        <Ident>ULKEN</Ident>
        <Region>LI</Region>
        <Type>WAYPOINT</Type>
        <Pos Lon="16.039169" Lat="39.614998" Alt="13000.00"/>
      </Waypoint>
      <Waypoint>
        <Ident>SIRGI</Ident>
        <Region>LI</Region>
        <Type>WAYPOINT</Type>
        <Pos Lon="16.703613" Lat="40.130558" Alt="13000.00"/>
      </Waypoint>
      <Waypoint>
        <Name>Gioia Del Colle Mil</Name>
        <Ident>LIBV</Ident>
        <Type>AIRPORT</Type>
        <Pos Lon="16.932999" Lat="40.769669" Alt="1148.00"/>
      </Waypoint>
    </Waypoints>
  </Flightplan>
</LittleNavmap>

 

Alex:

In reading that text that you sent me, it seems that it may be impossible to obtain what I was looking for, namely, a precise way of going say, from LNM to Pilot2ATC, or to MSFS and always having complete uniformity in the result.  Looks like variances are almost inevitable when trying to do this.  Might just be the nature of the beast(s).

Thanks again.

Michael

Thank you for the plan, Michael.

I'll have a look at it.

It should not be impossible to load a plan properly into MSFS. It should work mostly ok.

Alex

Looks alright to me. Below shots are with all export options off and exported with "File" -> "Export Flight Plan as MSFS 2020 PLN". Then loaded in the MSFS opening screen. Also the GPS in the aircraft shows it ok.

The altitude at waypoints from LNM is usually ignored by MSFS. This is as expected.

I have a lot of more complex examples here with SID, STAR and approaches that work ok.
It also may depend if you have the Navigraph navdata update installed or not. I tested with and without and see no issues.

LNM:

MSFS latest beta 15:

 

Alex

Alex:

Something must be wrong with mine.  I just did another one in Spain.  For simplicity, let's say the ILS last leg was at 360 degrees, which is correct.  So the final leg is north.

I exported to MSFS 2020 format.  All options were off.

I imported the file into Pilot2ATC and again the last leg was still at 360 degrees.  Correct.

When I brought the same file into MSFS, the LOG says that the last leg is 360 degrees, but the in-game "map" shows a completely different track, in a southerly direction.  And I didn't change any of the drop-downs or anything in MSFS.

I don't see how the MSFS version can be so dramatically different.

Thanks again, and sorry to bug you about what must be a rather simple problem.

Michael

No problem at all, Michael.

If all goes wrong you can also create the plan in MSFS, save it as PLN and import it into LNM for flight following.
You can load MSFS PLN files from LNM menu "File" -> "Open flight plan" like LNMPLN files. LNM detects the format automatically.

Alex

Thank you.  I also found that sometimes I can "tweak" the MSFS version to match whatever LNM has and get away with it.  Just use the dropdowns for approaches and such.  Leave en route alone.  Seems to work.

Thanks again.

Michael

 

The only difference I see is that I'm using the MSFS beta. Maybe they fixed some of the issues but I doubt it.

Alex