FlightControl-Master/MOOSE
1
0
Fork 0
mirror of https://github.com/FlightControl-Master/MOOSE.git synced 2025-10-29 16:58:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Documentation

Browse Source
This commit is contained in:
FlightControl_Master 2017-07-20 13:19:39 +02:00
parent a61c6b4fe2
commit 4d33abb0eb
19 changed files with 113 additions and 68 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

68
Moose Development/Moose/AI/AI_A2A_Dispatcher.lua
View File

@ -2109,18 +2109,16 @@ do
-- ![Banner Image](..\Presentations\AI_A2A_DISPATCHER\Dia1.JPG)
--
-- The AI_A2A_GCICAP class is designed to create an automatic air defence system for a coalition setting up GCI and CAP air defenses.
-- The class derives from @{AI#AI_A2A_DISPATCHER} and thus all the methods that are defined in this class, can be used also in AI\_A2A\_GCICAP.
-- The class derives from @{AI#AI_A2A_DISPATCHER} and thus, all the methods that are defined in the @{AI#AI_A2A_DISPATCHER} class, can be used also in AI\_A2A\_GCICAP.
--
-- ====
--
-- # Demo Mission
-- # Demo Missions
--
-- ### [AI\_A2A\_GCICAP Demo Mission](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/release-2-2-pre/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration)
-- ### [AI\_A2A\_GCICAP for mission designers](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/release-2-2-pre/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration)
--
-- ### [AI\_A2A\_GCICAP Mission, only for beta testers](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/master/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration)
-- ### [AI\_A2A\_GCICAP for beta testers](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/master/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration)
--
-- ### [ALL Demo Missions pack of the last release](https://github.com/FlightControl-Master/MOOSE_MISSIONS/releases)
--
-- ====
--
-- # YouTube Channel
@ -2131,37 +2129,52 @@ do
--
-- ![Banner Image](..\Presentations\AI_A2A_DISPATCHER\Dia3.JPG)
--
-- AI_A2A_GCICAP includes automatic spawning of Combat Air Patrol aircraft (CAP) and Ground Controlled Intercept aircraft (GCI) in response to enemy
-- air movements that are detected by a ground based radar network.
-- AI\_A2A\_GCICAP includes automatic spawning of Combat Air Patrol aircraft (CAP) and Ground Controlled Intercept aircraft (GCI) in response to enemy
-- air movements that are detected by an airborne or ground based radar network.
--
-- With a little time and with a little work it provides the mission designer with a convincing and completely automatic air defence system.
--
-- The AI_A2A_GCICAP provides a lightweight configuration method using the mission editor. Within a very short time, and with very little coding,
-- the mission designer is able to configure a complete A2A defense system for a coalition using the DCS Mission Editor available functions.
-- Using the DCS Mission Editor, you define borders of the coalition which are guarded by GCICAP,
-- configure airbases to belong to the coalition, define squadrons flying certain types of planes or payloads per airbase, and define CAP zones.
-- **Very little lua needs to be applied, a one liner**, which is fully explained below, which can be embedded
-- right in a DO SCRIPT trigger action or in a larger DO SCRIPT FILE trigger action.
--
-- CAP flights will take off and proceed to designated CAP zones where they will remain on station until the ground radars direct them to intercept
-- detected enemy aircraft or they run short of fuel and must return to base (RTB).
-- When a CAP flight leaves their zone to perform an interception or return to base a new CAP flight will spawn to take their place.
--
-- When a CAP flight leaves their zone to perform a GCI or return to base a new CAP flight will spawn to take its place.
-- If all CAP flights are engaged or RTB then additional GCI interceptors will scramble to intercept unengaged enemy aircraft under ground radar control.
-- With a little time and with a little work it provides the mission designer with a convincing and completely automatic air defence system.
--
-- In short it is a plug in very flexible and configurable air defence module for DCS World.
--
-- The AI_A2A_GCICAP provides a lightweight configuration method using the mission editor.
-- ====
--
-- # The following actions need to be followed when using AI\_A2A\_GCICAP in your mission:
--
--
-- ## 1) Configure a working AI\_A2A\_GCICAP defense system for ONE coalition.
--
-- ### 1.1) Define which airbases are for which coalition.
--
-- ![Mission Editor Action](..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_1.JPG)
--
-- Color the airbases red or blue. You can do this by selecting the airbase on the map, and select the coalition blue or red.
--
-- ### 1.2) Place Groups given a name starting with a **EWR prefix** of your choice to build your EWR network.
-- ### 1.2) Place groups of units given a name starting with a **EWR prefix** of your choice to build your EWR network.
--
-- ![Mission Editor Action](..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_2.JPG)
--
-- **All EWR groups starting with the EWR prefix (text) will be included in the detection system.**
--
-- An EWR network, or, Early Warning Radar network, is used to early detect potential airborne targets and to understand the position of patrolling targets of the enemy.
-- Typically EWR networks are setup using 55G6 EWR, 1L13 EWR, Hawk sr and Patriot str ground based radar units.
-- These radars have different ranges and 55G6 EWR and 1L13 EWR radars are Eastern Bloc units (eg Russia, Ukraine, Georgia) while the Hawk and Patriot radars are Western (eg US).
-- Additionally, ANY other radar capable unit can be part of the EWR network! Also AWACS airborne units, planes, helicopters can help to detect targets, as long as they have radar.
-- Additionally, ANY other radar capable unit can be part of the EWR network!
-- Also AWACS airborne units, planes, helicopters can help to detect targets, as long as they have radar.
-- The position of these units is very important as they need to provide enough coverage
-- to pick up enemy aircraft as they approach so that CAP and GCI flights can be tasked to intercept them.
--
-- ![Banner Image](..\Presentations\AI_A2A_DISPATCHER\Dia7.JPG)
--
-- Additionally in a hot war situation where the border is no longer respected the placement of radars has a big effect on how fast the war escalates.
-- For example if they are a long way forward and can detect enemy planes on the ground and taking off
-- they will start to vector CAP and GCI flights to attack them straight away which will immediately draw a response from the other coalition.
@ -2172,17 +2185,30 @@ do
-- EWR networks are **dynamically maintained**. By defining in a **smart way the names or name prefixes of the groups** with EWR capable units, these groups will be **automatically added or deleted** from the EWR network,
-- increasing or decreasing the radar coverage of the Early Warning System.
--
-- ### 1.3) Place Airplane or Helicopter Groups with late activation switched on
-- ### 1.3) Place Airplane or Helicopter Groups with late activation switched on above the airbases to define Squadrons.
--
-- These are **templates**, with a given name starting with **a Template prefix** above each airbase that you wanna have a squadron.
-- ![Mission Editor Action](..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_3.JPG)
--
-- These are **templates**, with a given name starting with a **Template prefix** above each airbase that you wanna have a squadron.
-- These **templates** need to be within 1.5km from the airbase center. They don't need to have a slot at the airplane, they can just be positioned above the airbase,
-- without a route, and should only have ONE unit.
--
-- ### 1.4) Place floating helicopters to create the CAP zones.
-- ![Mission Editor Action](..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_4.JPG)
--
-- **All airplane or helicopter groups that are starting with any of the choosen Template Prefixes will result in a squadron created at the airbase.**
--
-- ### 1.4) Place floating helicopters to create the CAP zones defined by its route points.
--
-- ![Mission Editor Action](..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_5.JPG)
--
-- **All airplane or helicopter groups that are starting with any of the choosen Template Prefixes will result in a squadron created at the airbase.**
--
-- The helicopter indicates the start of the CAP zone.
-- The route points the form of the CAP zone polygon.
-- The place of the helicopter is important, as the airbase closest to the helicopter will be the airbase from where the CAP planes will take off for CAP.
-- The route points define the form of the CAP zone polygon.
--
-- ![Mission Editor Action](..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_6.JPG)
--
-- **The place of the helicopter is important, as the airbase closest to the helicopter will be the airbase from where the CAP planes will take off for CAP.**
--
-- ## 2) There are a lot of defaults set, which can be further modified using the methods in @{AI#AI_A2A_DISPATCHER}:
--

2
Moose Mission Setup/Moose.lua
View File

@ -1,5 +1,5 @@
env.info( '*** MOOSE DYNAMIC INCLUDE START *** ' )
env.info( 'Moose Generation Timestamp: 20170702_1214' )
env.info( 'Moose Generation Timestamp: 20170720_1318' )
local base = _G

74
docs/Documentation/AI_A2A_Dispatcher.html
View File

@ -1196,17 +1196,15 @@ Therefore if F4s are wanted as a coalition’s CAP or GCI aircraft Germany will
<p>The AI<em>A2A</em>GCICAP class is designed to create an automatic air defence system for a coalition setting up GCI and CAP air defenses.</p>
<p>The class derives from <a href="AI.html##(AI_A2A_DISPATCHER)">AI#AI<em>A2A</em>DISPATCHER</a> and thus all the methods that are defined in this class, can be used also in AI_A2A_GCICAP.</p>
<p>The class derives from <a href="AI.html##(AI_A2A_DISPATCHER)">AI#AI<em>A2A</em>DISPATCHER</a> and thus, all the methods that are defined in the <a href="AI.html##(AI_A2A_DISPATCHER)">AI#AI<em>A2A</em>DISPATCHER</a> class, can be used also in AI_A2A_GCICAP.</p>
<hr/>
<h1>Demo Mission</h1>
<h1>Demo Missions</h1>
<h3><a href="https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/release-2-2-pre/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration">AI_A2A_GCICAP Demo Mission</a></h3>
<h3><a href="https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/release-2-2-pre/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration">AI_A2A_GCICAP for mission designers</a></h3>
<h3><a href="https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/master/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration">AI_A2A_GCICAP Mission, only for beta testers</a></h3>
<h3><a href="https://github.com/FlightControl-Master/MOOSE_MISSIONS/releases">ALL Demo Missions pack of the last release</a></h3>
<h3><a href="https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/master/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration">AI_A2A_GCICAP for beta testers</a></h3>
<hr/>
@ -1218,37 +1216,52 @@ Therefore if F4s are wanted as a coalition’s CAP or GCI aircraft Germany will
<p><img src="..\Presentations\AI_A2A_DISPATCHER\Dia3.JPG" alt="Banner Image"/></p>
<p>AI<em>A2A</em>GCICAP includes automatic spawning of Combat Air Patrol aircraft (CAP) and Ground Controlled Intercept aircraft (GCI) in response to enemy
air movements that are detected by a ground based radar network.
CAP flights will take off and proceed to designated CAP zones where they will remain on station until the ground radars direct them to intercept
detected enemy aircraft or they run short of fuel and must return to base (RTB).
When a CAP flight leaves their zone to perform an interception or return to base a new CAP flight will spawn to take their place.
If all CAP flights are engaged or RTB then additional GCI interceptors will scramble to intercept unengaged enemy aircraft under ground radar control.
With a little time and with a little work it provides the mission designer with a convincing and completely automatic air defence system.
In short it is a plug in very flexible and configurable air defence module for DCS World.</p>
<p>AI_A2A_GCICAP includes automatic spawning of Combat Air Patrol aircraft (CAP) and Ground Controlled Intercept aircraft (GCI) in response to enemy
air movements that are detected by an airborne or ground based radar network. </p>
<p>The AI<em>A2A</em>GCICAP provides a lightweight configuration method using the mission editor.</p>
<p>With a little time and with a little work it provides the mission designer with a convincing and completely automatic air defence system.</p>
<p>The AI<em>A2A</em>GCICAP provides a lightweight configuration method using the mission editor. Within a very short time, and with very little coding,
the mission designer is able to configure a complete A2A defense system for a coalition using the DCS Mission Editor available functions.
Using the DCS Mission Editor, you define borders of the coalition which are guarded by GCICAP,
configure airbases to belong to the coalition, define squadrons flying certain types of planes or payloads per airbase, and define CAP zones.
<strong>Very little lua needs to be applied, a one liner</strong>, which is fully explained below, which can be embedded
right in a DO SCRIPT trigger action or in a larger DO SCRIPT FILE trigger action. </p>
<p>CAP flights will take off and proceed to designated CAP zones where they will remain on station until the ground radars direct them to intercept
detected enemy aircraft or they run short of fuel and must return to base (RTB). </p>
<p>When a CAP flight leaves their zone to perform a GCI or return to base a new CAP flight will spawn to take its place.
If all CAP flights are engaged or RTB then additional GCI interceptors will scramble to intercept unengaged enemy aircraft under ground radar control.</p>
<p>In short it is a plug in very flexible and configurable air defence module for DCS World.</p>
<hr/>
<h1>The following actions need to be followed when using AI_A2A_GCICAP in your mission:</h1>
<h2>1) Configure a working AI_A2A_GCICAP defense system for ONE coalition.</h2>
<h3>1.1) Define which airbases are for which coalition.</h3>
<p><img src="..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_1.JPG" alt="Mission Editor Action"/></p>
<p>Color the airbases red or blue. You can do this by selecting the airbase on the map, and select the coalition blue or red.</p>
<h3>1.2) Place Groups given a name starting with a <strong>EWR prefix</strong> of your choice to build your EWR network.</h3>
<h3>1.2) Place groups of units given a name starting with a <strong>EWR prefix</strong> of your choice to build your EWR network.</h3>
<p><img src="..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_2.JPG" alt="Mission Editor Action"/></p>
<p><strong>All EWR groups starting with the EWR prefix (text) will be included in the detection system.</strong> </p>
<p>An EWR network, or, Early Warning Radar network, is used to early detect potential airborne targets and to understand the position of patrolling targets of the enemy.
Typically EWR networks are setup using 55G6 EWR, 1L13 EWR, Hawk sr and Patriot str ground based radar units.
These radars have different ranges and 55G6 EWR and 1L13 EWR radars are Eastern Bloc units (eg Russia, Ukraine, Georgia) while the Hawk and Patriot radars are Western (eg US).
Additionally, ANY other radar capable unit can be part of the EWR network! Also AWACS airborne units, planes, helicopters can help to detect targets, as long as they have radar.
Additionally, ANY other radar capable unit can be part of the EWR network!
Also AWACS airborne units, planes, helicopters can help to detect targets, as long as they have radar.
The position of these units is very important as they need to provide enough coverage
to pick up enemy aircraft as they approach so that CAP and GCI flights can be tasked to intercept them.</p>
<p><img src="..\Presentations\AI_A2A_DISPATCHER\Dia7.JPG" alt="Banner Image"/></p>
<p>Additionally in a hot war situation where the border is no longer respected the placement of radars has a big effect on how fast the war escalates.
For example if they are a long way forward and can detect enemy planes on the ground and taking off
they will start to vector CAP and GCI flights to attack them straight away which will immediately draw a response from the other coalition.
@ -1259,17 +1272,30 @@ It all depends on what the desired effect is. </p>
<p>EWR networks are <strong>dynamically maintained</strong>. By defining in a <strong>smart way the names or name prefixes of the groups</strong> with EWR capable units, these groups will be <strong>automatically added or deleted</strong> from the EWR network,
increasing or decreasing the radar coverage of the Early Warning System.</p>
<h3>1.3) Place Airplane or Helicopter Groups with late activation switched on</h3>
<h3>1.3) Place Airplane or Helicopter Groups with late activation switched on above the airbases to define Squadrons.</h3>
<p>These are <strong>templates</strong>, with a given name starting with <strong>a Template prefix</strong> above each airbase that you wanna have a squadron.
<p><img src="..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_3.JPG" alt="Mission Editor Action"/></p>
<p>These are <strong>templates</strong>, with a given name starting with a <strong>Template prefix</strong> above each airbase that you wanna have a squadron.
These <strong>templates</strong> need to be within 1.5km from the airbase center. They don't need to have a slot at the airplane, they can just be positioned above the airbase,
without a route, and should only have ONE unit.</p>
<h3>1.4) Place floating helicopters to create the CAP zones.</h3>
<p><img src="..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_4.JPG" alt="Mission Editor Action"/></p>
<p><strong>All airplane or helicopter groups that are starting with any of the choosen Template Prefixes will result in a squadron created at the airbase.</strong> </p>
<h3>1.4) Place floating helicopters to create the CAP zones defined by its route points.</h3>
<p><img src="..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_5.JPG" alt="Mission Editor Action"/></p>
<p><strong>All airplane or helicopter groups that are starting with any of the choosen Template Prefixes will result in a squadron created at the airbase.</strong> </p>
<p>The helicopter indicates the start of the CAP zone.
The route points the form of the CAP zone polygon.
The place of the helicopter is important, as the airbase closest to the helicopter will be the airbase from where the CAP planes will take off for CAP.</p>
The route points define the form of the CAP zone polygon. </p>
<p><img src="..\Presentations\AI_A2A_DISPATCHER\AI_A2A_GCICAP-ME_6.JPG" alt="Mission Editor Action"/></p>
<p><strong>The place of the helicopter is important, as the airbase closest to the helicopter will be the airbase from where the CAP planes will take off for CAP.</strong></p>
<h2>2) There are a lot of defaults set, which can be further modified using the methods in <a href="AI.html##(AI_A2A_DISPATCHER)">AI#AI<em>A2A</em>DISPATCHER</a>:</h2>

