KORD, Chicago O'hare has runways with strange designations currently. Runway 9R/27L was renamed runway 10/28, and runway 9L/27R was renamed as 9R/27L. I have an updated AFCAD file which reflects this, and the runway designations are correct in the afcad, I've checked them myself a number of times. Yet RC4 is still calling them by their old designation. I have run the Rebuild Scenery DB a million times with the latest version of Makerunways downloaded from the link at the top of the forum recently (I'm constantly adding other airports and updating AFCADs) but RC4 is still using the old, incorrect designations for the runways. Where is it getting this incorrect information from?

follow the instructions posted at the top of the forum, and send me a .logbe SURE you click debug, before loading the .plnwhat version of makerwys.exe is in the root of fs? 4.26 is current.as you are running rc/fs, and you hear a bad runway call, you can stop everything, and send me a .logtell me who said what runway, and why that runway is wrong.jd

I have makerunways 4.25 which I downloaded last month. Looks like 4.27 was just released today so I'll install that and try the log.Approach and tower were both calling runway 10 as runway 9R.

get the latest, rebuild the database, and make a log for mejust click debug before loading the .plnjd