So here is my problem.  I have generated a proper plan file from LNM and stored it in MSFS as the .fln file OK.  When I load the plan in MSFS at startup it creates a total different plan (direct only between two airports) than what I had in the original LNM plan that was exported to  MSFS.  The LNM generated plan had some other waypoints generated in the LNM plan which were completely ignored by MSFS.  Can you explain why this might be happening?  I have done this for two different airports and the same result seems to pop up.

MSFS flight plan loading is a mess. Sorry, have to say that. Opposed to its ancestor FSX it is not tolerant to differences in navdata/flight plans at all and has more issues like ignoring departure parking, automatically selecting transitions, being picky about waypoins, etc.

I can only recommend to install the Navigraph navdata update in MSFS and LNM to have the navigation databases in sync. This minimizes the issues.

Also quoting from the manual since the paragraph is a bit hidden there:

Quote

• If you use the Navigraph update for MSFS: Update the Little Navmap database with the FMS Data Manager as well to keep the program in sync with the MSFS scenery library. Use the scenery mode Use Navigraph for Navaids and Procedures in the menu Scenery Library to get access to all procedures in Little Navmap.
• If you do not use the Navigraph update for MSFS: Use the scenery mode Do not use Navigraph Database in the menu Scenery Library to avoid issues with missing or changed navaids. Keep in mind that SID and STAR are not available yet in Little Navmap.

Hope this helps a bit.

Alex

 

 

Alex - Thanks for the immediate response!!  First of all, thanks for your commitment to this third-party app.   I am enjoying using it and learning much about flight planning.  I am sure the community owes you a lot for your long hours of work at tweaking this and trying to incorporate suggestions.  Keep up the good work!

Let me just add some more experience to what I did above.   I have tried different configurations for loading the plan I mentioned to you and noticed that MSFS will start out loading up the correct Departure runway and default to VFR (Direct-GPS).  It assigned the wrong Arrival runway as the default.  That is, in the LNM plan I assigned another runway and selected an ILS approach.  The result was the end-to-end flight plan as executed by MSFS had all the correct waypoints (including a custom one I set in between) and placed me on an ILS approach to the airport (but not necessarily to the correct runway from the LNM plan).  I disengaged the AP and then flew in manual to landing.  If I do a initial load again of the same plan and make any changes to runways or change to another type of departure or change the arrival to an ILS, all the LNM plan waypoints are wiped out.  So much for that.  Just an FYI, not sure if I made sense for you.

Best Wishes - Thanks Again!!

3 hours ago, albar965 said:

MSFS flight plan loading is a mess.

+1²  (what he said)  Oh! And that is just pre-flight.....

Edited February 27, 20215 yr by fppilot

@amei MSFS completely ignores runway assignements when loading plans. If you change these in MSFS you have to use the  dropdown list and not the map. Changing anything on the map wipes out the plan. Changing a procedure wipes out the plan too. I don't know why they implemented it like this. It makes no sense. No other simulator causes so much issues when loading plans. Neither FSX, nor P3D nor X-Plane.