Dear navdata team, I’m using MSFS 2024, with navigraph hub installed for up to date navdata. I have recently downloaded a new freeware scenery that adds rwy 16/34 for Kuwait airport ( https://flightsim.to/file/100331/kuwait-international-airport-okkk ) in this scenery the developer has suggested moving the order of the package order on the simulator. However when I use fenix or PMDG the SIDs and. STARs with ILS all appear on the mcdu/fmc. Unfortunately when I use inibuilds A320neo, the STARs have completely missing waypoints. And when I use FBW A32NX there is absolutely not SIDs or STARs to chose at all (neither are the approaches). Is there anything that can be done to resolve this?
Hi…,
What is the status if you uninstall the freeware scenery and use stock scenery?
Cheers
Ian
Hi Ian. Stock scenery without navigraph has nothing. No SIDs or STARs. Are we meant to not change the package reorder tool? If I don’t change the reorder then there is absolutely nothing. Below is a an example of what the new reorder looks like…
And if you use Navigraph and stock scenery? If this works then the freeware scenery needs to be made compatible with MSFS2024 .
See also FAQ - MSFS2024 (SU3 and above) - airport, procedure, waypoint, 3rd party & flightplan import issues
Cheers
Ian
IIRC the default scenery still has the old ICAO code (OKBK) – at least in 2020 but possibly also 2024 – so using default scenery would also result in unavailable procedures albeit for a different reason.
Regards,
Tim
The odd thing is fenix and pmdg is picking up all the correct STAR/SID, because it has external nav data. Inibuilds or fbw is dependent on MSFS navdata albeit with navigraph injected data
Correct, and that is precisely the difference and the limitation here. We may not modify existing airport identifiers or runway identifiers in the stock sim.
When you use 3rd-party sceneries, they must be 100% MSFS 2024 compatible and may not include the navdata delete flag. With SU3, numerous changes were made to ensure the correct loading order of the packages. When the scenery is not fully compatible, you run into such issues.
In other words, when all these recommendations from the posted link from Ian don’t help, then you must contact the scenery designer to fix this. The recommendation from the dev to use the re-order tool is a first indicator for me that this scenery is not fully compatible.
As I have written, it is also possible that the scenery includes the delete all navdata flag, but again, we can only speculate on the reasons.
As you can see in the navdata for Fenix, PMDG, Just Flight, iFly, and others, which utilize an external database (independent of the MSFS logic), we provide the correct data. So this issue is not navdata related …
Please get in touch with the scenery designer.
Cheers
Richard
P.S.: According to the re-order tool, you only need this tool when you want to use your own navdata from a 3rd-party scenery. In that case, you must shift the 3rd-party package under our packages. In all other cases, you don’t need it since SU3 - as long as the scenery designer has done their work to make their scenery SU3+ compatible.
Just an update to this:
The 3rd party scenery delete approaches, arrival and departures … so it is a scenery issue even when you re-order it:
Here, directly from the scenery:
Additionally, the classification of the package is incorrect, but this is also a scenery development customization.
So, no navdata issue - 3rd party scenery issue.
Cheers,
Richard
Thanks Richard. I’m very grateful for your help in looking into this. I have contacted the developer. Is there anything I need to communicate to the developer with regards to how he can rectify this issue and make it SU3+ compatible?
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.