I've run Make Runways multiple times since installing ImagineSim's KIAD over a year ago and every time I fly into or out of Dulles RC4 only recognizes Rwy's 1 L and 1 R. Rwy 1C is not recognized, even when I want to request a Rwy, 1C is not listed. I enter the correct path for MSFS when running make runway from RC4. And make runways has updated other add-on airports. Any ideas?

 

Todd

Are you running makerwys version 4.612 or later? 4.614 is current at:

http://forum.simflight.com/topic/66136-useful-additional-programs/

 

The current real world charts show these ILS runways:

• IAP : ILS OR LOC RWY 01R
  
• IAP : ILS OR LOC RWY 19L
  
• IAP : ILS OR LOC/DME RWY 01C
  
• IAP : ILS OR LOC/DME RWY 01L
  
• IAP : ILS OR LOC/DME RWY 12
  
• IAP : ILS OR LOC/DME RWY 19C
  
• IAP : ILS OR LOC/DME RWY 19R
  

Both C's have localizers.

 

Let's trouble shoot:

 

In your FS folder, open with notepad or wordpad (never a spreadsheet or database application) r5.csv. Search for KIAD. There should be 8 entries with 7 having localizer frequencies if your scenery is current.

 

From Pete Dowson's "MakeRwys ReadMe.txt" in your FS folder here's the field description of all:

 

"R5.CSV (RUNWAYS FILE for RCV5):

 

ICAO, Rwy*, Latitude*, Longitude*, Altitude*, HeadingMag, Length*, ILSfreqFlags*, Width*, MagVar, CentreLatitude, CentreLongitude, ThresholdOffset*,Status*"

 

RC4 copies r5csv to RCv4\data as r4.csv. Here's in part the runway field description:

"Rwy is nnn for runway number, then 0, 1=L, 2=R, 3=C, 4=W (water)"

 

I only have an older FS afcad type file prior to the the opening of the center 1/19 runways so here's my example less the center:

 

KIAD,0011,38.939075,-77.459778,313,10.840,11501,111.30BG,150,-10.200,38.954849,-77.459549,0,,

KIAD,0012,38.923748,-77.436447,313,10.860,11511,110.10BG,150,-10.200,38.939533,-77.436211,0,,

KIAD,0120,38.943768,-77.490479,313,120.880,10489,109.30BG,150,-10.200,38.938686,-77.473175,0,,

KIAD,0191,38.955318,-77.435974,313,190.860,11511,110.10BG,150,-10.200,38.939533,-77.436211,0,,

KIAD,0192,38.970623,-77.459320,313,190.840,11501,111.30BG,150,-10.200,38.954849,-77.459549,0,,

KIAD,0300,38.933605,-77.455872,313,300.880,10489,0,150,-10.200,38.938686,-77.473175,0,,

 

Disregard the first number. Here we have listed 1L and 1R, 12, 19L and 10R, and 30. If the center runway was recognized you would have 0013 and 0193 entries.

 

If you have those center entries let us insure that r5 got copied to the rcv4\data folder by opening in wordpad or notepad r4.csv. If they are not there but were in r5.csv then it did not get copied from your FS folder. For this case if RC and FS reside on the same PC you should be doing everything from with RC answering "no" to the Widefs question. If you have RC on a WideFS client networked PC to an FS host pc then you need to run makerwys.exe direct in the FS host pc FS folder and then run the scenery rebuild in RC on the client machine answering Yes to the WideFS prompt.

 

If you do not have the center runway entries in your r5.csv in your FS folder then there is probably a scenery priority or afcad type issue.

 

Let's take a look at the log makerwys.exe created. In Word or Wordpad open in your FS folder. It is a huge file so don't use notepad and even in word or worpad runs slowly.

 

Search for Airport KIAD. If FS9 the default airport found first has this entry (in part):

 

Airport KIAD :N38:56:40.2997 W077:27:20.9188 313ft

Country Name="United States"

City Name="Washington"

Airport Name="Washington Dulles Intl"

in file: Scenery\NAME\scenery\AP927180.BGL

 

Runway 1L/19R centre: N38:57:17.4560 W077:27:34.3888 313ft

