# No Stars into KORD

**URL:** <https://forum.navigraph.com/t/no-stars-into-kord/3939>\
**Category:** SID/STAR/APPR\
**Created:** [January 16, 2021, 12:57pm UTC](https://forum.navigraph.com/t/no-stars-into-kord/3939 "2021-01-16T12:57:24Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [January 18, 2021, 9:25am UTC](https://forum.navigraph.com/t/no-stars-into-kord/3939/7 "2021-01-18T09:25:13Z")

</div>

Jan, thank … yes, that´s exactly the issue - the sceneries will be loaded in order of the content.xml file. the order is: Top of the file lowest, bottom/end of the file has the highest priority. That means, when our package is BEFORE the FSDT KORD scenery (which now includes the new runways) our package can´t still assign the new runways because the FSDT KORD scenery has a higher priority as our package.

Therefore, move the FSDT KORD file (+ the ASONBO KORD scenery if still installed) before our package. The best place is between the “fs-base” line and the “fs-base-nav” line. Our package (navdata) will ALLWAYS be installed after the “fs-base-nav” line to disable the underlying NavBlue data.

Here, what I mean (and what @JKTech explained):  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/4/4250dc3fd35163e3f2c98d43c2bf9a7f4efd75e4.png)

Here the KORD STARs with the FSDT KORD scenery installed (with all runways):

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/2/2313cda0e5ecb2e275e53ff3b896b988b73d48a7.jpeg)

Cheers,  
Richard

PS: the location of the content.xml file find you in the FAQ [here](https://forum.navigraph.com/t/faq-location-path-of-content-xml-package-file/2798)

PPS: Thanks Jan - I have set your answer as “Solution” 😉

---

_[View the full topic](https://forum.navigraph.com/t/no-stars-into-kord/3939)._