No Stars into KORD

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

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

Cheers,
Richard

PS: the location of the content.xml file find you in the FAQ here

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

1 Like