648
edits
AI Systems: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 57: | Line 57: | ||
==== Types of AI Objects ==== | ==== Types of AI Objects ==== | ||
* aircraft | * aircraft | ||
* wingman | * wingman: See [[Howto:Add_wingmen]] for the main article about this subject. | ||
* tanker | * tanker | ||
* carrier | * carrier: The aircraft carrier AI object is based on the "ship" object but is much more complicated. See the scenario file called "data/AI/nimitz_demo.xml" for details. User information can be found at [[Howto:Carrier]] | ||
* ship | * ship | ||
* escort | * escort | ||
| Line 67: | Line 67: | ||
* ballistic | * ballistic | ||
* static | * static | ||
* submodels: 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. See [[Submodels]] for the main article about this subject. See also {{readme file|submodels}}. It gives a good idea about how to create submodel files, what parameters are available and how to use them, and also the type of research needed to make sure the information and models are accurate historically. | |||
AI objects have some things in common: | AI objects have some things in common: | ||
| Line 344: | Line 345: | ||
</interpolation> | </interpolation> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=== Submodels === | === Submodels === | ||
Submodels are controlled by the submodel manager. The manager reads a submodel configuration file at the start of the sim session. This configuration file is written by the aircraft author and defines all the submodels for that particular aircraft. | Submodels are controlled by the submodel manager. The manager reads a submodel configuration file at the start of the sim session. This configuration file is written by the aircraft author and defines all the submodels for that particular aircraft. | ||
| Line 360: | Line 353: | ||
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 === | === Multiplayer controlled traffic === | ||