This is all I get when I run the scenery library database (Airports 83759, ILS 258 and Waypoints 343). I've added the correct streamedpackages folder in option/scenery library database c:\Users\Me\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\StreamedPackages\.

I'm running Little Navmap version 3.0.15.rc1 and sim version 1.3.23.0 (Steam). The sim is running and is connected.

Is there something I can do to sort this out?

Harry

Edited March 7, 20251 yr by HarryS
Added Text

14 hours ago, HarryS said:

This is all I get when I run the scenery library database (Airports 83759, ILS 258 and Waypoints 343). I've added the correct streamedpackages folder in option/scenery library database c:\Users\Me\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\StreamedPackages\.

I'm running Little Navmap version 3.0.15.rc1 and sim version 1.3.23.0 (Steam). The sim is running and is connected.

As mentioned in the changelog: LNM does not use any folder like streamedpackages to load airports and navaids. You cannot even change the folder in LNM for MSFS 2024. All is loaded directly from SimConnect. 

You can send me your log file: https://albar965.github.io/contact.html

Maybe I can see something in there.

Alex

Hi Alex,

Thanks for the reply. The problem turned out to be a corrupt 3rd party airport. A shame we can't separate 3rd party airports from default airports on the map like 2020. I know you can tag the 3rd party airports. Just not the same. I understand that simconnect doesn't tell you which is which.

Anyway thanks again for the reply.

Regards,
Harry

16 hours ago, HarryS said:

Thanks for the reply. The problem turned out to be a corrupt 3rd party airport.

Thanks for the feedback. Good to know. It's really bad that I cannot find out which one breaks the loading process. Before I could at least find the offender by looking at the log. Meh.🤕

16 hours ago, HarryS said:

A shame we can't separate 3rd party airports from default airports on the map like 2020.

Asobo at least acknowledged the limits. I still hope the SimConnect interface will be improved in the future.

Alex

It's the same with AI traffic. You can use FSLTL but you got to take the mainly unusable Asobo planes with it. Again one of the downsides of streaming. I'd really like the choice of streaming vs. loading it on the hard drive like 2020. Oh well....

Harry

On 3/15/2025 at 3:22 PM, albar965 said:

Thanks for the feedback. Good to know. It's really bad that I cannot find out which one breaks the loading process. Before I could at least find the offender by looking at the log. Meh.🤕

Asobo at least acknowledged the limits. I still hope the SimConnect interface will be improved in the future.

Alex

Hello Alex,

Is there a way to fake that MSFS 2020 is Installed for the "eyes" of Little Navmap to use the scenery library build function for this version of the simulator? I tried to create a fake Community Folder on the right place (C:\Users\*****\AppData\Roaming\Microsoft Flight Simulator\Packages\Community) the and didn't recognize. So I installed it fully, a waste of space.
The main reason here is that I don´t need the MSFS2020 installed, I only have to use it for the scenry build in LNM, which for the 2024 version doesn't work very well for me, doesn't compile well (or nothing) and the 2020 is perfect (I use the Linker to populate Community 2020 folder).
It's a workaround but is enough for me, would be perfect if I could unsinstall the MSFS2020 version and keep only the necessary folders for Little Navmap to recognize.
Thank you in advance!
Antonio.

1 hour ago, tcarmona said:

Is there a way to fake that MSFS 2020 is Installed for the "eyes" of Little Navmap to use the scenery library build function for this version of the simulator? I tried to create a fake Community Folder on the right place (C:\Users\*****\AppData\Roaming\Microsoft Flight Simulator\Packages\Community) the and didn't recognize. So I installed it fully, a waste of space.
The main reason here is that I don´t need the MSFS2020 installed, I only have to use it for the scenry build in LNM, which for the 2024 version doesn't work very well for me, doesn't compile well (or nothing) and the 2020 is perfect (I use the Linker to populate Community 2020 folder).
It's a workaround but is enough for me, would be perfect if I could unsinstall the MSFS2020 version and keep only the necessary folders for Little Navmap to recognize.

Hi Antonio,

have a look at this FAQ entry: https://albar965.github.io/littlenavmap-faq.html#msfs-scenery-library

Create the Community and Official\OneStore folders.
Create a text file C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt which should contain one line:

InstalledPackagesPath "C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages"

Create an empty text file: C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-base\layout.json

I'm not sure if this is enough. You most likely also need the MSFS folders fs-base, fs-base-genericairports and fs-base-nav populated with files.

What is the problem with the MSFS 2024 scenery build? It's working quite reliably for me, albeit slowly (10 minutes). I'd rather have a look at this. It would help if you start the MSFS 2024 loading, let LNM crash or quit it if hanging and then send me an issue report (LNM menu "Tools"). Maybe I can help with this.

Alex

Hello Alex,

Thank you very much for your quick awnser!
Yes I would rather to fix 2024, yes.

Anyway, I compilied it again and what it gives me is this: after 4 minutes and 52 seconds 85076 Airports, 47 ILS, 118 Waypoints, 1 NDB, Rest 0.
I sent you an email with the screenshot and the report as you asked, but it didn't froze or crashed... never did actually.
I have the Steam edition for both simulators so, if this doesn't work I will follow the link you sent (FAQ) for this version.
Let see if we fix the 2024!

Thank you for your time

Antonio.

 

 

On 6/6/2025 at 5:33 PM, tcarmona said:

Thank you very much for your quick awnser!
Yes I would rather to fix 2024, yes.

Anyway, I compilied it again and what it gives me is this: after 4 minutes and 52 seconds 85076 Airports, 47 ILS, 118 Waypoints, 1 NDB, Rest 0.
I sent you an email with the screenshot and the report as you asked, but it didn't froze or crashed... never did actually.
I have the Steam edition for both simulators so, if this doesn't work I will follow the link you sent (FAQ) for this version.
Let see if we fix the 2024!

I see that you have the Navigraph navdata update installed in LNM and MSFS. Then you can simply ignore the missing NDB and VOR since these are fetched from the update Navigraph databases in LNM. Make sure to have "Select automatically" enabled in the menu "Scenery library" -> Navigraph.

Still, it is strange that the navaids are not loaded. I have to check.

Alex

Hello Alex, is (was) set to "automatically".

Don't know if it matters, but the MSFS2020 compiles ok.

Thanks!

Antonio.

Just now, tcarmona said:

Don't know if it matters, but the MSFS2020 compiles ok.

MSFS 2024 loading is completely different to MSFS 2020. LNM reads BGL and other files from the MSFS 2020 scenery library to build the databases. No files are read from MSFS 2024. All is transferred using the more or less stable SimConnect interface while '24 is running.

I'm testing right now and see crashes with the latest MSFS 2024 beta but only having the Navigraph navdata update installed. No idea yet what is going on there. 🤷‍♂️

Alex

Ok. Loading MSFS 2024 with Navigraph seems to work again. No idea what caused these strange crashes. Sometimes it helps to restart MSFS 2024.

Alex

Hello Alex, 

Thank you for your time.

It doesn't work for me, with or without navigraph (scenery Library » Do not use...).

No problem, I use tyhe MSFS2020 Scenery way of doing it.

Time to time I we'll try it.

Thanks again 

Antonio.

3 hours ago, tcarmona said:

It doesn't work for me, with or without navigraph (scenery Library » Do not use...).

That is not what I meant. I'd set this back to automatically.

Try to uninstall the Navigraph update in MSFS and reload in LNM. Maybe it helps. You can reinstall the Navigraph update again after loading.

Alex