There are only NHATA, PANCA, PHUSA, SUIDA 1C arrivals. 1As and 1Bs are missing. Also all the ANKIN, BANKE, COTUN, HUNTA, SOTEN arrivals are missing totally. They are all found with the default sim navdata.
the reason is simple, the default scenery is incomplete because in the sim you see only one runway 02L/20R
… but in real, you have two runways 02L/20R and 02R/20L:
The logic in the sim is now, when the sim can´t assign a procedure to a runway (because the runway isn´t available in the sim or the runway-ident is differ), then the sim suppress/disable all STARs for this airport. The STARs are included in the data, but not visible due this internal sim logic. Sorry.
There are a few examples here in the forum, but one is PHNL:
As soon, as the runways are available, you will see the STARs also immediately (as in the PHNL posting describe). Sorry, but thats not a navdata issue.
Then why do all the STARs work with the default navdata? Every single one is shown in the A320 FMS. Only with Navigraph data installed it shows those 4 STARs. If I’ll try to choose runway 02R, then it says no STARs but it does give them for 02L…
Because they don´t export STARs where they don´t have runways …
When you look on the charts, you will see, that some charts are for ALL runways, all STARs what you´re also seeing in our dataset. But most of the STARs are runway-specific STARs and that´s exactly the limitation in the sim. Again, when you read the PHNL posting in detail you see exactly the same behavior. The data are still included but not visible due the missing runway.
Sorry, we may not add runways to an existing airport - and therefore we must live with this sim-limitation for the moment. Add the runways to this airport by yourself and you will immediately see, that all STARs are included in the current AIRAC cycle. This is not a navdata issue.
Sorry we may have some language barrier here but I really don’t understand what prevents showing the runway-specific STARs with Navigraph data. What is limiting it? If I uninstall Navigraph data, then with the default database I can select all the runway-specific STARs. And with Navigraph data only those for all runways. I get the point that with a missing runway theyre all hidden but why arent they hidden with the default database?
The sim … not we, because the data are included in the AIRAC update.
Here are the STAR which are NOT showing in the sim due the missing runway (yellow marker):
… and here are the STARs where the sim can assign all runways because they are available in the default scenery (green marker):
Again, the logic in the sim is now:
When a STAR was found, where the sim can´t assigned a runway (ie. AKNIK1A 02R), then the STAR will be disabled/suppressed completely, also for the runway which exists (in the example case AKNIK1A 02L). That´s the logic in the sim and not in our data. The data still contains the AKNIK1A for 02L and 02R - but this STAR will not be shown, nor can select due this internal logic.
Here a screenshot from our parsed data on the AKNIK1A example - you see, both runways are included but this STAR will not be shown:
Read the reference PHNL posting, this was exactly the same issue also confirmed by one of our user, which had created the missing runways to test this. After that, all STARs were available …
Hope it´s clear now … the data are included but will not be shown due the missing runway. Please report this missing runway (because the runway exists in real-world) to ASOBO, as far they have added it - you will see, and you can select the missing (yellow marker) STARs.
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.