117
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
Add a note about pending SID/STAR support
(A note about a taxidraw bugfix.) |
(Add a note about pending SID/STAR support) |
||
| Line 3: | Line 3: | ||
In essence, setting-up the AI controlled traffic system involves three steps: | In essence, setting-up the AI controlled traffic system involves three steps: | ||
# Create Traffic files, | # Create Traffic files, | ||
# Build ground networks for the Airports containing traffic. | # Build ground networks for the Airports containing traffic. | ||
# Create the appropriate Departure / Arrival procedures for each airport involved. | |||
Notice that the "Download all AI aircraft" is no longer necessary, because most, if not all, AI aircraft are now part of the base package. | |||
== Building Traffic Files == | == Building Traffic Files == | ||
| Line 417: | Line 419: | ||
If the FlightGear AI system can't find a valid route between startup location | If the FlightGear AI system can't find a valid route between startup location | ||
and runway, it will list which nodes are not connected and exit. | and runway, it will list which nodes are not connected and exit. | ||
= SIDs / STARs = | |||
SID is an acronym for Standard Instrument Departure. Likewise, STAR is an acronym for STandard Instrument ARrival. Directly after takeoff, in particular at busy airports, aircraft follow a standard flightpath, that will keep them safely separated from arriving traffic, avoid ground obstructions, and also keeps traffic away from populated areas as much as possible. Currently, steps are in progress to allow FlightGear traffic to follow SIDs. Ultimately, the plan is to provide SID and star data in a format that can also be used by the user controlled Aircraft's Flight Management Computer. Currently, some sample data exist in the form of a PropertyList formatted xml file that contains a list of waypoints. | |||
This section of the AI Traffic documentation is meant as a stub that keeps track of the current development. At the moment of writing, some proof-of-principle data for EHAM SIDs will be committed to the World Scenery Repository, along with some experimental code in FlightGear to make use of these data. Note that these data are meant to be just that; a proof of principle. User contributions will be accepted as soon as the format has stabilized. | |||
= Appendix: Special Notes = | = Appendix: Special Notes = | ||