I m really not trying to de-rail this thread. I am having troubles thinking clearly and am confused. It’s me! Honest.
I really don’t know the ins and outs. All I’m concluding after my first days with Little Nav Map is that the old 1801 cycle doesn’t sit well with the MSFS data, if you do not turn it off through Scenery Library → Navigraph cycle 1801 → Do not use.
You then lose all the nice approaches and departures - that don’t work properly anyway in MSFS (but I read somewhere that will come back through the MSFS data in a later version of LNM).
How the software works with MSFS if you have a Navigraph subscription and the latest cycle, I do not know (since I don’t have one).
If you’re using whatever that bundled (possibly out of date) Navigraph database mentioned earlier, then no, all bets are off as to what you’d see in the sim as you’re dealing with two different data sources to reconcile in a single flight plan.
To get 1:1 correspondence on NavData, either load the NavBlue scenery into LNM if that’s what you have. Or if you have Navigraph, install it into the sim (it acts the same way as a Community Mod) and then load that data into LNM - or point it since LNM auto detects your installed scenery libraries.
This is NavData.
It’s important to understand that the procedures you see INSIDE LNM, which are based on the NavData currently loaded, may or may not be 100 percent understood by the sim’s flight planner tool when you import a plan from LNM into the sim. As stated before, some procedure types are not understood by the sim, such as holding patterns.
2 Likes
That helps ememPilot. (I think)
I do not have access to my MSFS sim for at least another week or so and it will resolve itself for me, anyway. I think I want to focus on the U.S. for a little while anyway.
I say its good to ignore me on this. My dog does everyday!
1 Like
CasualClick: I think I get it now. Thank you very much!
I may dump LNM if the new Navigraph window works ALL of the time. K.I.S.S.
If it is good enough for EasyJetPilot it is great for me.
I’m going to go back to bed now and get some sleep. COVID sucks-hard
1 Like
Get well soon!
1 Like
Thanks for the get-well reply, ememPilot!
COVID has been the hardest sickness to overcome for me while being alive for 61 years. It is so dangerous. It stays in your system; it seems like “forever”. I have been sick since May 1st and it feels like it has been a year instead of a month. Please be safe peeps! I and others really care for your well being.
“We” are all we have got, so take care of your friends and family!
2 Likes
Yeah, that sounds horrible. Hang in there. I know these long haul diseases can be very discouraging.
I got the jab on Friday. Felt quite miserable due to the side effects, but happy that I did. The ‘side effects’ of the virus are a lot worse.
2 Likes
I had to look that up. For others to understand, ememPilot is referring to the “Jab Vaccine for COVID”, I believe.
Related article: Covid-19: “First man to get jab vaccine William Shakespeare dies of unrelated illness”. This BBC article was posted 5 days ago: Covid-19: First man to get jab William Shakespeare dies of unrelated illness
Thanks again, ememPilot for the kind words and understanding.
Indeed I was! Referring to the covid vaccination 
And to add to the confusion: I’m not William Shakespeare! Great name though…
2 Likes
I’m also having issues with LNM. It is adding waypoints when i load the flight plan into the sim. Also, if I load flight plans 2 or more times, I CTD.
It is the sim planner, not LNM, adding extra points most likely. LNM will read the NavBlue data correctly and only show valid procedure legs available. It’s the sim that doesn’t understand certain procedure legs and adds USR waypoints to make up that shortcoming. Also, SU5 started adding additional TOC/TOD waypoints if you’re using the default G1000.
2 Likes
Thanks for that. I’m using the G3000 in the TBM 9000. Hopefully this will be corrected sometime soon. I much prefer planning flights using LNM over the ‘in sim’ planner. Again… thanks. I’m happy it’s not just my system this is happening to. What I don’t understand is that it was working fine prior to hotfix. Hopefully developers are aware of this and are addressing it.