Hi, I am a developer of many payware sceneries. My customer recently noticed that LBBG and LBWN doesn’t have SID/STARs. I remember they had. He passed me a link saying that it may be caused by mismatch between default runway names/idents and add-on’s runways.
I deleted my scenery and checked them. By default their runways tagged as
LBBG: Runway 4 - Runway 22
LBWN: Runway 9 - Runway 27
BUT It should be
LBBG: Runway 04 - Runway 22
LBWN: Runway 09 - Runway 27
Deletion of “0” prefixes in new base nav data for LBBG and LBWN causes SID/STARs to disappear when my add-on installed.
There are nothing i can do in the SDK because you can’t select runway numbers without “0” in front.
Recent updates in MSFS nav data causes this mismatch. Please fix the default base nav data. Other airports still have runway with “0X” but in LBBG and LBWN it is broken.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- Start in safe mode
- Check the LBBG and LBWN runway names
- See they don’t have 04 and 09, they have 4 and 9 and it is also mismatching with the real life
Screenshots and Example
This is how it looks now:
And how its on my addon, how it should be and also how it was on previous msfs base nav data below:
The 0 prefix is UI-only (and I am not sure why it was changed). The numbers are stored as integers, and compared as integers for SID/STAR matching. The problem would be something else. Are you sure your scenery does not have some delete flags for navdata set?
I am seeing SID/STARs for all of these runways in FS2020 (live and SU16 flighting) and FS2024 without your scenery installed.
Hi,
I don’t mean to be rude but I know my work. I’ve flown here countless times and used SID/STARs. Suddenly, I can’t see them when my scenery installed for both versions of the game. No updates for my scenery but it seems something is now not matching. See the link please: Missing SIDs/STARs or IAPs without runway-idents on some airports - Known Issues - Navigraph (This is the mismatch I am talking about. But my mismatch is caused by those missing zeros.)
BTW, As much as i can see all the other airports’ runways still named with “0” prefixes. So no “0” is not an ui thing.
@tracernz is aware of this, as he is the developer who has handled navdata code inside the sim, and has also worked on the exact issue you have linked. He is also correct: the sim C++ code does not compare the runway numbers as strings at all, and there is no point in the navdata loading code where SID or STAR matching would operate based on a leading 0 or not leading 0.
Inside the sim, runway numbers are stored as a single C style enum which expresses them from 1 to 36 (i.e. RUNWAY_NUMBER_ONE, RUNWAY_NUMBER_TWO, etc). You can also see in his screenshot that the runway is listed as 9 in the UI instead of 09 for LBWN departure and yet there are two 09 departures available, further illustrating the underlying C++ code does not distinguish. So, something else must be at issue here, although I’m not totally sure what.
Do you have the XML of the airport definition for your scenery? Perhaps it would shed some light on the issue.
Thanks,
Matt
Hi,
@NAVData was able to install your scenery and notice that it indeed does have the flags set to delete navdata: https://forum.navigraph.com/t/how-can-i-be-sure-navigraph-data-is-overriding-incorrect-asobo-data/19855/3. To fix it, make sure all the items shown in a green line below are not checked. Each of them will cause part of the navdata to be deleted, and they should only be used if you really intend that.
1 Like
Hi @tracernz,
We have set these types in our data, so I`m unsure what you mean here … I don´t understand the reference link either … What should we set where? 
Thanks,
Richard
Not to add to the confusion but AG Sim have updated their scenery and it is now working.
Richard, we spoke separately about this and you also provided the ‘priority’ fix for Navigraph data to ‘surround’ all airports. I believe the original issue has been solved.
Thank you all
1 Like
Somehow those flags are ticked while we export for the MSFS Marketplace and that version is distributed through all the shops. I don’t know how did it got ticked but… Issue is now fixed. Thanks for your effort.
1 Like
Sorry for any confusion. I was giving you the credit for confirming the issue :).
1 Like
