86
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
In essence, the AI controlled traffic system is comprised of three elements: | In essence, the AI controlled traffic system is comprised of three elements: | ||
# AI Aircrafts models : Are part of the base package under $DATA/AI/Aircrafts and cannot be | # AI Aircrafts models : Are part of the base package under <tt>$DATA/AI/Aircrafts</tt> and cannot be flown by end user like regular FDM models as they are dedicated and exclusive to AI systens. | ||
# AI traffic schedules : Are part of the base package under $DATA/AI/Traffic and define where and when AI aircrafts should fly | # AI traffic schedules : Are part of the base package under <tt>$DATA/AI/Traffic</tt> and define where and when AI aircrafts should fly | ||
# Groundnets : Are part of | # Groundnets : Are part of the scenery pack under <tt>[[terrasync]]/Airports</tt> and contain the information required to guide AI aircrafts on the ground from gates to runways and vice versa, at each individual airport (one per airport) | ||
| Line 15: | Line 15: | ||
* FlightGear 1.9.0 and subsequent versions : <tt>[[$FG ROOT]]/AI/Traffic/</tt> | * FlightGear 1.9.0 and subsequent versions : <tt>[[$FG ROOT]]/AI/Traffic/</tt> | ||
Traffic is organised by Operator in subfolders, | Traffic is organised by Operator in subfolders, organised by the initial of each operator's ICAO designator. For example, traffic for United Airlines is stored under <tt>[[$FG ROOT]]/AI/Traffic/U/UAL.xml</tt> | ||