1
docs/Documentation/Cargo.html
View File

@ -3542,7 +3542,6 @@ The range till cargo will board.</p>
<dl class="function">
<dt>
<em>#number</em>
<a id="#(CARGO_UNIT).RunCount" >
<strong>CARGO_UNIT.RunCount</strong>
</a>

5
docs/Documentation/Designate.html
View File

@ -694,8 +694,8 @@ If not activated, Targets will be selected in a random order, but most like thos
<h2>6. Designate Menu Location for a Mission</h2>
<p>You can make DESIGNATE work for a MISSION object. In this way, the Designate menu will not appear in the root of the radio menu, but in the menu of the Mission.
Use the method <a href="##(DESIGNATE).SetMission">DESIGNATE.SetMission</a>() to set the MISSION object for the designate function.</p>
<p>You can make DESIGNATE work for a <a href="Mission.html##(MISSION)">Mission#MISSION</a> object. In this way, the designate menu will not appear in the root of the radio menu, but in the menu of the Mission.
Use the method <a href="##(DESIGNATE).SetMission">DESIGNATE.SetMission</a>() to set the <a href="Mission.html">Mission</a> object for the designate function.</p>
<h2>7. Status Report</h2>
@ -917,6 +917,7 @@ function below will use the range 1-7 just in case</p>
<dl class="function">
<dt>
<em></em>
<a id="#(DESIGNATE).LaserCodes" >
<strong>DESIGNATE.LaserCodes</strong>
</a>

