July 24, 20241 yr Author 2 hours ago, albar965 said: I suppose the above was done with the Navigraph update in MSFS disabled and reloading the LNM scenery library after doing so, right? In order to ensure this requirement, I have remove all Navigraph from MSFS before launching and reloaded the scenery library within LNM. And I have created a new FPL from scratch in both tools LFMI to LICT. MAR05 and ROM12 are Userwaypoints in LNM. Only MAR05 exists in my USERWP in Charts, so I disregarded ROM12. Here is the LNM export in MSFS Here is the CHARTS Export in MSFS. Some differences and similarities... FPL export from LNM: Quote <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>LFMI to LICT</Title> <FPType>IFR</FPType> <RouteType>LowAlt</RouteType> <CruisingAlt>1500</CruisingAlt> <DepartureID>LFMI</DepartureID> <DepartureLLA>N43° 31' 32.35",E4° 55' 31.66",+000054.00</DepartureLLA> <DestinationID>LICT</DestinationID> <DestinationLLA>N37° 54' 43.00",E12° 29' 35.99",+000016.00</DestinationLLA> <Descr>LFMI, LICT created by Little Navmap 3.0.8</Descr> <DepartureName>Istres Le Tubé</DepartureName> <DestinationName>Birgi Mil</DestinationName> <AppVersion> <AppVersionMajor>11</AppVersionMajor> <AppVersionBuild>282174</AppVersionBuild> </AppVersion> <ATCWaypoint id="LFMI"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N43° 31' 21.00",E4° 55' 26.99",+000054.00</WorldPosition> <ICAO> <ICAOIdent>LFMI</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MAR05"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N42° 41' 0.00",E5° 5' 0.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>MAR05</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="ROM12"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N41° 0' 0.00",E8° 0' 0.00",+001500.00</WorldPosition> <ICAO> <ICAORegion>LF</ICAORegion> <ICAOIdent>ROM12</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="BELOK"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N39° 23' 23.00",E10° 21' 39.02",+001500.00</WorldPosition> <ICAO> <ICAORegion>LI</ICAORegion> <ICAOIdent>BELOK</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LICT"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N37° 54' 43.80",E12° 29' 36.82",+000016.00</WorldPosition> <ICAO> <ICAOIdent>LICT</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document> And from CHARTS Quote <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>LFMI to LICT</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>38000</CruisingAlt> <DepartureID>LFMI</DepartureID> <DepartureLLA>N43° 31' 21.00",E04° 55' 27.01",+000082.00</DepartureLLA> <DestinationID>LICT</DestinationID> <DestinationLLA>N37° 54' 42.84",E12° 29' 35.88",+000026.00</DestinationLLA> <Descr>LFMI to LICT created by Navigraph</Descr> <DepartureName>LE TUBE</DepartureName> <DestinationName>BIRGI</DestinationName> <AppVersion> <AppVersionMajor>11</AppVersionMajor> <AppVersionBuild>282174</AppVersionBuild> </AppVersion> <ATCWaypoint id="LFMI"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N43° 31' 21.00",E04° 55' 27.01",+000082.00</WorldPosition> <ICAO> <ICAOIdent>LFMI</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MAR05"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N42° 40' 20.00",E05° 8' 54.00",+000000.00</WorldPosition> <ICAO> <ICAOIdent>MAR05</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="ROM12"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N41° 0' 1.00",E08° 0' 0.00",+000000.00</WorldPosition> <ICAO> <ICAOIdent>ROM12</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="BELOK"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N39° 23' 23.00",E10° 21' 39.00",+000000.00</WorldPosition> <ICAO> <ICAOIdent>BELOK</ICAOIdent> <ICAORegion>LI</ICAORegion> </ICAO> </ATCWaypoint> <ATCWaypoint id="LICT"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N37° 54' 42.84",E12° 29' 35.88",+000026.00</WorldPosition> <ICAO> <ICAOIdent>LICT</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document> I hope to have forgotten nothing 😉 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 1 hour ago, braudoux said: I hope to have forgotten nothing No. Perfect. Thank you a lot! I'll try this without Navigraph update. Alex Alex' Projects: Little Navmap
July 25, 20241 yr MSFS does not have LFMI. In LNM I see it only with the Navigraph data enabled. Maybe this is the reason. Alex Alex' Projects: Little Navmap
July 25, 20241 yr Author I have an addon installed. I may send it to you if you wish. 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 25, 20241 yr 1 hour ago, braudoux said: I have an addon installed. I may send it to you if you wish. Thank you for the offer. I can give it a try (https://www.littlenavmap.org/contact.html). The strange thing is that MSFS has no issues with the add-on airport and instead moves arbitrary waypoints elsewhere. Do you also use add-ons in your other flight plans above? Maybe add-ons which update stock airports instead of adding new ones? This is probably the reason why I cannot reproduce it. What if you remove the add-ons? I'm thinking more and more that this is worth a bug report for Asobo. Alex Alex' Projects: Little Navmap
July 26, 20241 yr Author The only addon that I am using is MSFS ADDON Linker which allows me to manage my sceneries according to where I fly. I don't think that there is a relation with it. I have raise a ticket to MSFS. Will let you know their replies Bruno Edited July 26, 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 26, 20241 yr 46 minutes ago, braudoux said: The only addon that I am using is MSFS ADDON Linker which allows me to manage my sceneries according to where I fly. I don't think that there is a relation with it. Addon linker should not cause any issues. 46 minutes ago, braudoux said: I have raise a ticket to MSFS. Will let you know their replies Thank you. This helps a lot. Hope somebody at Asobo cares. Alex Alex' Projects: Little Navmap
August 18, 20241 yr Author Nobody seems interested in my problem there... I shaked the bowl twice and the same reply is provided: Quote As we have stated earlier, this issue is logged into our internal bug tracker and is being investigated. We will not provide individual status updates about the investigation or cannot say when/if the issue will be fixed. Kind regards, Microsoft Flight Simulator Support Team I am definitely stuck for military flights... 😞 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
August 18, 20241 yr 4 hours ago, braudoux said: I am definitely stuck for military flights... At least they look at it ... someday.🙁 Alex Alex' Projects: Little Navmap
Create an account or sign in to comment