186
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
→Defining a flight: nowikified <time> tag in departure, fix arrival port as a tag, added nowikified <time> tag to arrival
Portreekid (talk | contribs) (Clarified cruise-alt) |
(→Defining a flight: nowikified <time> tag in departure, fix arrival port as a tag, added nowikified <time> tag to arrival) |
||
| Line 218: | Line 218: | ||
* '''<required-aircraft>''' The key that links this flight to a particular aircraft. The see explanation in the ''aircraft'' section. | * '''<required-aircraft>''' The key that links this flight to a particular aircraft. The see explanation in the ''aircraft'' section. | ||
* '''<fltrules>''' Can be ''IFR'' or ''VFR''. This is required for use in ATC, but currently not used. This is likely to change, however. | * '''<fltrules>''' Can be ''IFR'' or ''VFR''. This is required for use in ATC, but currently not used. This is likely to change, however. | ||
* '''<departure>''' Definition of the departure airport. This section should contain the '''<port>''' and '''<time>''' keywords. | * '''<departure>''' Definition of the departure airport. This section should contain the '''<port>''' and '''<nowiki><time></nowiki>''' keywords. | ||
* '''<cruise-alt>''' Cruising altitude for this flight. This is a bit of a simplification from the real world, where aircraft usually don't stay at the same cruise altitude throughout the flight. This behavior will probably also change in future versions. Values are in [https://en.wikipedia.org/wiki/Flight_level flightlevels] | * '''<cruise-alt>''' Cruising altitude for this flight. This is a bit of a simplification from the real world, where aircraft usually don't stay at the same cruise altitude throughout the flight. This behavior will probably also change in future versions. Values are in [https://en.wikipedia.org/wiki/Flight_level flightlevels] | ||
* '''<arrival>''' Same as '''<departure>''', but now defining the port of arrival. | * '''<arrival>''' Same as '''<departure>''', but now defining the '''<port>''' and '''<nowiki><time></nowiki>''' of arrival. | ||
* '''<repeat>''' Repeat period. This can be either the keyword ''WEEK'', or a number followed by ''Hr''. ''WEEK'' means that the whole schedule repeats itself on a weekly basis. ''Hr'' means that the whole schedule repeats after the number of hours specified directly before it (e.g. ''24Hr'' means that the schedule repeats after 24 hours). With Traffic Manager II, it is generally recommended not to mix schedules that rotate on different frequencies. In general, the best results are obtained when using only weekly rotating flights. For flights that are in reality operated on a daily basis, it is recommended to just specify multiple entries, i.e. one separate flight for every weekday. | * '''<repeat>''' Repeat period. This can be either the keyword ''WEEK'', or a number followed by ''Hr''. ''WEEK'' means that the whole schedule repeats itself on a weekly basis. ''Hr'' means that the whole schedule repeats after the number of hours specified directly before it (e.g. ''24Hr'' means that the schedule repeats after 24 hours). With Traffic Manager II, it is generally recommended not to mix schedules that rotate on different frequencies. In general, the best results are obtained when using only weekly rotating flights. For flights that are in reality operated on a daily basis, it is recommended to just specify multiple entries, i.e. one separate flight for every weekday. | ||
* '''<port>''' This should be the international ICAO airport code. This keyword should be specified only within the '''<departure>''' or '''<arrival>''' sections. As far as I know, here it should still be in upper case, although the FlightGear command line currently also supports lower case ICAO codes. | * '''<port>''' This should be the international ICAO airport code. This keyword should be specified only within the '''<departure>''' or '''<arrival>''' sections. As far as I know, here it should still be in upper case, although the FlightGear command line currently also supports lower case ICAO codes. | ||