3
docs/Documentation/Fsm.html
View File

@ -1598,7 +1598,7 @@ A string defining the start state.</p>
<dl class="function">
<dt>
<em>#string</em>
<em></em>
<a id="#(FSM)._StartState" >
<strong>FSM._StartState</strong>
</a>
@ -1897,6 +1897,7 @@ A string defining the start state.</p>
<dl class="function">
<dt>
<em></em>
<a id="#(FSM).current" >
<strong>FSM.current</strong>
</a>

1
docs/Documentation/Point.html
View File

@ -2829,6 +2829,7 @@ The y coordinate.</p>
<dl class="function">
<dt>
<em></em>
<a id="#(POINT_VEC2).z" >
<strong>POINT_VEC2.z</strong>
</a>

1
docs/Documentation/Positionable.html
View File

@ -1838,7 +1838,6 @@ self</p>
<dl class="function">
<dt>
<em><a href="Core.Spot.html##(SPOT)">Core.Spot#SPOT</a></em>
<a id="#(POSITIONABLE).Spot" >
<strong>POSITIONABLE.Spot</strong>
</a>

2
docs/Documentation/Settings.html
View File

@ -1142,7 +1142,7 @@ true if metric.</p>
<dl class="function">
<dt>
<em>#boolean</em>
<em></em>
<a id="#(SETTINGS).Metric" >
<strong>SETTINGS.Metric</strong>
</a>

17
docs/Documentation/Spawn.html
View File

@ -2194,9 +2194,6 @@ The group that was spawned. You can use this group for further actions.</p>
<p> Don't repeat the group from Take-Off till Landing and back Take-Off by ReSpawning.</p>
</dd>
</dl>
<dl class="function">
@ -2729,9 +2726,6 @@ when nothing was spawned.</p>
<p> Overwrite unit names by default with group name.</p>
</dd>
</dl>
<dl class="function">
@ -2746,9 +2740,6 @@ when nothing was spawned.</p>
<p> By default, no InitLimit</p>
</dd>
</dl>
<dl class="function">
@ -2784,7 +2775,7 @@ when nothing was spawned.</p>
<dl class="function">
<dt>
<em>#number</em>
<em></em>
<a id="#(SPAWN).SpawnMaxGroups" >
<strong>SPAWN.SpawnMaxGroups</strong>
</a>
@ -2801,7 +2792,7 @@ when nothing was spawned.</p>
<dl class="function">
<dt>
<em>#number</em>
<em></em>
<a id="#(SPAWN).SpawnMaxUnitsAlive" >
<strong>SPAWN.SpawnMaxUnitsAlive</strong>
</a>
@ -3129,7 +3120,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):Schedule( 600, 0.5 )
<dl class="function">
<dt>
<em>#boolean</em>
<em></em>
<a id="#(SPAWN).SpawnUnControlled" >
<strong>SPAWN.SpawnUnControlled</strong>
</a>
@ -3153,7 +3144,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):Schedule( 600, 0.5 )
<p> Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.</p>
<p> When the first Spawn executes, all the Groups need to be made visible before start.</p>
</dd>
</dl>

