1. AI_A2A_DISPATCHER constructor:
+
The AIA2ADISPATCHER.New() method creates a new AI_A2A_DISPATCHER instance.
1.1. Define the EWR network:
-As part of the AI_A2A_DISPATCHER constructor, an EWR network must be given as the first parameter. +
As part of the AI_A2A_DISPATCHER :New() constructor, an EWR network must be given as the first parameter. 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.
See the following example to setup an EWR network containing EWR stations and AWACS.
+
+
-- Define a SET_GROUP object that builds a collection of groups that define the EWR network.
-- Here we build the network with all the groups that have a name starting with DF CCCP AWACS and DF CCCP EWR.
DetectionSetGroup = SET_GROUP:New()
@@ -965,11 +971,11 @@ Detection = DETECTION_AREAS:New( DetectionSetGroup, 30000 )
A2ADispatcher = AI_A2A_DISPATCHER:New( Detection )
The above example creates a SET_GROUP instance, and stores this in the variable (object) DetectionSetGroup. DetectionSetGroup is then being configured to filter all active groups with a group name starting with DF CCCP AWACS or DF CCCP EWR to be included in the Set. -DetectionSetGroup is then being ordered to start the dynamic filtering. Note that any destroy or new spawn of a group with the above names will be removed or added to the Set. -Then a new Detection object is created from the class DETECTION_AREAS. A grouping radius of 30000 is choosen, which is 30km. +DetectionSetGroup is then being ordered to start the dynamic filtering. Note that any destroy or new spawn of a group with the above names will be removed or added to the Set.
+ +Then a new Detection object is created from the class DETECTION_AREAS. A grouping radius of 30000 is choosen, which is 30km. The Detection object is then passed to the AIA2ADISPATCHER.New() method to indicate the EWR network configuration and setup the A2A defense detection mechanism.
You could build a mutual defense system like this:
@@ -1003,6 +1009,13 @@ You need to evaluate the value of this parameter carefully. If too small, more intercept missions may be triggered upon detected target areas. If too large, any airborne cap may not be able to reach the detected target area in time, because it is too far. +In this example an engage radius is set to 80 km.
+ +-- Initialize the dispatcher, setting up a radius of 80km where any airborne friendly
+-- without an assignment within 80km radius from a detected target, will engage that target.
+A2ADispatcher:SetEngageRadius( 80000 )
+4. Set the Intercept radius or Gci radius:
When targets are detected that are still really far off, you don't want the AIA2ADISPATCHER to launch intercepts just yet. @@ -1011,6 +1024,12 @@ The Gci radius is by default defined as 200km. This value can be overridden usin Override the default Gci radius when the era of the warfare is early, or, when you don't want to let the AIA2ADISPATCHER react immediately when a certain border or area is not being crossed.
+In this example, the GCI radius is setto 150 km:
+ +-- Initialize the dispatcher, setting up a GCI radius of 150km where no GCI will be started if the target is further than 150 km from the closest airabse.
+A2ADispatcher:SetGciRadius( 80000 )
+5. Set the borders:
According to the tactical and strategic design of the mission broadly decide the shape and extent of red and blue territories. @@ -1030,6 +1049,22 @@ If a hot war is chosen then no borders actually need to be defi it makes it easier sometimes for the mission maker to envisage where the red and blue territories roughly are. In a hot war the borders are effectively defined by the ground based radar coverage of a coalition.
+In this example a border is set for the CCCP A2A dispatcher:
+ +
-- Setup the A2A dispatcher, and initialize it.
+A2ADispatcher = AI_A2A_DISPATCHER:New( Detection )
+
+-- Setup the border.
+-- Initialize the dispatcher, setting up a border zone. This is a polygon,
+-- which takes the waypoints of a late activated group with the name CCCP Border as the boundaries of the border area.
+-- Any enemy crossing this border will be engaged.
+
+CCCPBorderZone = ZONE_POLYGON:New( "CCCP Border", GROUP:FindByName( "CCCP Border" ) )
+A2ADispatcher:SetBorderZone( CCCPBorderZone )
+6. Squadrons:
The AI_A2A_DISPATCHER works with Squadrons, that need to be defined using the different methods available.
@@ -1059,6 +1094,18 @@ while defining which plane types are being used by the squadron and how many resFor performance and bug workaround reasons within DCS, squadrons have different methods to spawn new aircraft or land returning or damaged aircraft.
+This example defines a couple of squadrons. Note the templates defined within the Mission Editor.
+ +
+
-- Setup the squadrons.
+ A2ADispatcher:SetSquadron( "Mineralnye", AIRBASE.Caucasus.Mineralnye_Vody, { "SQ CCCP SU-27" }, 20 )
+ A2ADispatcher:SetSquadron( "Maykop", AIRBASE.Caucasus.Maykop_Khanskaya, { "SQ CCCP MIG-31" }, 20 )
+ A2ADispatcher:SetSquadron( "Mozdok", AIRBASE.Caucasus.Mozdok, { "SQ CCCP MIG-31" }, 20 )
+ A2ADispatcher:SetSquadron( "Sochi", AIRBASE.Caucasus.Sochi_Adler, { "SQ CCCP SU-27" }, 20 )
+ A2ADispatcher:SetSquadron( "Novo", AIRBASE.Caucasus.Novorossiysk, { "SQ CCCP SU-27" }, 20 )
+6.1. Set squadron take-off methods
@@ -1096,6 +1143,23 @@ The more and the longer aircraft need to taxi at an airfield, the more risk therCurrently within the DCS engine, the airfield traffic coordination is erroneous and contains a lot of bugs. If you experience while testing problems with aircraft take-off or landing, please use one of the above methods as a solution to workaround these issues!
+This example sets the default takeoff method to be from the runway. +And for a couple of squadrons overrides this default method.
+ + -- Setup the Takeoff methods
+
+ -- The default takeoff
+ A2ADispatcher:SetDefaultTakeOffFromRunway()
+
+ -- The individual takeoff per squadron
+ A2ADispatcher:SetSquadronTakeoff( "Mineralnye", AI_A2A_DISPATCHER.Takeoff.Air )
+ A2ADispatcher:SetSquadronTakeoffInAir( "Sochi" )
+ A2ADispatcher:SetSquadronTakeoffFromRunway( "Mozdok" )
+ A2ADispatcher:SetSquadronTakeoffFromParkingCold( "Maykop" )
+ A2ADispatcher:SetSquadronTakeoffFromParkingHot( "Novo" )
+6.2. Set squadron landing methods
In analogy with takeoff, the landing methods are to control how squadrons land at the airfield:
@@ -1122,6 +1186,23 @@ A2A defense system, as no new CAP or GCI planes can takeoff. Note that the method AIA2ADISPATCHER.SetSquadronLandingNearAirbase() will only work for returning aircraft, not for damaged or out of fuel aircraft. Damaged or out-of-fuel aircraft are returning to the nearest friendly airbase and will land, and are out of control from ground control. +This example defines the default landing method to be at the runway. +And for a couple of squadrons overrides this default method.
+ + -- Setup the Landing methods
+
+ -- The default landing method
+ A2ADispatcher:SetDefaultLandingAtRunway()
+
+ -- The individual landing per squadron
+ A2ADispatcher:SetSquadronLandingAtRunway( "Mineralnye" )
+ A2ADispatcher:SetSquadronLandingNearAirbase( "Sochi" )
+ A2ADispatcher:SetSquadronLandingAtEngineShutdown( "Mozdok" )
+ A2ADispatcher:SetSquadronLandingNearAirbase( "Maykop" )
+ A2ADispatcher:SetSquadronLanding( "Novo", AI_A2A_DISPATCHER.Landing.AtRunway )
+6.3. Set squadron grouping
Use the method AIA2ADISPATCHER.SetSquadronGrouping() to set the grouping of CAP or GCI flights that will take-off when spawned.
@@ -1196,16 +1277,24 @@ multiplied by the Overhead and rounded up to the smallest integer.The following example illustrates how CAP zones are coded:
+
-- CAP Squadron execution.
CAPZoneEast = ZONE_POLYGON:New( "CAP Zone East", GROUP:FindByName( "CAP Zone East" ) )
A2ADispatcher:SetSquadronCap( "Mineralnye", CAPZoneEast, 4000, 10000, 500, 600, 800, 900 )
A2ADispatcher:SetSquadronCapInterval( "Mineralnye", 2, 30, 60, 1 )
+
CAPZoneWest = ZONE_POLYGON:New( "CAP Zone West", GROUP:FindByName( "CAP Zone West" ) )
A2ADispatcher:SetSquadronCap( "Sochi", CAPZoneWest, 4000, 8000, 600, 800, 800, 1200, "BARO" )
A2ADispatcher:SetSquadronCapInterval( "Sochi", 2, 30, 120, 1 )
+
CAPZoneMiddle = ZONE:New( "CAP Zone Middle")
A2ADispatcher:SetSquadronCap( "Maykop", CAPZoneMiddle, 4000, 8000, 600, 800, 800, 1200, "RADIO" )
A2ADispatcher:SetSquadronCapInterval( "Sochi", 2, 30, 120, 1 )
For example, the following setup will create a CAP for squadron "Sochi":
-A2ADispatcher:SetSquadronCap( "Sochi", CAPZoneWest, 4000, 8000, 600, 800, 800, 1200, "BARO" ) - A2ADispatcher:SetSquadronCapInterval( "Sochi", 2, 30, 120, 1 )
+ A2ADispatcher:SetSquadronCap( "Sochi", CAPZoneWest, 4000, 8000, 600, 800, 800, 1200, "BARO" )
+ A2ADispatcher:SetSquadronCapInterval( "Sochi", 2, 30, 120, 1 )
+8. Setup a squadron for GCI:
@@ -1254,7 +1344,8 @@ too short will mean that the intruders may have alraedy passed the ideal interceFor example, the following setup will create a GCI for squadron "Sochi":
-A2ADispatcher:SetSquadronGci( "Mozdok", 900, 1200 )
+ A2ADispatcher:SetSquadronGci( "Mozdok", 900, 1200 )
+9. Other configuration options
@@ -1264,175 +1355,9 @@ too short will mean that the intruders may have alraedy passed the ideal interce Use the method AIA2ADISPATCHER.SetTacticalDisplay() to switch on the tactical display panel. The default will not show this panel. Note that there may be some performance impact if this panel is shown. -10. Mission Editor Guide:
+10. Q & A:
-The following steps need to be followed, in order to setup the different borders, templates and groups within the mission editor:
- -10.1. Define your EWR network:
- -
At strategic positions within the battlefield, position the correct groups of units that have radar detection capability in the battlefield. -Create the naming of these groups as such, that these can be easily recognized and included as a prefix within your lua MOOSE mission script. -These prefixes should be unique, so that accidentally no other groups would be incorporated within the EWR network.
- -10.2. Define the border zone:
- -
For a cold war situation, define your border zone. -You can do this in many ways, as the Zone capability within MOOSE outlines. However, the best practice is to create a ZONE_POLYGON class. -To do this, you need to create a zone using a helicopter group, that is late activated, and has a unique group name. -Place the helicopter where the border zone should start, and draw using the waypoints the polygon zone around the area that is considered the border. -The helicopter group name is included as the reference within your lua MOOSE mission script, so ensure that the name is unique and is easily recognizable.
- -10.3. Define the plane templates:
- -
Define the templates of the planes that define the format of planes that will take part in the A2A defenses of your coalition. -These plane templates will never be activated, but are used to create a diverse airplane portfolio allocated to your squadrons.
- -IMPORTANT! Plane templates MUST be of ONE unit, and must have the Late Activated flag switched on!
- -Plane templates are used to diversify the defending squadrons with:
- --
-
- different airplane types -
- different airplane skins -
- different skill levels -
- different weapon payloads -
- different fuel and other characteristics -
Place these airplane templates are good visible locations within your mission, so you can easily retrieve them back.
- -10.4. Define the CAP zones:
- -
Similar as with the border zone, define the CAP zones using helicopter group templates. Its waypoints define the polygon zones. -But you can also define other zone types instead, like moving zones.
- -
Or you can define also zones using trigger zones.
- -10.5. "Script it":
- -Find the following mission script as an example:
- - -- Define a SET_GROUP object that builds a collection of groups that define the EWR network.
- -- Here we build the network with all the groups that have a name starting with DF CCCP AWACS and DF CCCP EWR.
- DetectionSetGroup = SET_GROUP:New()
- DetectionSetGroup:FilterPrefixes( { "DF CCCP AWACS", "DF CCCP EWR" } )
- DetectionSetGroup:FilterStart()
-
- -- Here we define detection to be done by area, with a grouping radius of 3000.
- Detection = DETECTION_AREAS:New( DetectionSetGroup, 30000 )
-
- -- Setup the A2A dispatcher, and initialize it.
- A2ADispatcher = AI_A2A_DISPATCHER:New( Detection )
-
-
-
- -- Initialize the dispatcher, setting up a border zone. This is a polygon,
- -- which takes the waypoints of a late activated group with the name CCCP Border as the boundaries of the border area.
- -- Any enemy crossing this border will be engaged.
- CCCPBorderZone = ZONE_POLYGON:New( "CCCP Border", GROUP:FindByName( "CCCP Border" ) )
- A2ADispatcher:SetBorderZone( CCCPBorderZone )
-
- -- Initialize the dispatcher, setting up a radius of 100km where any airborne friendly
- -- without an assignment within 100km radius from a detected target, will engage that target.
- A2ADispatcher:SetEngageRadius( 300000 )
-
- -- Setup the squadrons.
- A2ADispatcher:SetSquadron( "Mineralnye", AIRBASE.Caucasus.Mineralnye_Vody, { "SQ CCCP SU-27" }, 20 )
- A2ADispatcher:SetSquadron( "Maykop", AIRBASE.Caucasus.Maykop_Khanskaya, { "SQ CCCP MIG-31" }, 20 )
- A2ADispatcher:SetSquadron( "Mozdok", AIRBASE.Caucasus.Mozdok, { "SQ CCCP MIG-31" }, 20 )
- A2ADispatcher:SetSquadron( "Sochi", AIRBASE.Caucasus.Sochi_Adler, { "SQ CCCP SU-27" }, 20 )
- A2ADispatcher:SetSquadron( "Novo", AIRBASE.Caucasus.Novorossiysk, { "SQ CCCP SU-27" }, 20 )
-
- -- Setup the overhead
- A2ADispatcher:SetSquadronOverhead( "Mineralnye", 1.2 )
- A2ADispatcher:SetSquadronOverhead( "Maykop", 1 )
- A2ADispatcher:SetSquadronOverhead( "Mozdok", 1.5 )
- A2ADispatcher:SetSquadronOverhead( "Sochi", 1 )
- A2ADispatcher:SetSquadronOverhead( "Novo", 1 )
-
- -- Setup the Grouping
- A2ADispatcher:SetSquadronGrouping( "Mineralnye", 2 )
- A2ADispatcher:SetSquadronGrouping( "Sochi", 2 )
- A2ADispatcher:SetSquadronGrouping( "Novo", 3 )
-
- -- Setup the Takeoff methods
- A2ADispatcher:SetSquadronTakeoff( "Mineralnye", AI_A2A_DISPATCHER.Takeoff.Air )
- A2ADispatcher:SetSquadronTakeoffInAir( "Sochi" )
- A2ADispatcher:SetSquadronTakeoffFromRunway( "Mozdok" )
- A2ADispatcher:SetSquadronTakeoffFromParkingCold( "Maykop" )
- A2ADispatcher:SetSquadronTakeoffFromParkingHot( "Novo" )
-
- -- Setup the Landing methods
- A2ADispatcher:SetSquadronLandingAtRunway( "Mineralnye" )
- A2ADispatcher:SetSquadronLandingNearAirbase( "Sochi" )
- A2ADispatcher:SetSquadronLandingAtEngineShutdown( "Mozdok" )
- A2ADispatcher:SetSquadronLandingNearAirbase( "Maykop" )
- A2ADispatcher:SetSquadronLanding( "Novo", AI_A2A_DISPATCHER.Landing.AtRunway )
-
-
- -- CAP Squadron execution.
- CAPZoneEast = ZONE_POLYGON:New( "CAP Zone East", GROUP:FindByName( "CAP Zone East" ) )
- A2ADispatcher:SetSquadronCap( "Mineralnye", CAPZoneEast, 4000, 10000, 500, 600, 800, 900 )
- A2ADispatcher:SetSquadronCapInterval( "Mineralnye", 2, 30, 60, 1 )
-
- CAPZoneWest = ZONE_POLYGON:New( "CAP Zone West", GROUP:FindByName( "CAP Zone West" ) )
- A2ADispatcher:SetSquadronCap( "Sochi", CAPZoneWest, 4000, 8000, 600, 800, 800, 1200, "BARO" )
- A2ADispatcher:SetSquadronCapInterval( "Sochi", 2, 30, 120, 1 )
-
- CAPZoneMiddle = ZONE:New( "CAP Zone Middle")
- A2ADispatcher:SetSquadronCap( "Maykop", CAPZoneMiddle, 4000, 8000, 600, 800, 800, 1200, "RADIO" )
- A2ADispatcher:SetSquadronCapInterval( "Sochi", 2, 30, 120, 1 )
-
- -- GCI Squadron execution.
- A2ADispatcher:SetSquadronGci( "Mozdok", 900, 1200 )
- A2ADispatcher:SetSquadronGci( "Novo", 900, 2100 )
- A2ADispatcher:SetSquadronGci( "Maykop", 900, 1200 )
-10.5.1. Script the EWR network
- -
10.5.2. Script the AI_A2A_DISPATCHER object and configure it
- -
10.5.3. Script the squadrons
- -
Create the squadrons using the AIA2ADISPATCHER.SetSquadron objects using:
- --
-
- Zone#ZONE class to create a zone using a trigger zone set in the mission editor. -
- Zone#ZONE_UNIT class to create a zone around a unit object. -
- Zone#ZONE_GROUP class to create a zone around a group object. -
- Zone#ZONE_POLYGON class to create a polygon zone using a late activated group object. -
Use the @{#AIA2ADISPATCHER.SetSquadronCap)() method to define CAP execution for the squadron, within the CAP zone defined.
- -
Use the @{#AIA2ADISPATCHER.SetSquadronCapInterval)() method to define how many CAP groups can be airborne at the same time, and the timing intervals.
- -
Use the @{#AIA2ADISPATCHER.SetSquadronGci)() method to define GCI execution for the squadron.
- -11. Q & A:
- -11.1. Which countries will be selected for each coalition?
+10.1. Which countries will be selected for each coalition?
Which countries are assigned to a coalition influences which units are available to the coalition.
For example because the mission calls for a EWR radar on the blue side the Ukraine might be chosen as a blue country
@@ -1440,7 +1365,7 @@ so that the 55G6 EWR radar unit is available to blue.
Some countries assign different tasking to aircraft, for example Germany assigns the CAP task to F-4E Phantoms but the USA does not.
Therefore if F4s are wanted as a coalition’s CAP or GCI aircraft Germany will need to be assigned to that coalition.
11.2. Country, type, load out, skill and skins for CAP and GCI aircraft?
+10.2. Country, type, load out, skill and skins for CAP and GCI aircraft?
- Note these can be from any countries within the coalition but must be an aircraft with one of the main tasks being “CAP”. diff --git a/docs/Documentation/Cargo.html b/docs/Documentation/Cargo.html index fe4a4263b..9f6098452 100644 --- a/docs/Documentation/Cargo.html +++ b/docs/Documentation/Cargo.html @@ -3542,7 +3542,6 @@ The range till cargo will board.
- - #number CARGO_UNIT.RunCount diff --git a/docs/Documentation/Settings.html b/docs/Documentation/Settings.html index 6836574d8..318968720 100644 --- a/docs/Documentation/Settings.html +++ b/docs/Documentation/Settings.html @@ -1142,7 +1142,7 @@ true if metric.
-
- #boolean
+
SETTINGS.Metric
diff --git a/docs/Documentation/Spawn.html b/docs/Documentation/Spawn.html
index 6168e3bad..a0a416bf7 100644
--- a/docs/Documentation/Spawn.html
+++ b/docs/Documentation/Spawn.html
@@ -822,12 +822,6 @@ and any spaces before and after the resulting name are removed.
SPAWN:_TranslateRotate(SpawnIndex, SpawnRootX, SpawnRootY, SpawnX, SpawnY, SpawnAngle) - - -- @@ -3159,7 +3153,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):Schedule( 600, 0.5 ) -SPAWN.uncontrolled -- Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.
+When the first Spawn executes, all the Groups need to be made visible before start.