Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Unblock the EXE (no signature yet)...
It will auto-detect file paths, but make sure that you then select the MSFS2020 database and "load" the Navdata from the menu.
There is already DEM data in Littleavmap without needing to download the offline data. You can get elevation profile data. Works fine if you do your own flight plans. But you can't get it for the nevada bush trip because Asobo uses data that includes airports that don't exist in real life. Little navmap won't show profile/elevation data for a trip that doesn't start at a real airport. Take the very first airport on the nevada trip. Yes, the runway exists and you can see it on both bing and google but it's private property and not an FAA recognized field. In addition, the airport designation they use for it, O64, *is* an faa recognize airport but is a helipad in Oklahoma and has been for 26 years. For the nevada trip there are nine invalid airports kicked back by littlenavmap. Two are heliports in completely different states. The one exception on the list that is a legit airport is 88NV which is the Black Rock airport they only activate for 13 days a year for Burning Man. But the important thing is the flight plans will still load since they have the gps coords so they're still usable in littlenavmap. Just can't see the elevation profile for the trip since the start and end points have to be airports. This is what it will show https://i.imgur.com/qEWVKCp.png
The airport data that asobo uses is so inconsistent it's a bit strange. They have airports that are closed in the game. They have airports that haven't existed for 20 years in the game. Which is likely the case for the fields in the bush trips. Some might have existed at some point in the past. They also have airports that have *never* existed in the game (KTUY in Tulsa. That designation has never been used that I could find. The airport that used to be there was the old North Tulsa airport but it has never been KTUY). And they have a lot of smaller class golf uncontrolled airports with ATC that tries to communicate with you. Navdata in general is a mess in the sim which is a shame since it's all publicly available data
But.... None of that changes that LittleNavMap is a pretty valuable tool for flight simming in general.
Thank you very much!!
You can import the MSFS2020 data, use the included data, or in a best case use an updated AIRAC via your subscription.
If I import the MSFS data with "Load Scenery Library" and choose the option "Do not use navigraph data", I still miss all the SIDs and STARs MSFS has.
Am I doing something wrong?
Known Issues
MSFS
Little Navmap cannot read SID and STAR from MSFS. Documentation about MSFS format changes are needed in SDK.
---
The SDK is woefully lacking.
I have a main computer with MSFS 2020 running and Little NavConnect (2.6.1) and it says "connecté to a simulator".
On another computer, i have LittleNavMap (2.6.1) running and connected to the main computer as it Little NavMap says 'it is connected to a simulator or Little NavConnect. Prepare....'
I have loaded a flight plan in MSFS, and I m ready to take off. But on the second computer, I see nothing.
I have dowloaded the scenery from the main computer and it seems ok, because i see all airport...
Did i missed something?
Thanks for the help.
In the meantime - I've been using Plan-G. Works well, though not as full featured as LNM. Also it just connects up without a Little NavConnect equivalent - just uses the MSFS2020 SimConnect that's already there.
https://www.littlenavmap.org/manuals/littlenavconnect/release/2.6/en/