Hi Jacek,

Firstly, that link is not available outside the US. Second, if the runway has been extended then I'm pretty certain you're still picking up the older (FSDT?) one as the runway length is identical in your post and mine. 7955ft.

Did you use GSX to check which BGL it's using?

Reading this notice suggests 09L will be redesignated 09R.  https://www.airport-technology.com/projects/chicago/

3 minutes ago, Ray Proudfoot said:

Hi Jacek,

Firstly, that link is not available outside the US. Second, if the runway has been extended then I'm pretty certain you're still picking up the older (FSDT?) one as the runway length is identical in your post and mine. 7955ft.

Did you use GSX to check which BGL it's using?

Reading this notice suggests 09L will be redesignated 09R.  https://www.airport-technology.com/projects/chicago/

I did check and GSX is using the correct file from DD's scenery, the other ADE file from FSDT is no longer on my HD. So here is the question - should MakeRwys.exe be in the root P3D directory or where the scenery.cfg is? I know things have changed significantly recently, maybe I have it in the incorrect directory? 

Jacek,

MakeRwys.exe needs to be in your main P3D folder. Do you have Lorby's freeware Addon Organizer? MakeRwys.exe can detect it and read all the scenery add-on entries. If you don't then it won't that could explain why RC4 is not using the DD BGL. This can be seen by looking at the runway lengths using ADE.

Note 09R is 11247.7ft long in that one proving RC4 is not using that one.

Are the RC's coordinates to the start point of the runway?

I've spent a little bit more time on this tonight. P3D is definitely using the correct ADE for DD's scenery. It is RC that is not reading KORD_ADE.bgl from the scenery directory as it surely is keeping the FSDT's configuration from a while ago. The longitude for DD's 9R is completely different that FSDT's ADE. I loaded both of these bgls into ADE tonight to confirm and these coordinates in r5 file are surely FSDT's.

How does the rebuilding process work when the scenery.cfg and the actual add on scenery files are completely on different drives? I used to keep FSDT's scenery on the same drive as P3D, I think that's what's being cached in the r5 file in the P3D root. I can probably reinstall Chicago and temporarily place it in the P3D Addon directory just for the purpose of scanning and then move it to my usual drive to see if that will take care of the RC's db rebuild. 

Edited June 5, 20197 yr by Drumcode

Yes, it will use the start point. But I asked you whether you have Lorby's Addon Organizer installed. You didn't answer. Is KORD installed into an addon folder or scenery.cfg? If the former then without Addon Organizer you won't be able to see where it is in the loading order and MakeRwys won't be reading the BGL. That's why you're not getting the correct entries for RC4.

From memory MakeRwys creates a huge file named Runways.txt in the main P3D folder. Examine that for all KORD entries. Default will be first followed by the DD ones. The location of addon scenery is irrelevant. The paths are stored in either scenery.cfg or in the relevant add-on folder under MyDocuments\Prepar3D v4 Files

Edited June 5, 20197 yr by Ray Proudfoot

I only just installed Lorby's AO yesterday, but I'm not really familiar what it is supposed to do. I'll check the runways file tonight after work.

All my addon sceneries are installed on dedicated drive. Add-on xmls in the directory you've mentioned and scenery.cfg in LM's folder in Program Data. I have no scenery installed in the P3D root directory apart from ORBX stuff. 

Edited June 5, 20197 yr by Drumcode

Lorby's utility allows you an overview of the contents of scenery.cfg and all your addon scenery which of course have no entry in scenery.cfg. You can move entries up and down as you wish. Make sure DD KORD is near the top and check there is no entry for FSDT Chicago O'Hare.

But crucially for MakeRwys it scans the contents of your addon folder so will add DD KORD to the files that eventually feed RC4.

Two things not already mentioned here--first, there's this note from Pete's readme: "Those Prepar3D version 3 and 4 scenery installs abiding by the new L-M system for add-ons will NOT be seen by MakeRunways unless you copy the LorbySceneryExport program from the ZIP into the Prepar3D folder, to sit beside MakeRwys.exe"  This is not the same as having Lorby-SI's P3D Addon Manager installed.

So make sure you not only have makerwys.exe in the main P3D folder, but also the LorbySceneryExport.exe that is included in the same zip file as makerwys, otherwise none of your xml-based scenery is processed by makerwys.

Second, you need to run makerwys as admin for it to work properly with the various P3D xml folders.

Regards

6 hours ago, w6kd said:

Second, you need to run makerwys as admin for it to work properly with the various P3D xml folders.

Bob, you beauty! That was it! 🙂  I could easily see all the sceneries getting scanned too!

Thanks to everyone for the input! 

KORD,0091,42.002842,-87.926582,668,93,7500,111.75
KORD,0092,41.983891,-87.931648,668,93,11248,110.50
KORD,0093,41.988289,-87.931671,668,93,11220,110.90