117
edits
AI Systems: Difference between revisions
Jump to navigation
Jump to search
Some restructuring to make the internal subsystems dependency more obvious.
(→AI Models: changed all tags to lowercase, which as of 1.9.1 seems to be what actually works.) |
(Some restructuring to make the internal subsystems dependency more obvious.) |
||
| Line 1: | Line 1: | ||
== | == AI Systems in FlightGear == | ||
[[FlightGear]] has a | [[FlightGear]] has a number of more or less independently operating systems for simulating semi- intelligent interaction with the environment. Because there oftentimes exists some confusion regarding to which system does what, one should take notice of the differences between them: The major distinction is that between an older ATC/AI system, and a newer AIModels system. The AIModels system can, in turn, be controlled in at least three different ways; directly, using a script, through the multiplayer system, and through a subsystem known as the traffic manager. | ||
To enable/disable the ATC/AI system: use --prop:/sim/ai-traffic/enabled=[1|0] | |||
To enable/disable the AIModels system: use --prop:/sim/ai/enabled=[1|0] | |||
== ATC/AI == | |||
The [[ATC|Air Traffic Control]] system simulates interaction between the user and a number of AI controlled cessna and piper aircraft. This system can be controlled using the GUI from within FlightGear. The ATC/AI system is no longer maintained and marked for deprication. Recent reports have indicated that the ATC/AI system my be causing numerical computation problems in some cases, resulting in a flurry of NaN warning messages on the FlightGear console. If you experience this, you might consider shutting down the ATC/AI system | |||
For airports with a tower frequency, if that frequency is tuned in to your radio, you may contact ATC. | For airports with a tower frequency, if that frequency is tuned in to your radio, you may contact ATC. | ||
| Line 10: | Line 17: | ||
* You must be within 40 nautical miles of an ATC facility (towered airport with tower frequencies) to contact ATC. | * You must be within 40 nautical miles of an ATC facility (towered airport with tower frequencies) to contact ATC. | ||
== AI Models == | == AI Models == | ||
| Line 308: | Line 313: | ||
:-Dene | :-Dene | ||
== Submodels == | === Submodels === | ||
Submodels are AI ballistic objects that emanate from, fall from, or launch from the user aircraft. They are presently used to model smoke, contrails, flares, tracers, bombs, drop tanks and flight path markers. | Submodels are AI ballistic objects that emanate from, fall from, or launch from the user aircraft. They are presently used to model smoke, contrails, flares, tracers, bombs, drop tanks and flight path markers. | ||
| Line 314: | Line 319: | ||
As an example examine the submodels file in the Aircraft/737-300 directory. This file creates two submodels which will become the airplane's left and right engine contrails. Each contrail needs its own submodel definition because the contrails begin at different locations. Each contrail consists of a train of individual "puff" models that are released in rapid succession as long as the "trigger" property is true. We ensure an unlimited supply of puffs by setting the "count" parameter to -1. The individual puffs, being AIBallistic objects, will follow their own ballistic paths once released. In this case we have used the "bouyancy" parameter to negate gravity in the ballistic path. The puffs have been given a life span of eight seconds. At cruising speed the [[Boeing 737|737]] will thus have about 400 puffs behind it at any moment. | As an example examine the submodels file in the Aircraft/737-300 directory. This file creates two submodels which will become the airplane's left and right engine contrails. Each contrail needs its own submodel definition because the contrails begin at different locations. Each contrail consists of a train of individual "puff" models that are released in rapid succession as long as the "trigger" property is true. We ensure an unlimited supply of puffs by setting the "count" parameter to -1. The individual puffs, being AIBallistic objects, will follow their own ballistic paths once released. In this case we have used the "bouyancy" parameter to negate gravity in the ballistic path. The puffs have been given a life span of eight seconds. At cruising speed the [[Boeing 737|737]] will thus have about 400 puffs behind it at any moment. | ||
=== Multiplayer Controlled Traffic === | |||
FlightGear's multiplayer system also makes use of the AIModels subsystem. See the [[Multiplayer]] page for more information. | |||
=== Traffic Manager Controlled Traffic === | |||
Traffic Manager Controlled Input to the AIModels subsystem is also known as Interactive Traffic. See: [[Interactive Traffic]] for more information. | |||
==External links== | ==External links== | ||