Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scenery Library Builder does not recognise some third-party airports in MSFS #819

Closed
marbleflower opened this issue Nov 26, 2021 · 2 comments
Assignees
Milestone

Comments

@marbleflower
Copy link

Hello, I've noticed this issue earlier but I wasn't certain it was an issue with the program until after I updated to SU7. After updating to SU6 and Little NavMap to version 2.6.17 in October, I've noticed that the scenery library builder is not marking all of my third party add-on airports with a yellow outline, for example KDCA https://flightsim.to/file/1071/kdca-ronald-reagan-washington-national-airport meanwhile nearby KIAD by the same author https://flightsim.to/file/1113/kiad-washington-dulles-international-airport is marked as expected. This is also present in some other airports by other authors like CYUL https://flightsim.to/file/1691/cyul-montreal and CYQX https://flightsim.to/file/6912/cyqx-gander. I tried this with both the stock Navigraph database enabled and disabled. Building the scenery library in v2.6.16 recognises the add-on airports as expected.

Little NavMap v2.6.17
Windows 10 64 bit
Screenshot (1116)
![Uploading Screenshot (1114).png…](
Screenshot (1115)
)

MSFS 2020 v1.21.13.0
Screenshot (1113)
MSFS Stock data
Screenshot (1111)

Screenshot (1112)
Logfile link leads to a deadlink
1250410_20211126223723_1
1250410_20211126223737_1
1250410_20211126223745_1

@albar965
Copy link
Owner

Thank you for the detailed report. Looks like a duplicate for #798 but I keep it for the examples. Will try to fix for 2.8.

@albar965 albar965 self-assigned this Nov 28, 2021
@albar965 albar965 added this to the Release 2.8 milestone Nov 28, 2021
@albar965
Copy link
Owner

albar965 commented Apr 4, 2022

Tried all three airport add-ons with 2.7.9.develop and these are recognized now, no matter if Navigraph is installed or not.

image

albar965 added a commit to albar965/atools that referenced this issue Apr 4, 2022
…X and P3D which apparently does not apply to MSFS.

Before a feature was not updated if the new airport did not contain new features like aprons or taxiways. Example LICC add-on.

Changed closed airport detection to avoid wrongly enabled airports LANO and KODX. Airport close flag now always results in a closed airport. Even if runways are open.

albar965/littlenavmap#819
albar965/littlenavmap#802
albar965/littlenavmap#798
@albar965 albar965 closed this as completed Apr 4, 2022
albar965 added a commit to albar965/atools that referenced this issue Apr 8, 2022
…X and P3D which apparently does not apply to MSFS.

Before a feature was not updated if the new airport did not contain new features like aprons or taxiways. Example LICC add-on.

Changed closed airport detection to avoid wrongly enabled airports LANO and KODX. Airport close flag now always results in a closed airport. Even if runways are open.

albar965/littlenavmap#819
albar965/littlenavmap#802
albar965/littlenavmap#798
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants