I have tried unsuccessfully to make FSX and RC4 depict the actual real world runways and I cannot seem to figure out what I am doing wrong.

 

I ran the MakeRwys.exe V 4.674 with Admin rights after placing it in my C:\FSX folder.

 

The new r4 and r5.csv files were created with new date time stamps.

 

This is the data for r5.csv for Tampa

 

KTPA 11 27.9633 -82.5423 26 3.73 11032 108.90BG 150 -2 27.97843 -82.5418 0 KTPA 12 27.96431 -82.529 26 3.73 8323 111.95BD 150 -2 27.97572 -82.5286 0 KTPA 100 27.97083 -82.5361 26 93.73 6992 0 150 -2 27.97054 -82.5252 0 KTPA 191 27.98713 -82.5282 26 183.73 8323 110.30BG 150 -2 27.97572 -82.5286 0 KTPA 192 27.99355 -82.5413 26 183.73 11032 108.50BDG 150 -2 27.97843 -82.5418 0 KTPA 280 27.97025 -82.5144 26 273.73 6992 0 150 -2 27.97054 -82.5252 0

 

RC4.3 is still showing 18/36 runways for KTPA when the current runways are 01/19.

 

KJAX is another airport that has RWY 7 when RWY 8 is the new runway.

 

I also rebuilt the DB in RC4.3

 

Any help would be appreciated.

 

Thanks

Don

Have you checked the runway files that RC4 has to make sure they are the updated ones? I believe when you create a new DB through RC4 it takes those r5 and r4 and puts it in an RC4 folder or something like that.

The format of r5.csv you posted is incorrect. You are misssing leading zeros. Here is what my installed KTPA r5.csv rows look like:

 

KTPA,0090,27.970001,-82.535698,26,95.550,6710,0,150,-3.500,27.969671,-82.525284,0,,CL
KTPA,0181,27.987934,-82.526443,26,185.550,8650,110.30BG,150,-3.500,27.976078,-82.526924,0,,
KTPA,0182,27.993090,-82.541611,26,185.550,10600,108.50BDG,150,-3.500,27.978561,-82.542198,0,,
KTPA,0270,27.969341,-82.514870,26,275.550,6710,0,150,-3.500,27.969671,-82.525284,0,,
KTPA,0361,27.964033,-82.542786,26,5.550,10600,108.90BG,150,-3.500,27.978561,-82.542198,0,,
KTPA,0362,27.964222,-82.527405,26,5.550,8650,111.95BD,150,-3.500,27.976078,-82.526924,0,,
 

Note the four number characters in the  field following the ICAO.

 

In your FS9 folder you'll find a document called MakeRwys Read Me text that explains how to read this information. You must use a text editor such as wordpad or notepad. Do not use a database or spreadsheet app.

 

r5.csv from your FS folder is copied as r4.csv to its data folder. Here is the field definitions for r5.csv:

 

R5.CSV (RUNWAYS FILE for RCV5):

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

 

Rwy is nnn for runway number, then 0, 1=L, 2=R, 3=C, 4=W (water)
  Note that runways designated N, NE, etc are denoted by runway
  numbers over 36, as follows:
    37 =  N-S
    38 =  E-W
    39 =  NW-SE
    40 =  SW-NE
    41 =  S-N
    42 =  W-E
    43 =  SE-NW
    44 =  NE-SW
    45 =  N
    46 =  W
    47 =  NW
    48 =  SW
    49 =  S
    50 =  E
    51 =  SE
    52 =  NE

 

The first three characters are used for the runway number. The fourth translates to nothing, left, right, or center, or water.

 

The runway data is pulled from your installed scenery using the highest priority file with "afd" data either default, AF2_, AFX, or with ADE but not limited to those labels. The FS scenery.cfg is used to guide makerwys.exe.

 

So for my version of KTPA we have for runways:

 

KTPA,0090, -- 09
KTPA,0181, -- 18L
KTPA,0182, -- 18R
KTPA,0270, -- 27
KTPA,0361, -- 36L
KTPA,0362, -- 36R

 

Due to annual changes in magnetic deviation, or resigns in runway layout, runway numbering can change and this may be reflected in add-on scenery files including just afd types. Whichever has priority is the data RC will get.

 

This current chart:

http://flightaware.com/resources/airport/TPA/APD/AIRPORT+DIAGRAM/pdf

 

shows runways as 1L/19R, 1R/19L, 10/28

 

With a magnetic deviation of 0.1 degrees west annually and a 2010 deviation of 4.8 W, the default data from around 2003 would have one number less after rounding to the nearest 10 degree boundary.

 

(Magnetic deviation is added or subtracted depending on direction of variation to the true heading in degrees of a runway and then the result is rounded to the nearest ten degrees with the last number not used.)

 

The true heading of the two 19s according to that chart is 186.5.

 

My add-on KTPA from the US Airport collection from Aerosoft and designed by Fly Tampa shows a magnetic deviation of 3.5 for the airport. This afd file was created in January, 2004. So for the current chart an increase of 1.3 degrees westerly to give 4.8W would be enough to push the true heading of the runways over the ten degree boundary.  In the mag-var field of r5.csv -3.5 is also shown. RC may use this to calculate the runway true heading.

 

The runway list (exported from Airport Design Editor) for this 2004 add-on scenery shows:

 

ID, Heading, Length Feet, Width Feet, Surface, XWind, Comments
18R/36L,182.1,10600.0,150.0,Concrete,False,
18L/36R,182.1,8650.0,150.0,Asphalt,False,
09/27,092.1,6710.0,150.0,Asphalt,False,

 

I also have a chart with 2002 data for KTPA which shows a true heading of 184.8 for the 18s at that time. The mag deviation is stated at 3.1W in 1995.
 

So when you state the wrong runways are shown, what are you using for reference? Where you are using AIRAC updated data for flight planners or nav instruments, they may be more modern than your latest add-on scenery for said airport and you have a discrepancy.