July 18, 20241 yr Hello, I am flying military sorties with C160. My FPL prepared in LNM is a low level flight with waypoints. I have exported it in MSFS FPL. When I load that FPL within MSFS, only the DEP and ARR bases are associated and none of my waypoints. One WP has been created in the the African Atlantique ocean coastline... I used to import FPL before and that was working, not this time... Any idea why? Thanks for assistance Bruno P3D V4.5 and V5 on SSD1TB - W10.64 All add-ons on HDD 2To Intel Core I9+9900K, RAM32Gb, NVidia RTX2080TI, Surround 3 x 27inc, VR Pimax5K+ Saitex X55, Saitek Yoke Pro + Throttle quadrant, Multi panel, Saitek Rudder pedals, Thrustmaster MFD Cougar x2
July 18, 20241 yr Can you post the flight plan as LNMPLN here? Do you have the Navigraph navdata update for MSFS and LNM installed? Alex Alex' Projects: Little Navmap
July 18, 20241 yr Author Quote <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>LFOJ to LFSO</Title> <FPType>VFR</FPType> <RouteType>Direct</RouteType> <CruisingAlt>1500</CruisingAlt> <DepartureID>LFOJ</DepartureID> <DepartureLLA>N47° 59' 2.09",E1° 46' 22.84",+000412.00</DepartureLLA> <DestinationID>LFSO</DestinationID> <DestinationLLA>N48° 34' 59.01",E5° 57' 16.03",+001106.00</DestinationLLA> <Descr>LFOJ, LFSO created by Little Navmap 3.0.8</Descr> <DeparturePosition>PARKING NONE 17</DeparturePosition> <DepartureName>Bricy</DepartureName> <DestinationName>Ochey</DestinationName> <AppVersion> <AppVersionMajor>11</AppVersionMajor> <AppVersionBuild>282174</AppVersionBuild> </AppVersion> <ATCWaypoint id="LFOJ"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N47° 59' 16.00",E1° 45' 38.00",+000412.00</WorldPosition> <ICAO> <ICAOIdent>LFOJ</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="POWER LINE"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 39' 16.27",E1° 41' 1.06",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>POWER LINE</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="POWER LINE"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 16' 42.71",E2° 18' 38.55",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>POWER LINE</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="A2 (NEV)"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 9' 10.00",E2° 55' 45.01",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>A2 (NEV)</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="C2"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 14' 1.21",E3° 28' 45.01",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>C2</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="C9"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 12' 0.00",E3° 39' 0.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>C9</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="C1"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 20' 31.00",E3° 45' 49.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>C1</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="N1"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N48° 6' 30.00",E5° 47' 30.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>N1</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="N7"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N48° 30' 48.00",E4° 54' 55.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>N7</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="N8"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N49° 9' 49.99",E4° 35' 50.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>N8</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="N9"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N49° 13' 48.00",E4° 33' 7.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>N9</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="N3"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N49° 25' 0.00",E4° 49' 0.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>N3</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="N5"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N49° 28' 0.00",E5° 2' 0.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>N5</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MONTENACH"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N49° 25' 14.88",E6° 22' 42.24",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>MONTENACH</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="N6"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N48° 39' 57.29",E6° 37' 3.09",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>N6</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="SORTIE N6"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N48° 29' 52.63",E6° 27' 39.57",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>SORTIE N6</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="SO-NEUVEMAISON"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N48° 36' 26.97",E6° 8' 35.85",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>SO-NEUVEMAISON</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="SO-MOSEL"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N48° 39' 7.08",E5° 59' 19.32",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>SO-MOSEL</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LFSO"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N48° 34' 59.01",E5° 57' 16.00",+001106.00</WorldPosition> <ICAO> <ICAOIdent>LFSO</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document> Yes I have updated AIRAC to both LNM and Navigraph. But there is no relation with AIRAC as none of the waypoints are known in AIRAC. P3D V4.5 and V5 on SSD1TB - W10.64 All add-ons on HDD 2To Intel Core I9+9900K, RAM32Gb, NVidia RTX2080TI, Surround 3 x 27inc, VR Pimax5K+ Saitex X55, Saitek Yoke Pro + Throttle quadrant, Multi panel, Saitek Rudder pedals, Thrustmaster MFD Cougar x2
July 18, 20241 yr Thank you. I'll have a look at it but give me a day or so. I'd like to finish some other stuff before. Maybe MSFS does not like the spaces or dashes in the names. Alex Alex' Projects: Little Navmap
July 19, 20241 yr Author I have tested the option of spaces and dashes, and nothing has changed... I have tried to load a more conventional FPL (LFOJ-BIKF) and it works. Finally I tried this one that poses the same situation with unrecognized waypoints: Quote <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>LFMI to LFOA</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>29500</CruisingAlt> <DepartureID>LFMI</DepartureID> <DepartureLLA>N43° 31' 32.35",E4° 55' 31.66",+000054.00</DepartureLLA> <DestinationID>LFOA</DestinationID> <DestinationLLA>N47° 3' 25.51",E2° 38' 19.77",+000578.00</DestinationLLA> <Descr>LFMI, LFOA created by Little Navmap 3.0.8</Descr> <DepartureName>Istres Le Tubé</DepartureName> <DestinationName>Avord</DestinationName> <AppVersion> <AppVersionMajor>11</AppVersionMajor> <AppVersionBuild>282174</AppVersionBuild> </AppVersion> <ATCWaypoint id="LFMI"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N43° 31' 21.00",E4° 55' 27.00",+000054.00</WorldPosition> <ICAO> <ICAOIdent>LFMI</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MAR03"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N45° 0' 0.00",E3° 45' 0.00",+029500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>MAR03</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MGO03"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 20' 0.00",E2° 29' 0.00",+029500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>MGO03</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WP1"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 36' 35.38",E1° 32' 2.01",+029500.00</WorldPosition> <ICAO> <ICAOIdent>WP1</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="SIMCP"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 13' 54.59",E1° 41' 20.40",+029500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>SIMCP</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WP2"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 18' 56.82",E1° 42' 26.18",+029500.00</WorldPosition> <ICAO> <ICAOIdent>WP2</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WP3"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 20' 49.91",E1° 21' 47.74",+029500.00</WorldPosition> <ICAO> <ICAOIdent>WP3</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WP4"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 18' 57.66",E1° 42' 26.18",+029500.00</WorldPosition> <ICAO> <ICAOIdent>WP4</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WP5"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 20' 56.62",E1° 21' 47.74",+029500.00</WorldPosition> <ICAO> <ICAOIdent>WP5</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WP6"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 32' 40.89",E1° 10' 47.74",+025935.96</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>WP6</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WP7"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 30' 35.05",E1° 30' 21.90",+021537.05</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>WP7</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="WP8"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 47' 33.14",E1° 34' 29.10",+015983.72</WorldPosition> <ICAO> <ICAOIdent>WP8</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="CTX"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 56' 11.80",E1° 48' 4.10",+011887.79</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>CTX</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LFOA"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N47° 3' 25.00",E2° 38' 20.00",+000578.00</WorldPosition> <ICAO> <ICAOIdent>LFOA</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document> Edited July 19, 20241 yr by braudoux P3D V4.5 and V5 on SSD1TB - W10.64 All add-ons on HDD 2To Intel Core I9+9900K, RAM32Gb, NVidia RTX2080TI, Surround 3 x 27inc, VR Pimax5K+ Saitex X55, Saitek Yoke Pro + Throttle quadrant, Multi panel, Saitek Rudder pedals, Thrustmaster MFD Cougar x2
July 19, 20241 yr Author New testing: Firstly this FPL LFSO to LFOJ with some waypoints including one VOR (DJL), one airfield (LFLA) and three user-waypoints military nav (SOERS, MET02 and OJER25S). This is not working. Quote <?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>VFR</FlightplanType> <CruisingAlt>18500</CruisingAlt> <CruisingAltF>18500.00000000</CruisingAltF> <CreationDate>2024-07-19T13:21:22+08:00</CreationDate> <FileVersion>1.2</FileVersion> <ProgramName>Little Navmap</ProgramName> <ProgramVersion>3.0.8</ProgramVersion> <Documentation>https://www.littlenavmap.org/lnmpln.html</Documentation> </Header> <SimData>MSFS</SimData> <NavData Cycle="2407">NAVIGRAPH</NavData> <AircraftPerformance> <Type>C172</Type> <Name>Example Performance Profile</Name> </AircraftPerformance> <Waypoints> <Waypoint> <Name>Ochey</Name> <Ident>LFSO</Ident> <Type>AIRPORT</Type> <Pos Lon="5.954453" Lat="48.583057" Alt="1106.00"/> </Waypoint> <Waypoint> <Name>1000FE</Name> <Ident>SOERS</Ident> <Region>LF</Region> <Type>USER</Type> <Pos Lon="5.673214" Lat="48.406876" Alt="6466.94"/> </Waypoint> <Waypoint> <Name>Dijon Longvic</Name> <Ident>DJL</Ident> <Region>LF</Region> <Type>VOR</Type> <Pos Lon="5.097333" Lat="47.270779" Alt="18500.00"/> </Waypoint> <Waypoint> <Name>METRO 02</Name> <Ident>MET02</Ident> <Region>LF</Region> <Type>USER</Type> <Pos Lon="3.500278" Lat="47.573334" Alt="18500.00"/> </Waypoint> <Waypoint> <Name>Branches</Name> <Ident>LFLA</Ident> <Type>AIRPORT</Type> <Pos Lon="3.496674" Lat="47.846390" Alt="18500.00"/> </Waypoint> <Waypoint> <Name>ORMES</Name> <Ident>OJER25S</Ident> <Region>LF</Region> <Type>USER</Type> <Comment>Entry rwy 25 South 1500ft QFE Water Tower</Comment> <Pos Lon="1.814864" Lat="47.943314" Alt="1631.43"/> </Waypoint> <Waypoint> <Name>Bricy</Name> <Ident>LFOJ</Ident> <Type>AIRPORT</Type> <Pos Lon="1.760559" Lat="47.987778" Alt="412.00"/> </Waypoint> </Waypoints> </Flightplan> </LittleNavmap> Then I have removed the 3 user-waypoints and it works. Quote <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>LFSO to LFOJ</Title> <FPType>VFR</FPType> <RouteType>Direct</RouteType> <CruisingAlt>18500</CruisingAlt> <DepartureID>LFSO</DepartureID> <DepartureLLA>N48° 34' 59.01",E5° 57' 16.03",+001106.00</DepartureLLA> <DestinationID>LFOJ</DestinationID> <DestinationLLA>N47° 59' 16.00",E1° 45' 38.01",+000412.00</DestinationLLA> <Descr>LFSO, LFOJ created by Little Navmap 3.0.8</Descr> <DepartureName>Ochey</DepartureName> <DestinationName>Bricy</DestinationName> <AppVersion> <AppVersionMajor>11</AppVersionMajor> <AppVersionBuild>282174</AppVersionBuild> </AppVersion> <ATCWaypoint id="LFSO"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N48° 34' 59.01",E5° 57' 16.03",+001106.00</WorldPosition> <ICAO> <ICAOIdent>LFSO</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="DJL"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N47° 16' 14.80",E5° 5' 50.40",+018500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>DJL</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LFLA"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N47° 50' 47.00",E3° 29' 48.02",+018500.00</WorldPosition> <ICAO> <ICAOIdent>LFLA</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LFOJ"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N47° 59' 16.00",E1° 45' 38.01",+000412.00</WorldPosition> <ICAO> <ICAOIdent>LFOJ</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document> Hope this will help 😉 P3D V4.5 and V5 on SSD1TB - W10.64 All add-ons on HDD 2To Intel Core I9+9900K, RAM32Gb, NVidia RTX2080TI, Surround 3 x 27inc, VR Pimax5K+ Saitex X55, Saitek Yoke Pro + Throttle quadrant, Multi panel, Saitek Rudder pedals, Thrustmaster MFD Cougar x2
July 19, 20241 yr Thanks for the examples. I'll have a look at it when I'm back near my flying computer. Alex Alex' Projects: Little Navmap
July 19, 20241 yr Author No worries, enjoy your week-end 😉 P3D V4.5 and V5 on SSD1TB - W10.64 All add-ons on HDD 2To Intel Core I9+9900K, RAM32Gb, NVidia RTX2080TI, Surround 3 x 27inc, VR Pimax5K+ Saitex X55, Saitek Yoke Pro + Throttle quadrant, Multi panel, Saitek Rudder pedals, Thrustmaster MFD Cougar x2
July 21, 20241 yr I tried with the MSFS 1.37.19.0 (Navigraph navdata update installed in MSFS and LNM) and see no issues: Sorry, but I have not idea what is going on there. It shows ok even in the G1000. This is the plan in LNM: Alex Alex' Projects: Little Navmap
July 23, 20241 yr Author Hello, I am desperate 😞 I tried a very basic FPL with 2 WP and this what it looks like : The nav log is fine but the map is crazy... And strangely the GPS has accepted the WP... It looks like a bug in the MSFS map. P3D V4.5 and V5 on SSD1TB - W10.64 All add-ons on HDD 2To Intel Core I9+9900K, RAM32Gb, NVidia RTX2080TI, Surround 3 x 27inc, VR Pimax5K+ Saitex X55, Saitek Yoke Pro + Throttle quadrant, Multi panel, Saitek Rudder pedals, Thrustmaster MFD Cougar x2
July 23, 20241 yr This looks like its wrong in the GPS too (180°). What happens if you move the Navigraph update out of Community? MSFS had problems with the flight plan in the past with this installed. This showed waypoints move far North. Alex Alex' Projects: Little Navmap
July 23, 20241 yr Author How can I move the path, there is no option in the MSFS update tool for MSFS... P3D V4.5 and V5 on SSD1TB - W10.64 All add-ons on HDD 2To Intel Core I9+9900K, RAM32Gb, NVidia RTX2080TI, Surround 3 x 27inc, VR Pimax5K+ Saitex X55, Saitek Yoke Pro + Throttle quadrant, Multi panel, Saitek Rudder pedals, Thrustmaster MFD Cougar x2
July 23, 20241 yr 32 minutes ago, braudoux said: How can I move the path, there is no option in the MSFS update tool for MSFS... Just move the folders navigraph-navdata and navigraph-navdata-base out of "Community" to another folder like "Community OFF" using Windows Explorer. Alex Alex' Projects: Little Navmap
July 24, 20241 yr Author No joy with this new folder configuration... I tried another FPL including 2 Userpoints and again they flee in the south I have done a test : exporting the SAME flight plan from LNM and Navigraph CHARTS, and the result is similar but not identical. In the following screenshot, LNM misplaces YACIM and DIVKO (known FIXes) and the 2 USERWP are merged (MAR05, MAR06 separated by 0NM) The following screenshot shows the same FPL imported in MSFS from Navigraph Charts. The route is recognized till the last known FIX DIVKO. Then there is an inserted CRUISE waypoint from where the route drifts. The waypoints MAR05 and MAR06 are inserted in the User waypoints within CHARTS. Both are also merged (separated by 0NM) I hope that will help. Maybe that poses a problem within my MSFS because both exports are wrong? Please feel free to suggest any kind of test. Bruno Edited July 24, 20241 yr by braudoux P3D V4.5 and V5 on SSD1TB - W10.64 All add-ons on HDD 2To Intel Core I9+9900K, RAM32Gb, NVidia RTX2080TI, Surround 3 x 27inc, VR Pimax5K+ Saitex X55, Saitek Yoke Pro + Throttle quadrant, Multi panel, Saitek Rudder pedals, Thrustmaster MFD Cougar x2
July 24, 20241 yr 5 hours ago, braudoux said: I hope that will help. Maybe that poses a problem within my MSFS because both exports are wrong? Thank you. Can you post both of the last two flight plans here? This would help me a lot. I suppose the above was done with the Navigraph update in MSFS disabled and reloading the LNM scenery library after doing so, right? I'm not sure I can help since I cannot reproduce this here but I'd like to have a look at it anyway. Sometimes small nonsensical changes can be used as workarounds for MSFS buggy flight plan loading. Alex Alex' Projects: Little Navmap
Create an account or sign in to comment