117
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
→Defining the aircraft
| Line 132: | Line 132: | ||
<?xml version="1.0"?> | <?xml version="1.0"?> | ||
<trafficlist> | <trafficlist> | ||
<aircraft> | |||
<model>Aircraft/MD11/Models/KLMmd11.xml</model> | |||
<livery>KLM</livery> | |||
<airline>KLM</airline> | |||
<home-port>EHAM</home-port> | |||
<required-aircraft>MD11KLM</required-aircraft> | |||
<actype>MD11/P</actype> | |||
<offset>25</offset> | |||
<radius>39</radius> | |||
<flighttype>gate</flighttype> | |||
<performance-class>jet_transport</performance-class> | |||
<registration>PH-KCA</registration> | |||
<heavy>true</heavy> | |||
</aircraft> | |||
<aircraft> | <aircraft> | ||
... | |||
</aircraft> | </aircraft> | ||
</trafficlist> | </trafficlist> | ||
The first lines inside the '''<aircraft>''' | The first lines inside the '''<aircraft>''' definition specify some of the aircraft's performance characteristics. | ||
* '''<model>''' Here is a path specified to the 3D model that should be used in FlightGear. | * '''<model>''' Here is a path specified to the 3D model that should be used in FlightGear. | ||
* '''<livery>''' This line is currently unused, and will likely remain unused. The original idea was to combine this with the '''<model>''' line (see above) to load a specific combination of aircraftype and paint scheme, but I abandoned that idea, because it didn't turn out to be very combatible with the existing FlightGear model loading code. | * '''<livery>''' This line is currently unused, and will likely remain unused. The original idea was to combine this with the '''<model>''' line (see above) to load a specific combination of aircraftype and paint scheme, but I abandoned that idea, because it didn't turn out to be very combatible with the existing FlightGear model loading code. | ||
* '''<airline>''' This line refers to the airline operating the aircraft. This information is currently used by FlightGear to handle gate/parking assignments. Use the official 3-letter [[ICAO]] airline code here, in case of commercial traffic. This keyword is unlikely to be used for general aviation and military traffic. | * '''<airline>''' This line refers to the airline operating the aircraft. This information is currently used by FlightGear to handle gate/parking assignments. Use the official 3-letter [[ICAO]] airline code here, in case of commercial traffic. This keyword is unlikely to be used for general aviation and military traffic. | ||
* '''<home-port>''' Each FlightGear aircraft is assigned to a home airport. Internally, this is used to ensure that routes are setup that will eventually lead back to the home airport. This is done to maintain some sensibility into the routing algorithm. '''[New for traffic manager II]''' | |||
* '''<required-aircraft>''' This value is a key that binds aircraft and flights together. In case of this example, the key MD11KLM. Indicates that this aircraft will only carry out flights containing the same key. Usually, a combination of aircraft type, and airline will suffice for this key. In some cases, in particular, when specific aircraft / airlines are distributed across multiple hubs (i.e. home ports), it may be necessary to specify a key containing the home airport as well. For example, Delta Airlines operates 767's out of Atlanta, as well as out of New York. To separate between these two cases, it would be advisable to use two keys; one for KATL (e.g. 767DALKATL), and one for KJFK (e.g., 767DALKJFK). '''[NEW for traffic manager II]''' | |||
* '''<actype>''' A description of the aircraft type reserved for future use in [[ATC]]. | * '''<actype>''' A description of the aircraft type reserved for future use in [[ATC]]. | ||
* '''<offset>''' Ground offset of the 3D model. Not all aircraft 3D models are build using the same convention. Use this parameter to align the wheels with the ground. Notice that this parameter will probably become obsolete in the near future, because model view point references can also be done in the xml file that the '''<model>''' keyword refers to. | * '''<offset>''' Ground offset of the 3D model. Not all aircraft 3D models are build using the same convention. Use this parameter to align the wheels with the ground. Notice that this parameter will probably become obsolete in the near future, because model view point references can also be done in the xml file that the '''<model>''' keyword refers to. | ||
| Line 170: | Line 174: | ||
** '''ufo''' (allows extreme accel/decel capabilities). | ** '''ufo''' (allows extreme accel/decel capabilities). | ||
*'''<registration>''' The aircraft's tail number. Future versions of FlightGear will use this registration in ATC for general aviation traffic. For commercial traffic the registration number will likely remain unused. | *'''<registration>''' The aircraft's tail number. Future versions of FlightGear will use this registration in ATC for general aviation traffic. For commercial traffic the registration number will likely remain unused. | ||
*'''<heavy>''' Can be true or false. Reserved for future use by ATC, to determine whether the postfix "Heavy" should be appended to the aircraft's callsign. | |||
== Defining a flight == | == Defining a flight == | ||