I recently started using little nav map, so I am not an expert in it’s functions.
I create a flight plan in LNM with departures, arrivals, approach, and waypoints along the way. This works fine, gives me everything I need. I save the flt plan as LNMPLN, then I export it as a MSFS flt plan, hopefully this is right. I then load this flt plan in MSFS, this is where most of the time it differs, The flight plan ends up being completely different than the LNM flt plan.
Since installing LNM I have only been flying in Africa. Is this discrepency due to MSFS not having all/correct SIDS/STARS/Approaches? I am able to match most of the waypoints, GPS or VOR, MSFS simply uses an entirley different fltplan.
Is there something I am doing wrong? Is it the area that I am flying in? or Is it MSFS?
I am flying the TBM930 with working title and G3000 mod if that is of any importance.
That’s because the sim’s built-in flight planner is not capable of understanding all the ARINC procedure legs that LNM does when you create the plan outside the sim.
Additionally, none of the stock Flight Management Systems (i.e., GPS) are capable of understanding and executing them either. The only two FMS that understand most of the procedure leg types are the Working Title CJ4 and the G1000 NXi. So you will always see oddball things like massive course turns instead of a tight leg for example.
The G3000 will be updated to NXi after the latter leaves Early Access and the CJ4 receives the updated treatment. Eventually, Working Title will rip out the sim’s FP logic and replace it with the one inside the NXi so all FMS, Working Title or third party can benefit from full ARINC compatibility.
There is a difference between actual MSFS and navigraph database. Fly TBM too in africa and some stuff will be different or non existant. Go to scenery librairy → 3. navigraph. Disable it for the time being then msfs and littlenavmap will be 1:1
I agree there is some differences but for the most part I’m not having too much trouble planning in LNM although I don’t often fly in Africa.
Did you import the MSFS scenery library in LNM? Check under the “scenery library” menu to make sure you first imported that library and then have it selected. Maybe that will help.
I usually just plan the flight in Little Nav Nap and enter it manually into the g3000. Just takes a minute, avoids any weirdness with the sims built in flight planner and makes it a little more immersive as that’s what you’d be doing in the real world anyway.
There is another option which I do often when I see the big discrepancies in the LNM loaded plans. After I save the plan exported to MSFS then load it in the sim I immediately save it back to the save files and then pick that newly saved plan and put it into LNM. Then all the waypoints and approaches match up.
If I don’t want to do that I simply generate the plan in LNM and manually input the plan into the Avionics while on ground. It can be very cumbersome though depending on which plane and which avionics are in use.