1
docs/Documentation/SpawnStatic.html
View File

@ -436,7 +436,6 @@ ptional) The name of the new static.</p>
<dl class="function">
<dt>
<em>#number</em>
<a id="#(SPAWNSTATIC).SpawnIndex" >
<strong>SPAWNSTATIC.SpawnIndex</strong>
</a>

2
docs/Documentation/Task_Cargo.html
View File

@ -630,7 +630,7 @@ based on the tasking capabilities defined in <a href="Task.html##(TASK)">Task#TA
<dl class="function">
<dt>
<em></em>
<em>#number</em>
<a id="#(TASK_CARGO).CargoLimit" >
<strong>TASK_CARGO.CargoLimit</strong>
</a>

BIN
docs/Presentations/AI_A2A_DISPATCHER/AI_A2A_GCICAP-ME_1.JPG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 180 KiB

BIN
docs/Presentations/AI_A2A_DISPATCHER/AI_A2A_GCICAP-ME_2.JPG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 428 KiB

BIN
docs/Presentations/AI_A2A_DISPATCHER/AI_A2A_GCICAP-ME_3.JPG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 306 KiB

BIN
docs/Presentations/AI_A2A_DISPATCHER/AI_A2A_GCICAP-ME_4.JPG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 180 KiB

BIN
docs/Presentations/AI_A2A_DISPATCHER/AI_A2A_GCICAP-ME_5.JPG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 412 KiB

