I noticed that LittleNavMap doesn't show add-on airports that are purchased via the marketplace. it still seems to depict the base airport.

Example: 1S2 (Darrington):

LNM shows:
Scenery

Base Airports	D:\Microsoft Flight Simulator\Official\OneStore\fs-base\scenery\0101\APX15140.bgl
Base Navigation	D:\Microsoft Flight Simulator\Official\OneStore\fs-base-nav\scenery\0101\NAX15140.bgl

In reality it is installed in d:\Microsoft Flight Simulator\Official\OneStore\orbx-airport-1s2-darrington\
This happens with many if not all airports purchased in the marketplace.

I have tried loading the scenery again, even deleted the AppData\Roaming\ABarthel folder to start again, but that doesn't solve the problem.
Is there a solution, apart from not using the marketplace to purchase addons?

Edit: I should pay better attention to the release notes. Those addons are encrypted and thus not showing. Too bad developers haven't thought of this beforehand, they could easily have solved this by adding an unencrypted file to be read by other third parties with just the information they are happy to share.

 

 

Edited December 22, 20205 yr by orchestra_nl
read the release notes

Yes. Sorry. Unfortunately they encrypt everything. Locking down texture files or other stuff would be sufficient but no ... ¯\_(ツ)_/¯
Alex

On 12/22/2020 at 6:33 PM, albar965 said:

Yes. Sorry. Unfortunately they encrypt everything. Locking down texture files or other stuff would be sufficient but no ... ¯\_(ツ)_/¯
Alex

I have the same case but with freeware. Example: https://flightsim.to/file/5105/lgir-heraklion-airport-n-kazantzakis-crete

The file structure is ok but it doesn't show up with yellow marking.

2 hours ago, earthdog said:

The file structure is ok but it doesn't show up with yellow marking.

Just tried. It's not recognized at all. No idea what's going on there. Needs a lot of debugging.😦

Alex

5 hours ago, earthdog said:

have the same case but with freeware. Example: https://flightsim.to/file/5105/lgir-heraklion-airport-n-kazantzakis-crete

The file structure is ok but it doesn't show up with yellow marking.

Thanks for the link. Just tried it. This is one of the cases where an add-on airport just adds textures and/or 3d objects. The BGL files do not contain airport structures like runways or aprons. Sorry, but there is no way LNM can detect these as add-on. Names in manifest or folder names are too random to extract and aiport ident.

Alex

22 minutes ago, albar965 said:

Thanks for the link. Just tried it. This is one of the cases where an add-on airport just adds textures and/or 3d objects. The BGL files do not contain airport structures like runways or aprons. Sorry, but there is no way LNM can detect these as add-on. Names in manifest or folder names are too random to extract and aiport ident.

Alex

I see. Yeah sure you cant start guessing.. Thanks for your time to check it out!

For some reason an Orbx airport does not show as addon while other Orbx airports do.

The airport info are all there in the BGL file but LNM does not see it, possibly because the BGL has a space in the name? It is called 'xml placements.bgl'
Hope this can help identifying the problem

 

 

4 hours ago, peroni said:

The airport info are all there in the BGL file but LNM does not see it, possibly because the BGL has a space in the name? It is called 'xml placements.bgl'
Hope this can help identifying the problem

Spaces cause no issues. Neither should special characters. But the airport probably adds only scenery elements and keeps the same airport layout from stock.