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

FPLN: Arrival page shows incorrect RWYs for some airports #8692

Open
StephN-B opened this issue Jun 23, 2024 · 2 comments
Open

FPLN: Arrival page shows incorrect RWYs for some airports #8692

StephN-B opened this issue Jun 23, 2024 · 2 comments
Labels
Bug Something isn't working

Comments

@StephN-B
Copy link

Aircraft Version

Development

Build info

{
    "built": "2024-06-20T01:51:42+00:00",
    "ref": "refs/heads/master",
    "sha": "c6c13868fd1abc4346d1001ba3f32b4565e8e5aa",
    "actor": "tracernz",
    "event_name": "manual",
    "pretty_release_name": "master:c6c13868",
    "version": "a32nx-v0.12.0-dev.c6c1386"
}

Describe the bug

This issue seems to have been introduced with #7692.

What I find is that, when I am planning an Arrival on the Arrival page, I see an incorrect list of available Approaches - at least for some airports. One example is EDDK.

EDDK has an ILS13L approach, but this approach isn't listed on the Arrival page. Instead an approach 14L is listed, which doesn't exist.

Expected behavior

Show the correct list of available Approaches, and allow their selection.
The below shows the correct selection, using the iniBuilds A320:
image
image
image

Steps to reproduce

  1. Enter a flight plan, either manually or via SimBrief: EDDS/EDDK
  2. Select FPLN
  3. Enter departure details (OK in the above example)
  4. Try to enter arrival details for RWY ILS13L -> runway is not available:
    image
    image
    image

References (optional)

List of RWYs at EDDK according to Navigraph:
image

Additional info (optional)

No response

Discord Username (optional)

StephN-B

@StephN-B StephN-B added the Bug Something isn't working label Jun 23, 2024
@Saschl
Copy link
Member

Saschl commented Jun 23, 2024

I suspect there is a mismatch between navdata and scenery. Please make sure that:

  1. Navigraph data is up to date if used
  2. Any 3rd party EDDK sceneries are updated (EDDK from Aerosoft got updated fairly recently as the runway numbers changed)
  3. If nothing of the above helps try with an empty community folder (besides the A32NX). The base sim should have the correct runways after a worldhub update (at least it was submitted in April 2024)

@StephN-B
Copy link
Author

Thanks @Saschl for those tips, but unfortunately no joy on my side.
I can confirm that my Community folder is cleared out to the minimum content:
image

and that the Navigraph Data are all up-to-date:
image

The issue still persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants