117
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 44: | Line 44: | ||
To circumvent these problems, a new database format was introduced in FlightGear 1.9.0. In this new format, flights are no longer directly and rigidly assigned to specific aircraft. Instead, a more generic description of a fleet is given, along with a series of flights that need to be carried out. The routing is then taken care of by FlightGear itself. | To circumvent these problems, a new database format was introduced in FlightGear 1.9.0. In this new format, flights are no longer directly and rigidly assigned to specific aircraft. Instead, a more generic description of a fleet is given, along with a series of flights that need to be carried out. The routing is then taken care of by FlightGear itself. | ||
== An example of a traffic file == | == An example of a traffic file == | ||
| Line 477: | Line 473: | ||
</TaxiWaySegments> | </TaxiWaySegments> | ||
</groundnet> | </groundnet> | ||
== Realistic == | |||
With [[FGFS 1.0.0]] Interactive Traffic also reacts on other Non-AI Aicrafts. | |||
The [[Airbus A320|A320]] ( and maybe some others) has working flaps and gears. | |||
==Perfomance== | ==Perfomance== | ||