With the Navigraph simulator base package installed, there are no airport procedures for ZSHC Hangzhou Xiaoshan airport. Tested with AIRAC 2602 rev.1 in MSFS 2024.
For the test, I used the default A320 MCDU. As can see, SIDs, STARs, and Approaches are not selectable:
Hi Ashleigh,
Thank you for your report. It seems you have an incompatible package on your system, which disabled our 3rd-party navdata.
Do you have a 3rd-party scenery installed? When yes, which one? Have you tried this FAQ?
As you mentioned, the procedures are visible/selectable in Fenix, PMDG, … The procedures are also available in the MSFS navdata package, but another package on your system overrules the data.
Please follow the steps in the FAQ exactly and let us know your results.
Thanks for the reply. I should have also mentioned that this was at the default auto-generated scenery, i.e. with no third party scenery installed.
So the test was default scenery with default aircraft. With default navdata, all the procedures are there, however when replace default navdata with Navigraph navdata, then there are no procedures. I.e. the only change on the system is whether Navigraph base sim navdata is installed or not.
It would suggest the procedures are missing or disassociated with the Navigraph base sim navdata specifically?
I will follow-up later today with excluding everything.
Hi again Ashleigh,
We think we have identified the issue … the data are included as I have written before, but
As you may know, we “create” the airports, including runways and facilities that do not exist in the sim, to be in sync with all our apps. To do this, we compare the airports in the sim against our airport database, and here I have identified an issue (sorry for that). ZSHC was not found, so our adapter created it. But that was not true, because ZSHC is included in the stock sim. Here is the culprit: why the SIM does not offer our data correctly.
Ashleigh, we will fix this, of course, and you should expect it by the latest with AIRAC 2603. We may create a 2nd revision for 2602, but we will discuss this internally first. I hope this is ok for you. As soon as I have any new information for you, I will inform you here.
Thanks again for this valuable report! Much appriciated …
Thanks for looking deeper into this and great news to hear you’ve found the culprit. It also makes me think that this situation may have come about because ZSHC was not in the original release of MSFS 2020 but has at some point in the last few years been added, perhaps even as late as with the new airport data that came with the release of MSFS 2024.
Of course, no rush to update it for me; the next update cycle works fine. I’ll of course come back to it after you’ve updated to confirm all works as expected on my install too.
