117
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
→fgtraffic.xml
| Line 365: | Line 365: | ||
== fgtraffic.xml == | == fgtraffic.xml == | ||
At startup, FlightGear reads a file called '''fgtraffic.xml'''. In order to let FlightGear use our newly built traffic file, all we need to do is add a reference to the new file. Suppose we saved our file as PH-KCA.xml, all that would be required would be to add the following line: | If you use a current version of FlightGear cvs HEAD/ OpenSceneGraph, activating traffic is easy: Just copy the traffic file into the same directory as where the AI aircraft file resides (for example: data/AI/Aircraft/737). If you use an older version, or if you use the PLIB based version of FlightGear, traffic can be activated according to the following instructions. | ||
At startup, FlightGear (older versions, or CVS PLIB) reads a file called '''fgtraffic.xml'''. In order to let FlightGear use our newly built traffic file, all we need to do is add a reference to the new file. Suppose we saved our file as PH-KCA.xml, all that would be required would be to add the following line: | |||
<traffic include="<path>/PH-KCA.xml", | <traffic include="<path>/PH-KCA.xml", | ||
| Line 378: | Line 380: | ||
<traffic include="general/KSFO/c172.xml"/> | <traffic include="general/KSFO/c172.xml"/> | ||
</trafficlist> | </trafficlist> | ||
== Organizing by airline == | == Organizing by airline == | ||