BIN
docs/Presentations/AI_A2A_DISPATCHER/AI_A2A_GCICAP-ME_6.JPG Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 299 KiB

4
docs/README.md
View File

@ -81,7 +81,9 @@ Each TASK has a TASK ACTION flow, which is the flow that a player (hosted by a U
MOOSE AI Controlling Classes provide mechanisms to control AI over long lasting processes.
These AI Controlling Classes are based on FSM (Finite State Machine) Classes, and provided an encapsulated way to make AI behave or execute an activity.
* [AI_A2A_DISPATCHER](Documentation/AI_A2A_Dispatcher.html): Create an automatic and dynamic A2A defense system, executed by AI units, as a result of detected A2A airborne targets executing CAP and GCI. This script replaces the GCICAP script.
* [AI_A2A_GCICAP](Documentation/AI_A2A_Dispatcher.html): Create an automatic and dynamic A2A defense system, executed by AI units, as a result of detected A2A airborne targets executing CAP and GCI. Using an easy process you can define an air defense strategy using the Mission Editor.
* [AI_A2A_DISPATCHER](Documentation/AI_A2A_Dispatcher.html): Same as AI\_A2A\_GCICAP, but is for more advanced or developer type mission designers. This class provides more options.
* [AI_BALANCER](Documentation/AI_Balancer.html): Compensate in a multi player mission the abscence of players with dynamically spawned AI air units. When players join CLIENTS, the AI will either be destroyed, or will fly back to the home or nearest friendly airbase.