My problem trying to fly to Flightzone's Portland (KPDX), with RD4 was fixed. It was too easy. I found the answer here on the RD4 fourm. I'm showing the fix here again so that someone new with the problem will not have to search for the answer. It will be here, at least for awhile:The critical fix is as per John Burgess advice as follows:"if you rename KPDX_28L_ILSFIX.bgl as !KPDX_28L_ILSFIX.bgl all may be well:This simple fix works fine for me. This is the steps I took:-1. Locate the file KPDX_28L_ILSFIX.bgl (It is located under FlightZone02_SCScenery)2. Rename it to !KPDX_28L_ILSFIX.bgl3. Launch FS9 to ensure the Scenery.cfg is updated4. Exit FS95. Launch Radar Contact 46. Click Rebuild Scenery DB to update RC4 data.The two programs should then happily work together.Hopefully John or Ron will comment if I have this wrong.Cheers,Warren"Having fixed that problem a few other questions came to mind. Can anyone answer them? Please: Also suggested was to install the new version of "Make Runways Beta_398" obtained from the same man that makes the FSUIPC" programs ( sorry, I cann't remember his name). As it turned out I did not replace the default version of this .exe as I fixed my problem without doing so. From someone who knows:1. Should this new version be installed into FS2004?2. What does "running" this program do?3. If and when should this program be run?4.Does running this program do the same thing as running the "Rebuild Scenery DB" in Radar Contact 4 ?One last question. Does the same type problem araise when using Flightzone's Providence Airport? Thanks jerrycwo4

I believe the same or similar problems occurred with KPVD as well. Here's one thread of a few:http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchThe makerwys criteria for runway recognition was changed to primarily remove as I recall the requirement for start locations. Some scenery developers were providing a patch that included a "delete all runways" statement and were adding them back in without start locations. Makerwys reads data according to the scenery.cfg priority and then within each scenery folder with ascii (letter code) priority as displaced as Windows Explorer - arrange by name. (Placing the "!" in front of the name changed its priority.)Makerwys 398 now uses runway length (among other items but not start locations) as its criteria. The length is such that phantom runways as used in the AFCAD work-around for making non-parallel runways simultaneously active are below this criteria and are excluded, unlike the ATC features of FS runway selections.This was done to address the problem universally as opposed to modifying things each time for specific sceneries.It should be noted the AFCAD v2.11 creates files that contain automatically the statement to delete all runways so without the makerwys modification an improper AFCAD file could cause the same problem.

Ron, thanks for the explination but it's WAY over my head. Could I just ask you to answer questions 1,3 and 4 above. With thoses answers I think I'll be okay. Thanks for the help. jerrycwo4

>1. Should this new version be installed into FS2004?Recommended as described.>3. If and when should this program be run?It will be called automatically. See below.>4.Does running this program do the same thing as running the>"Rebuild Scenery DB" in Radar Contact 4 ?>Running the "Rebuild Scenery DB" will automatically run the new makerwys.exe and create and copy the new data files over to RC4data.In other words, install the new makerwys.exe in your FS9 root folder, then start RC and run the "Rebuild Scenery DB" function and you are good to go.As usual, if you put in new or modify scenery or AFCADS always start RC and run the "Rebuild Scenery DB" function. That is all you need to do for a non-Wide FS system where RC resides on the same computer as FS9.

Ron, This is what I was looking for. Now I understand that when I "run" Rebuild runwasy DB which is insise of RC4, it uses the .exe. Makerwys to remake the runway data. Thanks for the good help jerrycwo4

>My problem trying to fly to Flightzone's Portland (KPDX),>with RD4 was fixed. It was too easy. I found the answer here>on the RD4 fourm. I'm showing the fix here again so that>someone new with the problem will not have to search for the>answer. It will be here, at least for awhile:>>The critical fix is as per John Burgess advice as follows:>>"if you rename KPDX_28L_ILSFIX.bgl as !KPDX_28L_ILSFIX.bgl all>may be well:>>>This simple fix works fine for me. This is the steps I took:->>1. Locate the file KPDX_28L_ILSFIX.bgl >(It is located under FlightZone02_SCScenery)>2. Rename it to !KPDX_28L_ILSFIX.bgl>3. Launch FS9 to ensure the Scenery.cfg is updated>4. Exit FS9>5. Launch Radar Contact 4>6. Click Rebuild Scenery DB to update RC4 data.>>The two programs should then happily work together.>>Hopefully John or Ron will comment if I have this wrong.>>Cheers,>Warren">>>Having fixed that problem a few other questions came to mind.>Can anyone answer them? Please:>> Also suggested was to install the new version of "Make>Runways Beta_398" obtained from the same man that makes the>FSUIPC" programs ( sorry, I cann't remember his name). As it>turned out I did not replace the default version of this .exe>as I fixed my problem without doing so. From someone who>knows:>>1. Should this new version be installed into FS2004?>2. What does "running" this program do?>3. If and when should this program be run?>4.Does running this program do the same thing as running the>"Rebuild Scenery DB" in Radar Contact 4 ?>>One last question. Does the same type problem araise when>using Flightzone's Providence Airport? Thanks jerrycwo4===================================================================="This simple fix works fine for me. This is the steps I took:-1. Locate the file KPDX_28L_ILSFIX.bgl (It is located under FlightZone02_SCScenery)2. Rename it to !KPDX_28L_ILSFIX.bgl"Perhaps my eyes are decieving me but what's the point of renaming a file when your entering the exact same information?

First, with the makerwys beta 398, you should not need to rename the file. That was a temporary fix until the new version was coded with some different conditions for runway inclusion/exclusion which seems to be working for quite a few problem sceneries.What adding the "!" changed was the order makerwys read that file where files are in the same folder. It enabled runways that were excluded by that file to be replaced by another in that folder since with the "!" in the name that file was processed first in that folder. In the "computer alphabet" order of things "!" has the lowest value. If you open that folder in Windows Explorer you will see that "!ILS..." appears first. If for example there is an AF2_ file in that folder this means that makerwys processed the "!ILS..." file before the "AF2_" file which restored what was needed. It was confirmed by the scenery designer that renaming the file would cause no harm to FS processing his scenery.