|
|
下载中心
| 开发商: |
- |
| 软件大小: |
50kb |
| 兼容平台: |
P3d v1 P3d v2 其它 |
| 飞卡售价: |
1 飞卡 |
| 下载地址: |
- |
MakeRwys4.678.zip
(27.58 KB, 下载次数: 4, 售价: 1 飞卡)
下载地址:
支技FSX、FSX-SE、P3D.
大体作用：
解压到FSX根目录然后运行EXE，它会生成一个更新runways.csv，
可以解决 RAAS 喊错跑道号码的任何问题。 让你的 PRO ATC-X 正常工作； ==========================================
以下为原版英文说明：
MakeRwys.EXE Version 4.678, by Pete Dowson
==========================================
FS2000, FS2002, FS2004
----------------------
Place the EXE into your main FS folder
where the SCENERY.CFG file is located.
FSX, FSX-SE, Prepar3D
---------------------
Place the EXE into your the relevant main FS folder. For FSX Steam Edition
this will be in the Steam folder, under "steamappscommon".
MakeRunways will find the correct Scenery.CFG file automatically based on
the EXE name it finds there and its version number.
THEN
----
Double click the MakeRwys.EXE file in Explorer to run it.
The files created are derived by checking all of the BGLs in all of the Active
scenery layers with locally installed files, as defined in the SCENERY.CFG
file.
The process is different with pre-FS2004 AFD files and the new FS2004 airport
data files, though the usable databases produced are in the same format.
The files produced are:
Runways.txt
This is a text file showing the data analysed by the program in
readable format. Use this to check on things when something odd seems
to happen. you can find conflicting or overriding sceneries and so on
this way. However, be warned. The file will typically grow to over 10
megabytes. You need to view it with a text editor capable of dealing
easily with large files.
You can delete this file afterwards. It is only for your viewing,
nothing else.
Runways.xml
An XML file providing a database of airports and their runways.
FStarRC.rws
This is a binary runways database used by my FStarRC program.
Airports.fsm
This is a binary airports database used by FS_Meteo, at present after
re-naming to "Runways.rws".
Runways.csv
This is a comma-separated text database of all the runways, sorted,
and it is in the particular format used by Radar Contact (all versions
up until the change to the following:
R4.csv
This is the same as the previous CSV file, but includes additional
runway data added at the end of each line. This is used
in Radar Contact 4 (before RC4.3) for more precise ATC operations.
R5.csv
This is the same as R4.csv but with runway closure indicators in an
extra two fields - CL closed for landing and/or CT closed for
take-off. This file is used by RCV4.3 and RC5.
G5.csv
This contains information about Gates, Ramps, Parking places, along
with airline lists where specified. It is used by later versions of
Radar contact.
T5.csv
This contains details of all taxi paths.It is used by later versions of
Radar contact.
F5.csv
This lists all COM frequencies and associated names, including the
airport name, for Radar Contact 5 or later.
F4.csv
This lists all COM frequencies and associated names, including the
airport name, for Radar Contact 4. If you want to use this with RC4
you must copy it to the Radar Contact 'data' subfolder. Make a safe
copy of your original F4.CSV file first (I usually just rename it
to "f4orig.csv").
Note that MakeRwys matches frequences as best it can, with the
following extra "fiddles" to ensure a good range of frequencies:
1. Clearance Delivery is preferably met by FS type 14 "CD", but else is
met by type 7 "CLEARANCE".
2. Multicom is met by FS type 2 "MULTICOM", but failing that by type 4
"CTAF".
3. Approach is from FS type 8 "APPROACH", but failing that from a
second Type 9 "DEPARTURE" if there are more than one of the latter.
4. Deparature is from FS type 9 "DEPARTURE", but failing that from a
second Type 8 "ARRIVAL" if there are more than one of the latter.
Centre, FSS, AWOS and ASOS frequencies aren't used for this file.
=========================================================
MINIMUM RUNWAY LENGTH
By default MakeRunways imposes a minimum runway legth of 1500 feet,
otherwise runwaysc are omitted from the data files. This is to
eliminate so-called "ghost" runways being included -- very small
runways provided only to allow AI Traffic to be directed better for
landings and takeoffs.
If necessary you can override this value. Just use a command line
parameter in the form:
/>n
where n gives the nmuber of feet to be considered the miaximum for
exclusion. Take care not to make this too small for fear of
including those "ghosts", but if you really do want to see all,
you can set />0.
=========================================================
UPDATING RADAR CONTACT's TRANSITION ALTITUDES FILE
If you are a user of Aivlasoft's EFB program for FSX/P3D, then part of
the updated data you will have is a file with the correct Transition
Altitudes for most airports in the world. MakeRunways can now
automatically use that file to update Radar Contact's list too.
In order to do this, you must copy RC's "M4.CSV" file into the root
FS folder, next to MakeRunways. Don't worry about EFB -- if that is
correctly installed then MakeRunways will find it.
To tell MakeRunways to update M4.CSV add a command line parameter:
/+T
(T for Transition Altitude).
When MakeRunways has finished simply copy the M4.CSV file back into
RC's Data folder.
=========================================================
GATES FOR AIRLINE FILE
There is also an optional file, listing all the Gates for a specifically
selected airline. To obtain this for your preferred airline, run
MakeRwys.rexe with a command line parameter such as (e.g.)
/BAW
for the airline code BAW (British Airways).
If you are also using the />n and/or /+T parameters, those must come first.
The gates are listed in sorted order of Airport, but not of Gate name or
number -- the Gates are in their scenery file order. The file produced will
be an ordinary text file named Gates.txt. e.g.
BAW Gates.txt
in the above case.
=================
After running the program to completion, just copy the files to their
respective program's folders.
Have fun!
=========================================================
VALUES PROVIDED IN EACH CSV FILE:
=========================================================
RUNWAYS.CSV (ORIGINAL RUNWAYS FILE -- for very old versions of RC):
ICAO, Rwy*, Latitude*, Longitude*, Altitude*, HeadingMag, Length*, ILSfreq*
R4.CSV (RUNWAYS FILE for RCV4, until 4.3):
ICAO, Rwy*, Latitude*, Longitude*, Altitude*, HeadingMag, Length*, ILSfreq*, Width*, MagVar, CentreLatitude, CentreLongitude, ThresholdOffset*
R5.CSV (RUNWAYS FILE for RCV5):
ICAO, Rwy*, Latitude*, Longitude*, Altitude*, HeadingMag, Length*, ILSfreqFlags*, Width*, MagVar, CentreLatitude, CentreLongitude, ThresholdOffset*,Status*
RUNWAYS.XML (Airports and runways for "It's Your Plane")
For each Airport: ICAO id, ICAOName, City, Longitude, Latitude, Altitude (feet), MagVar
For each Airport: ICAO id, ICAOName, City, Longitude, Latitude, Altitude (feet), MagVar
And, within each Airport section, for each runway:
Runway id, Len (feet), Hdg (Magnetic: add MagVar for True), Def (surface), ILSFreq (nnn.nn), ILSHdg (Mag),
ILSid, ILSslope, Lat and Lon of threshold/start, Lat and Lon of FS's "Startt" point (which may be to the
side of the runway), ClosedLanding (TRUE or FALSE) and ClosedTakeoff (TRUE or FALSE), EndLights (NONE, LOW, MEDIUM or HIGH),
CenterLights (NONE, LOW, MEDIUM or HIGH), CenterRed (TRUE or FALSE).
G5.CSV (GATES for RCV5):
ICAO, GateName*, GateNumber, Latitude, Longitude, Radius*, HeadingTrue, GateType*, AirlineCodeList ...
F5.CSV (COMMS FREQUENCIES for RCV5)
ICAO, CommsType*, Frequency, "name of facility"
(with an entry for Airport Name with CommsType=0 and Frequency=0)
F4.CSV (COMMS FREQUENCIES for RCV4)
ICAO, Airport Name, ATISfreq, CDfreq, GroundFreq, TowerFreq, UnicomFreq, MulticomFreq, ApproachFreq, DepartureFreq
T5.CSV (TAXIWAYS for RCV5):
ICAO,TaxiwayName,MinimumWidthMetres,PointList ...
--------------------------------------------------------------------------------
where PointList is a sequence of: Latitude,Longitude,TaxiType*,WidthMetres
* 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
* Latitude is of threshold or AFCAD's "runway start"
* Longitude is of threshold or AFCAD's "runway start"
* Altitude in feet
* Length in feet
* ILSFreq as nnnnn for nnn.nn, or just 0 when no ILS
* ILSFreqFlags is ILSFreq then optional B (backcourse), D (DME) G (Glideslope) equipped
* Width in feet
* ThresholdOffset in feet
* Status: ,CT for Closed for Takeoff and/or ,CL for Closed for Landing
* Radius in metres
* TaxiType is
0 = unknown
1 = Normal
2 = Hold short
3 = unknown
4 = ILS hold short
5 = Gate/Park
* GateName is either omitted or one of
Dock
Park
PkN
PkNE
PkE
PkSE
PkS
PkSW
PkW
PkNW
* GateType is:
0 = none
1 = Ramp GA
2 = Ramp GA Small
3 = Ramp GA Medium
4 = Ramp GA Large
5 = Ramp Cargo
6 = Ramp Military Cargo
7 = Ramp Military Combat
8 = Gate Small
9 = Gate Medium
10 = Gate Large
11 = Dock GA
* CommsType is:
0 = Special entry with airport name, zero frequency
1 = ATIS
2 = MULTICOM
3 = UNICOM
4 = CTAF
5 = GROUND
6 = TOWER
7 = CLEARANCE
8 = APPROACH
9 = DEPARTURE
10 = CENTRE
11 = FSS
12 = AWOS
13 = ASOS
14 = CLEARANCE PRE-TAXI
15 = REMOTE CLEARANCE DELIVERY
=========================================================
Pete Dowson, 20th December 2014
=========================================================
|
|
发表于 2015-12-18 15:24:52
收藏