Start 1L: N38:56:22.3533 W077:27:35.1791 313ft Hdg: 0.6T, Length 11512ft

Computed start 1L: Lat 38.939060 Long -77.459776

Start 19R: N38:58:12.5588 W077:27:33.5988 313ft Hdg: 180.6T, Length 11512ft

Computed start 19R: Lat 38.970638 Long -77.459322

Hdg: 0.640 true (MagVar -10.200), Concrete, 11512 x 150 ft

Primary ILS ID = IOSZ

Primary ILS: IOSZ 111.30 Hdg: 0.6 , Flags: GS BC "ILS 01L"

Secondary ILS ID = IDLX

Secondary ILS: IDLX 111.30 Hdg: 180.6 , Flags: GS BC "ILS 19R"

*** Runway *** KIAD0011 Lat 38.939060 Long -77.459778 Alt 313 Hdg 11 Len 11512 Wid 150 ILS 111.30, Flags: GS BC

*** Runway *** KIAD0192 Lat 38.970638 Long -77.459320 Alt 313 Hdg 191 Len 11512 Wid 150 ILS 111.30, Flags: GS BC

Runway 1R/19L centre: N38:56:22.3209 W077:26:10.3694 313ft

 

What is important here is the file path showing the data source.

 

Search for Airport KIAD again. In only have an older add-on afcad placed by Ultimate Traffic 2007. First this next hit should be a data deletion section:

 

..\..\..\PAI-AF2S\scenery\PAI_AF2_KIAD_DEFAULT.bgl

=============================================================================

Deletions check for Airport KIAD:

Delete all taxiways!

 

 

Delete all runways and starts!

 

*** DelBth *** KIAD0011 Lat 38.939060 Long -77.459778 Alt 313 Hdg 11 Len 11512 Wid 150 ILS 111.30, Flags: GS BC

 

*** DelBth *** KIAD0012 Lat 38.923748 Long -77.436447 Alt 313 Hdg 11 Len 11511 Wid 150 ILS 110.10, Flags: GS BC

 

*** DelBth *** KIAD0120 Lat 38.943768 Long -77.490479 Alt 313 Hdg 121 Len 10489 Wid 150 ILS 109.30, Flags: GS BC

 

*** DelBth *** KIAD0191 Lat 38.955318 Long -77.435974 Alt 313 Hdg 191 Len 11511 Wid 150 ILS 110.10, Flags: GS BC

 

*** DelBth *** KIAD0192 Lat 38.970638 Long -77.459320 Alt 313 Hdg 191 Len 11512 Wid 150 ILS 111.30, Flags: GS BC

 

*** DelBth *** KIAD0300 Lat 38.933605 Long -77.455872 Alt 313 Hdg 301 Len 10489 Wid 150

 

 

Delete all taxiways!

 

 

COM: Delete all frequencies!

=============================================================================

 

I highlighted the path again.

 

Search again for Airport KIAD:

 

..\..\..\PAI-AF2S\scenery\PAI_AF2_KIAD_DEFAULT.bgl

=============================================================================

 

Airport KIAD :N38:56:40.2997 W077:27:20.9188 313ft

Country Name="United States"

State Name="Virginia"

City Name="Washington"

Airport Name="Washington Dulles Intl"

in file: ..\..\..\PAI-AF2S\scenery\PAI_AF2_KIAD_DEFAULT.bgl

 

Runway 1L/19R centre: N38:57:17.4560 W077:27:34.3888 313ft

Start 1L: N38:56:22.3533 W077:27:35.1791 313ft Hdg: 0.6T, Length 11501ft

Computed start 1L: Lat 38.939075 Long -77.459776

Start 19R: N38:58:12.5588 W077:27:33.5988 313ft Hdg: 180.6T, Length 11501ft

Computed start 19R: Lat 38.970623 Long -77.459322

Hdg: 0.640 true (MagVar -10.200), Concrete, 11501 x 150 ft

Primary ILS ID = IOSZ

*** No matching ILS record - assume provided by another layer

Secondary ILS ID = IDLX

*** No matching ILS record - assume provided by another layer

