Rather than retype everything the information below is copied from another thread on how to check the RC data was properly gathered and what runways.txt (a log of operations created by makerwys.exe when run by RC.:

 

-----------------------

First we will insure that the data files between FS and RC transferred Ok. In your FS folder look for r5.csv. Get the date-time of modification and size by right clicking on it. Now go to your rcv4\data folder and right click of r4.csv (a copy of r5.csv) whicjh should almost have the same date-time stamp and be the same size. If that is OK then go back to your FS folder and use word or wordpad to open runways.txt, a huge log file.

 

Search for your airport of interest such as "Airport KMCO" (without quotes). The first encounter will be the default KMCO and you'll see a path in the head of that section to the default folder and file used for the data. The file name will start with AP followed by a few numbers.

 

For each scenery add-on (including afcad types) there will be two sections to the same path, not necessarily together. We'll cal this a section pair. The first section regards deletions and the second has runway data and other information. If you have an add-on for KMCO continue to search for Airport KMCO. The last section pair you find in runways.txt has priority (as established by your library setup recorded in scenery.cfg) has priority and that furnishes the data to RC in r5.csv.

 

See if that last entry section pair points correctly to any add-on scenery. Again, make sure your makerwys.exe is current and you provided a correct path to your FS folder.

 

---------------------------------

 

Now go into your FS folder and open runways.txt in word or wordpad, not notepad, as it is a huge text file. Search for a problem California airport using its ICAO code instead of KMCO in the example below. Continue the search checking each hit as described until you get no more. The last section pair of deletions and additions has priority in the data going to RC.

 

-----------------------------------

Here is what needs to be checked that I've highlighted. This is for the default KMCO:

 

Airport KMCO :N28:25:43.9930 W081:18:57.6998 96ft

Country Name="United States"

State Name="Florida"

City Name="Orlando"

Airport Name="Orlando Intl"

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

 

Runway 18L/36R centre: N28:25:54.5535 W081:19:19.6701 96ft

Start 18L: N28:26:52.2478 W081:19:20.2865 96ft Hdg: 179.5T, Length 12037ft

Computed start 18L: Lat 28.448328 Long -81.322305

Start 36R: N28:24:56.8592 W081:19:19.0521 96ft Hdg: 359.5T, Length 12037ft

Computed start 36R: Lat 28.415312 Long -81.321951

Hdg: 179.460 true (MagVar -4.500), Asphalt, 12037 x 200 ft

Secondary ILS ID = IOJP

Secondary ILS: IOJP 110.70 Hdg: 359.5 , Flags: GS BC "CAT III ILS 36R"

*** Runway *** KMCO0181 Lat 28.448328 Long -81.322304 Alt 96 Hdg 184 Len 12037 Wid 200

*** Runway *** KMCO0362 Lat 28.415312 Long -81.321953 Alt 96 Hdg 4 Len 12037 Wid 200 ILS 110.70, Flags: GS BC

Runway 18R/36L centre: N28:25:54.4239 W081:19:36.4699 96ft

Start 18R: N28:26:52.1183 W081:19:37.0879 96ft Hdg: 179.5T, Length 12037ft

Computed start 18R: Lat 28.448292 Long -81.326974

Start 36L: N28:24:56.6973 W081:19:35.8519 96ft Hdg: 359.5T, Length 12037ft

Computed start 36L: Lat 28.415276 Long -81.326621

Hdg: 179.460 true (MagVar -4.500), Concrete, 12037 x 200 ft

Primary ILS ID = ITFE

Primary ILS: ITFE 111.90 Hdg: 179.5 , Flags: GS BC "ILS 18R"

*** Runway *** KMCO0182 Lat 28.448292 Long -81.326973 Alt 96 Hdg 184 Len 12037 Wid 200 ILS 111.90, Flags: GS BC

*** Runway *** KMCO0361 Lat 28.415276 Long -81.326622 Alt 96 Hdg 4 Len 12037 Wid 200

Runway 17 /35 centre: N28:25:18.6930 W081:17:44.6492 96ft

Start 17 : N28:26:06.4746 W081:17:45.1498 96ft Hdg: 179.5T, Length 10026ft

Computed start 17 : Lat 28.435610 Long -81.295883

Start 35 : N28:24:30.8790 W081:17:44.1486 96ft Hdg: 359.5T, Length 10026ft

Computed start 35 : Lat 28.408110 Long -81.295594

Hdg: 179.470 true (MagVar -4.500), Concrete, 10026 x 150 ft

Primary ILS ID = IDIZ

Primary ILS: IDIZ 111.75 Hdg: 179.5 , Flags: GS DME BC "CAT II ILS/DME 17"

Secondary ILS ID = IDDO

Secondary ILS: IDDO 110.50 Hdg: 359.5 , Flags: GS DME BC "CAT III ILS/DME 35"

*** Runway *** KMCO0170 Lat 28.435610 Long -81.295883 Alt 96 Hdg 184 Len 10026 Wid 150 ILS 111.75, Flags: GS DME BC

*** Runway *** KMCO0350 Lat 28.408110 Long -81.295593 Alt 96 Hdg 4 Len 10026 Wid 150 ILS 110.50, Flags: GS DME BC

 

 

--end extract--

 

For a traffic package afcad add-on first a deletions section:

..\..\..\PAI-AF2S\scenery\PAI_AF2_KMCO_DEFAULT.bgl

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

Deletions check for Airport KMCO:

Delete all taxiways!

 

 

Delete all runways and starts!

 

*** DelBth *** KMCO0170 Lat 28.435610 Long -81.295883 Alt 96 Hdg 184 Len 10026 Wid 150 ILS 111.75, Flags: GS DME BC

 

*** DelBth *** KMCO0181 Lat 28.448328 Long -81.322304 Alt 96 Hdg 184 Len 12037 Wid 200

 

*** DelBth *** KMCO0182 Lat 28.448292 Long -81.326973 Alt 96 Hdg 184 Len 12037 Wid 200 ILS 111.90, Flags: GS BC

 

*** DelBth *** KMCO0350 Lat 28.408110 Long -81.295593 Alt 96 Hdg 4 Len 10026 Wid 150 ILS 110.50, Flags: GS DME BC

 

*** DelBth *** KMCO0361 Lat 28.415276 Long -81.326622 Alt 96 Hdg 4 Len 12037 Wid 200

 

*** DelBth *** KMCO0362 Lat 28.415312 Long -81.321953 Alt 96 Hdg 4 Len 12037 Wid 200 ILS 110.70, Flags: GS BC

 

 

Delete all taxiways!

 

 

COM: Delete all frequencies!

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

 

and then the runway data (plus other stuff) later on:

 

..\..\..\PAI-AF2S\scenery\PAI_AF2_KMCO_DEFAULT.bgl

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

 

Airport KMCO :N28:25:43.9930 W081:18:57.6998 96ft

Country Name="United States"

State Name="Florida"

City Name="Orlando"

Airport Name="Orlando Intl"

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

 

Runway 18L/36R centre: N28:25:54.5535 W081:19:19.6701 96ft

Start 18L: N28:26:52.2478 W081:19:20.2865 96ft Hdg: 179.5T, Length 12037ft

Computed start 18L: Lat 28.448328 Long -81.322305

Start 36R: N28:24:56.8592 W081:19:19.0521 96ft Hdg: 359.5T, Length 12037ft

Computed start 36R: Lat 28.415312 Long -81.321951

Hdg: 179.460 true (MagVar -4.500), Asphalt, 12037 x 200 ft

Secondary ILS ID = IOJP

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

*** Runway *** KMCO0181 Lat 28.448328 Long -81.322304 Alt 96 Hdg 184 Len 12037 Wid 200

*** Runway *** KMCO0362 Lat 28.415312 Long -81.321953 Alt 96 Hdg 4 Len 12037 Wid 200

Runway 18R/36L centre: N28:25:54.4239 W081:19:36.4699 96ft

Start 18R: N28:26:52.1183 W081:19:37.0879 96ft Hdg: 179.5T, Length 12037ft

Computed start 18R: Lat 28.448292 Long -81.326974

Start 36L: N28:24:56.6973 W081:19:35.8519 96ft Hdg: 359.5T, Length 12037ft

Computed start 36L: Lat 28.415276 Long -81.326621

Hdg: 179.460 true (MagVar -4.500), Concrete, 12037 x 200 ft

Primary ILS ID = ITFE

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

*** Runway *** KMCO0182 Lat 28.448292 Long -81.326973 Alt 96 Hdg 184 Len 12037 Wid 200

*** Runway *** KMCO0361 Lat 28.415276 Long -81.326622 Alt 96 Hdg 4 Len 12037 Wid 200

Runway 17 /35 centre: N28:25:18.6930 W081:17:44.6492 96ft

Start 17 : N28:26:06.4746 W081:17:45.1498 96ft Hdg: 179.5T, Length 10026ft

Computed start 17 : Lat 28.435610 Long -81.295883

Start 35 : N28:24:30.8790 W081:17:44.1486 96ft Hdg: 359.5T, Length 10026ft

Computed start 35 : Lat 28.408110 Long -81.295594

Hdg: 179.470 true (MagVar -4.500), Concrete, 10026 x 150 ft

Primary ILS ID = IDIZ

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

Secondary ILS ID = IDDO

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

*** Runway *** KMCO0170 Lat 28.435610 Long -81.295883 Alt 96 Hdg 184 Len 10026 Wid 150

*** Runway *** KMCO0350 Lat 28.408110 Long -81.295593 Alt 96 Hdg 4 Len 10026 Wid 150

 

------end extract------------

 

Note that the path to the add-on scenery both sections is the same. In your system, does this path-filename point to your KMCO add-on? It gets this info from your scenery.cfg as managed by your FS library setup. The last pair of sections (deletions followed by the additions) gets priority in creating the runway file r5.csv.

 

Now I did not quite understand your last post. It looked like an unfinished file too long for notepad. You need word or wordpad.

 

Are you sure you updated to makerwys version 4612 and then ran the scenery rebuild?

fsuipc.simflight.com/beta/MakeRunways_4612.zip is the direct link to today's version.

 

To see if the data copied go into your fs folder and find r5.csv, right click, and get the date-time modified and the size. Then get the same properties for r4.csv in your RCv4\data folder. The time should be close and the size the same.

 

------------------------------

 

Be sure the departure airport in your flight plan sent to RC matches the departure airport where you parked your aircraft in FS. If using FSBuild remember the steps are (optional auto generate), then set up the export chioices, and then build to export and place the plan file into the correct folder to load into RC.

I rebuilt the scenery files in RC again this morning and for the first time the program seems to be running correctly---now my only test flight problem seems to be the fact that the Command autopilot in the PMDG 737NGX--700 series will not engage untill I pass about 10 thousand feet---but of course this is a whole new issue for a different forum

 

Cheers

 

Dorn