Version: 1.3.23.0
Frequency: Consistently
Severity: Blocker
Bug description:
When the runways on a stock airport are outdated, and you use a third-party scenery to update them (changing runway idents and/or adding new runways), you see the new runways in the EFB. Still, you can´t select procedures for these new runways (arrival, departure, etc.).
Repro steps:
Attachments:
3rd party scenery for VOBL - all runways are selectable - in the stock scenery, you have only 09L/27R, but 09R/27L is completely missing:
… from the stock Inibuild A321:
When you select runway 09L (which is present in the stock scenery) - you can select the procedures:
… and again from the stock Inibuild A321:
When you do the same with the newly added 09R (which is NOT present in the stock scenery) - you see and can´t select any even when the procedures are included in the data:
… and also here from the stock Inibuild A321:
In short, even when the runways are available (correct runway idents and/or correct airport layout), and the procedures are included in the BGLs, you can´t select any procedures for these new runways—not in the EFB nor in any other stock aircraft.
You see in the NAX68270 file that these procedures are included with the correct runway 09R, but this procedure (and all others) is not selectable, even when they exist in the data.
The third-party scenery package will be loaded correctly and has the new package_order_hint in the manifest file. The scenery will be loaded correctly (you see that all runways are available). So, it´s not a third-party scenery issue nor a third-party data issue—it looks like the MSFS2024 uses only the stock scenery for the linkage between procedure and runways and doesn´t use the third-party scenery as the root scenery.
Cheers,
Richard
