MSFS 2020 & EDDM => white zone in Little NavMap

[Area]

Hello everyone,

I have EDDM from world update XVIII and I use Little NavMap 3.0.12.

In Little NavMap when I go to EDDM, I have a "huge" white zone, If I remove the folder "microsoft-airport-eddm-munich" no more white area, if I put it back: white area. See video: https://drive.google.com/file/d/1hBCD-HPdI_wFtqifc-vrcVMYps8NttQC/view?usp=sharing

At the end I display the version of LNM and the version of EDDM

Do you know how to make it disappear without deleting the airport?

Thanks in advance.

NB: again a big thank you to Alexandre Barthel for LNM 🤩

[albar965]

Thanks for the video. This helps.

Looks like a broken taxiway definition in the airport. You can deselect "Taxiways" in LNM options on page "Map Labels" in branch "Airport Details".

Unfortunately I see a lot of issues like this with the Microsoft add-on airports. They are quite a mess when it comes to the data structures.

I'll have a look at it and will try to find a workaround.

Alex

 

[albar965]

Just spot checked some MS airports and as far as I can see this only affects EDDM. The other major hubs look ok.
Still looking for a workaround.

Alex

[Allard]

1 hour ago, albar965 said:

Just spot checked some MS airports and as far as I can see this only affects EDDM. The other major hubs look ok.
Still looking for a workaround.

Alex

A workaround might be to purchase the Simwings version of the airport. It doesn't have this issue.
But with MSFS2024 around the corner things may be different. I assume most WU airports have been updated.

[albar965]

Here is also a freeware EDDM: https://flightsim.to/file/56933/eddm-munich-franz-josef-strauss-airport

Keep in mind that you have to exclude the MS airport from loading in LNM options on page "Scenery Library Database". Otherwise the MS add-on will override your add-on in Community.

(Ignore the paths. These are from my Linux development computer)

Alex

[Allard]

45 minutes ago, albar965 said:

Keep in mind that you have to exclude the MS airport from loading in LNM options on page "Scenery Library Database". Otherwise the MS add-on will override your add-on in Community.

That is not necessary. If @Area is going to use another airport than the WU one, that airport will need to be removed in the MSFS Content manager anyway which will also prevent it from being detected by LNM.

But your suggestion can be used as a workaround: It will tell LNM to ignore loading the WU version of LNM.

[Area]

Thanks, @allard but your solution would cost me 23€ and removing EDDM from Microsoft content means depriving me of a beautiful scene and so why buy a "Premium de luxe" version.

@albar965, thank you for your attention to this problem. To fix it by "tinkering", I took out the EDDM folder and updated the scene library database (as in the video). But your software is definitely complete and well done and I followed your advice that I did not know "Keep in mind that you have to exclude the MS airport from loading in LNM options on page "Scenery Library Database"" and it works!!!

Thank you very much.

Edited November 17 by Area

[albar965]

2 hours ago, Area said:

@albar965, thank you for your attention to this problem. To fix it by "tinkering", I took out the EDDM folder and updated the scene library database (as in the video). But your software is definitely complete and well done and I followed your advice that I did not know "Keep in mind that you have to exclude the MS airport from loading in LNM options on page "Scenery Library Database"" and it works!!!

Glad to hear and you're welcome!

Alex