SCASM 2.50/2.91 |
Instructions for the new Airport Facility Directory format |
|
The new Facility Directory format (FS98) is stored in BGL files with an extended fileheader. It is not recomended to mix these commands (section 20) with others in one source file.
The facility entries are stored in so called object containers wich carry all data for one facility directory entry. Please follow exactly the recomended sequence of instructions since SCASM does not check this.
In FS98 this data is only used for the "Goto Airport" menu and for pilot information. In FS2002 these data are also used by the artificial intelligence aircrafts (AI aircrafts).
It is strongly recommend to compile the new facility data as a single BGL file since everytime a new facility data file is found by FS the database index is generated again. This dramatically slows down the new scenery testing.
The installation of AFD BGL files to FS98 is a little tricky.
If you want to see your data in the "Airport Facility Directory" menu you have to use one of the already existing region names from the map.
If you want to add an AFD file to an already existing scenery directory you have to deactivate this scenery in the scenery library. After this update your scenery directory with the AFD file and then activate the scenery again. It seems this procedure is only needed if you add an AFD file to an scenery directory the first time.
If you do not follow these procedure it sometimes happen that not all files are updated corectly.
For FS2002 it is recommended to use the new *AFD.BGL file as an input file for AFDLink.exe to update existing *AFD files. Please see the documentation of AFDLink.exe for more information.
To have a look ito AFD-BGL's please use my AFDTree program. This program will give you an idea about the data structure in these files.
In FS2K and later there are new data containers. It seems that these containers carry airway and airspace data. These data are currently not suported by SCASM and AFDTree. These data are not listed in the NameList and therefore are invisible for AFDTree.
TOP |
FS98 - FS2002 |
Container( type ref# ) |
A typical instruction sequence for an airport container:
|
TOP |
FS98 - FS2002 |
EndC |
This command indicates the end of an object container. |
TOP |
FS98 - FS2002 |
APLocation( Lat Lon elev ) |
This is the reference point of the airport. |
TOP |
FS98 - FS2000 |
ICAO_ID( id ) |
|
TOP |
FS98 - FS2000 (FS2002) |
RwyLoc( Lat Lon elev hdg magvar len wid type number surface ) |
There is only one entry for both runway directions. Heading and ID should be chosen for the lowest number. |
TOP |
2.85 - FS2002 |
|
This instruction uses 2 aditional parameters. This format is enabled for
FS2002 with
There is only one entry for both runway directions. Heading and ID should be chosen for the lowest number. |
TOP |
FS98 - FS2002 |
Frequency( frq type ["text"] ) |
If more than one frequency is specified for an airport, FS98 displays only the first one! |
TOP |
FS98 - FS2002 |
Navaid( Lat Lon elev hdg frq type class flags ID "name" ) |
Several of this instructions with different types are used to assemble a complete NAVAID. To build an ILS system you need at least the LOC type. For an complete ILS specify LOC, SLOPE and DME always in this sequence. Usually the ILS localiser is positioned behind the runway it belongs to and its heading should be perfectly aligned with the runway. The glide slope antenna is positioned besides the runway near the touch down markings. |
TOP |
FS98 - FS2002 |
SetupLoc( Lat Lon elev hdg type stype num ) |
This data record is used by FS to set the start position from the menu. |
TOP |
2.85 | FS2000 - FS2002 |
Tower( Lat Lon elev hdg ) |
|
TOP |
2.85 | FS2002 |
AI_DataStart |
This command marks the begin of the data section for AI aircraft information. This section MUST be terminated by an AI_DataEnd instruction. Also it must be followed by the instructions: TaxiwayPoints(), Positions(), TaxiwayPath() and TaxiwayNames() in exactly this order. In the moment we only know the instructions but not the exact rules how to use them. |
TOP |
2.85 | FS2002 |
AI_DataEnd |
Marks the end of AI aircraft data. |
TOP |
2.85 | FS2002 |
TaxiwayPoints( f x y ... f x y ) |
|
TOP |
2.85 | FS2002 |
Positions( x y size hdg type ... ) |
|
TOP |
2.85 | FS2002 |
TaxiwayPath( type width weight p1 p2 flags factor name .. ) |
|
TOP |
2.85 | FS2002 |
TaxiwayNames( "string0" ... "string n" ) |
|
TOP |
2.85 | FS2002 |
AI_Border( top_lat bottom_lat right_lon left_lon ) |
asumed to be used by AI traffic This command can be placed anywhere in your source file. But it should be only used once per file and therefore it is a good idea to insert it somewhere to the beginning. |
TOP |
FS98 - FS2002 |
NameList( lang ) |
The NameList() instruction is mandatory for this type of BGL files. It contains the NameEntry()'s for the World..goto..airport menu. A NameList must be closed by an EndNL command. |
TOP |
FS98 - FS2002 |
NameEntry( type ref# text ) |
|
TOP |
FS98 - FS2002 |
EndNL |
This marks the end of an NameList |
TOP |
Header( ... ) Container( APT 1 ) ; list of airport containers ... EndC ; more airport containers may follow ; Container( VOR ?? ) ; list of VOR containers ... EndC ; more VOR containers may follow ; Container( NDB ?? ) ; list of NDB containers ... EndC ; more NDB containers may follow ; ; end of container list NameList( 409 ) ; US english NameEntry( REGION 0 "EUROPE" ) NameEntry( CITY 0 TestCity ) NameEntry( AIRPORT 1 "Test airport" ) ; references the 1st container EndNL
TOP | © 1995-2002 Manfred Moldenhauer |