117
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
→Building Traffic Files
| Line 9: | Line 9: | ||
== Building Traffic Files == | == Building Traffic Files == | ||
Traffic patterns are stored in data files in extended markup language (.xml) format. | Traffic patterns are stored in data files in extended markup language (.xml) format. The actual location of these files are version dependent. For FlightGear 0.9.x, traffic files are stored in a sudirectory called '''Traffic''' in FlightGear's main data directory, hereafter referred to with it's technical name: | ||
<nowiki> | <nowiki> | ||
| Line 15: | Line 15: | ||
</nowiki> | </nowiki> | ||
In FlightGear 1.0., the traffic files can be found in a subdirectory of: | |||
<nowiki> | |||
${FGROOT}/AI/Aircraft/ | |||
</nowiki> | |||
For example, traffic belonging to a united airlines 737 would be located in: <tt>data/AI/Aircraft/737/737-UnitedAirlines-traffic.xml</tt> | |||
FlightGear 1.9.0 has seen yet another move. In this version, the traffic files can be located in: | |||
<nowiki> | |||
${FGROOT}/AI/Traffic/ | |||
</nowiki> | |||
For FlightGear 1.9.0 and later, a new traffic file format was introduced (henceforth referred to as "traffic manager II" format (TM-II), in which aircraft and flights are no longer directly coupled, leading to more flexibility. | |||
Each traffic pattern is built around two entities: Aircraft and Flights. Before discussing the details, lets start by exploring these two concepts a little further. | Each traffic pattern is built around two entities: Aircraft and Flights. Before discussing the details, lets start by exploring these two concepts a little further. | ||