*** Runway *** KIAD0011 Lat 38.939075 Long -77.459778 Alt 313 Hdg 11 Len 11501 Wid 150

*** Runway *** KIAD0192 Lat 38.970623 Long -77.459320 Alt 313 Hdg 191 Len 11501 Wid 150

Runway 1R/19L centre: N38:56:22.3209 W077:26:10.3694 313ft

Start 1R: N38:55:27.2181 W077:26:11.1835 313ft Hdg: 0.7T, Length 11511ft

Computed start 1R: Lat 38.923748 Long -77.436444

Start 19L: N38:57:17.4560 W077:26:09.5549 313ft Hdg: 180.7T, Length 11511ft

Computed start 19L: Lat 38.955318 Long -77.435977

Hdg: 0.660 true (MagVar -10.200), Concrete, 11511 x 150 ft

Primary ILS ID = IIAD

*** No matching ILS record - assume provided by another layer

Secondary ILS ID = ISGC

*** No matching ILS record - assume provided by another layer

*** Runway *** KIAD0012 Lat 38.923748 Long -77.436447 Alt 313 Hdg 11 Len 11511 Wid 150

*** Runway *** KIAD0191 Lat 38.955318 Long -77.435974 Alt 313 Hdg 191 Len 11511 Wid 150

Runway 12 /30 centre: N38:56:19.2758 W077:28:23.4187 313ft

Start 12 : N38:56:36.9631 W077:29:23.6526 313ft Hdg: 110.7T, Length 10489ft

Computed start 12 : Lat 38.943768 Long -77.490478

Start 30 : N38:56:01.5885 W077:27:23.1864 313ft Hdg: 290.7T, Length 10489ft

Computed start 30 : Lat 38.933605 Long -77.455872

Hdg: 110.680 true (MagVar -10.200), Concrete, 10489 x 150 ft

Primary ILS ID = IAJU

*** No matching ILS record - assume provided by another layer

*** Runway *** KIAD0120 Lat 38.943768 Long -77.490479 Alt 313 Hdg 121 Len 10489 Wid 150

*** Runway *** KIAD0300 Lat 38.933605 Long -77.455872 Alt 313 Hdg 301 Len 10489 Wid 150

 

Disregard the No ILS data in this example. It would not apply to yours.

 

For an add-on there is always a deletion section followed immediately or later by a section referring to runways and taxiways, etc. You need to insure that the last entries for Airport KIAD refer to the path for your Imagine Sim KIAD scenery installation. These last entries have priority as establishedby your FS scenery library settings listed by priority (the top of the list at number 1 is first in priority).

 

In these last sections pointing to Imagine Sim's KIAD scenery the one with the runway listings has the center runways detected. If not then they may not be in the afd (afcad type file). It may be the older AF2_ or the newer AFX_ or other type.

 

You can best examine these types of file with the free Airport Design Editor which opens both FS9 and FSX types of afd type files. Then you can do a List\Runways. Just use the file\open from .bgl and browse to that imagine sim folder and select the file with the runway data.

 

http://www.airportdesigneditor.co.uk/ and you'll see it looks like AFCAD221 and AFX runway diagrams. If you need to edit with this there are other considerations especially with an AFX type file. Just use this for examination right now.

 

So we covered the data generation procedures via RC including getting the data into its folder and how to determine the scenery priority and insuring the correct sceneery folders had priority as seen by makerwys.

 

If you install a traffic application be aware that some plasce their afd type files at higher priority then an add-on scenery. Check your FS scenery library settings.

Ronzie,

 

Thank you for the detailed trouble-shooting steps. I checked the r5.csv file and Rwy 1C was listed (0013), however in the r4.csv file in the rc4/data folder, Rwy 1C was NOT listed. I went ahead and updated Make Runways to v. 4.164 (I had version 4.163) and updated the database via RC4 (which I've done multiple times before). Rwy 1C (0013) is now listed in the r4.csv file. Looks like problem is fixed! I have no idea why it failed to update in the past. Either way, this time it worked.

 

I appreciate the timely individual support you give to all the users of RC4. I hope you and your family have a blessed New Year! Blue Skies, friend.

 

Todd