MOOSE - Mission Object Oriented Scripting Framework

[FlightControl]

Before i forget, a big thanks to stonehouse for his feedback and help on GCICAP. Thanks to alpenwolf, pikey, Viff, ironjockel, 132nd.etcher, gunterlund, and many others for helping with the testing.

 

Now there is time to improve the documentation, proof reading, add missing parts.

There is still work left to add (small) enhancements on the menu system for the tasking and reports. There is a backlog of requests and enhancements on GitHub to be looked into...

 

But am curious on your experience with this release.

[Silvern]

I have mobile access and can answer questions.

Now there's also a good demo published in the forums, which helps a lot.

 

I suggest you try out the different parameters and placements of the airbases, zones, attackers etc.

 

If you wanna add a defense system for the blue coalition, then define a dispatcher for blue, and setup EWR, airbases, squadrons and other attributes facts for blue also.

 

You can remove the info panel by commenting or deleting A2ADispatcher:SetTacticalDisplay( true )

 

 

Sv.

 

I've tested the corrected script and I've got it working now. Thanks for your help.

 

I've modified the script some further and achieved some good results, but I've also encountered a bug when deploying it in a mission of mine.

 

I've defined 3 airfield near Tbilisi as "red" in the mission and Vaziani as the base for "red" GCICAP flight. When all three airfields are marked as "red", the script bugs out. Instead of sending 2 planes per group, it would send one plane and two groups. Planes would do an airborne start instead of starting on runway like defined in the script.

 

But if I changed the other two airfields near Vaziani to neutral coalition, the script would work normally and groups would spawn on the runway instead of in the air. I assume it is something related to the close proximity of these 3 airfields around Tbilisi.

 

 

Now I have to try to limit the resources of red GCICAP flights so that they don't spawn hundreds of planes.

 

Great work on this framework! Love it!

[FlightControl]

I've tested the corrected script and I've got it working now. Thanks for your help.

 

I've modified the script some further and achieved some good results, but I've also encountered a bug when deploying it in a mission of mine.

 

I've defined 3 airfield near Tbilisi as "red" in the mission and Vaziani as the base for "red" GCICAP flight. When all three airfields are marked as "red", the script bugs out. Instead of sending 2 planes per group, it would send one plane and two groups. Planes would do an airborne start instead of starting on runway like defined in the script.

 

But if I changed the other two airfields near Vaziani to neutral coalition, the script would work normally and groups would spawn on the runway instead of in the air. I assume it is something related to the close proximity of these 3 airfields around Tbilisi.

 

 

Now I have to try to limit the resources of red GCICAP flights so that they don't spawn hundreds of planes.

 

Great work on this framework! Love it!

 

Ha yes. This can be. Didn't think of this problem.

Actually, the perimeter wherein could become smaller.

Or I need to check the error and see what I can do.

Will check it. Can you post an example where in the problem occurs?

[Silvern]

Ok, I will post an example later today.

[FlightControl]

Ok, I will post an example later today.

 

If I would reduce the radius where templates can be placed from 10km to 4km, which is the average size of an airfield, would that be okay and still be user friendly?

The consequence is that mission designers need to be a bit more precise when placing the templates, but I think should not be an impossible thing....

 

Thinking about it, the radius calculation to catch the templates near airfields could be refined.

For example:

- A default of 4 km for airbases.

- A default of 0.5 km for farps.

- A default of 1 km for ships.

 

 

Many funny things can be added ....

...

[Silvern]

If I would reduce the radius where templates can be placed from 10km to 4km, which is the average size of an airfield, would that be okay and still be user friendly?

The consequence is that mission designers need to be a bit more precise when placing the templates, but I think should not be an impossible thing....

 

Thinking about it, the radius calculation to catch the templates near airfields could be refined.

For example:

- A default of 4 km for airbases.

- A default of 0.5 km for farps.

- A default of 1 km for ships.

 

 

Many funny things can be added ....

...

 

4km is more than enough. Don't know about others, but I usually just place templates directly over the airfields. It's more transparent that way.

 

 

Your GCICAP script supports carrier operations? So that planes can take off on patrols and intercepts from the carrier?

[FlightControl]

4km is more than enough. Don't know about others, but I usually just place templates directly over the airfields. It's more transparent that way.

 

 

Your GCICAP script supports carrier operations? So that planes can take off on patrols and intercepts from the carrier?

 

Try it :-)

[Silvern]

Try it :-)

 

Will do!

 

I attached an example of the Tbilisi area bug. Probably an over-lap or something. If you set Tbilisi-Lochini and Sogunlag to neutral, then it works ok with the same script.

MooseGCI.miz

MooseGCI.lua

[FlightControl]

Fixed

 

Will do!

 

I attached an example of the Tbilisi area bug. Probably an over-lap or something. If you set Tbilisi-Lochini and Sogunlag to neutral, then it works ok with the same script.

 

Hi Silvern,

 

I've done some good updates:

 

 

• Optimized range of template placement for AI_A2A_GCICAP to 1.5km from center of airbase.
  
• Optimized takeoff height when airplanes spawn in the air.
  
• Optimized helicopters to be included in detections.
  

 

 

There is a demonstration mission that you can download:

 

 

 

https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/release-2-2-pre/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration

 

 

 

 

This demonstration mission has been optimized and a few things have been added:

 

• Added FARP and template placed above FARP.
  
• Added helicopters that are attacked by defending helicopters.
  
• Added Ship Kuznetov
  
• Added Templates placed above Ship.
  
• Range is now 1.5 km to place templates above airbases, so adjusted templates location.
  
• Take-off height is set to 200 above the airbase when spawning mid air.
  

 

The documentation for the GCICAP has been updated:

 

http://flightcontrol-master.github.io/MOOSE/Documentation/AI_A2A_Dispatcher.html#AI_A2A_GCICAP

 

 

 

Hope you like the changes!

 

FC

[Silvern]

Thanks! I'll check it out.

 

By the way, how did you define the carrier as a spawn point? Do you maybe have a lua example?

[HiJack]

Awesome job FC! :thumbup: I'm currently on sick leave from flying but will hopefully start creating some mission over the summer and will definitely be looking in to this new tasking classes. :)

[FlightControl]

Thanks! I'll check it out.

 

By the way, how did you define the carrier as a spawn point? Do you maybe have a lua example?

 

SPAWN:SpawnAtAirbase

 

http://flightcontrol-master.github.io/MOOSE/Documentation/Spawn.html##(SPAWN).SpawnAtAirbase

 

There is a lua example in the moose code.

 

Fc

[Silvern]

SPAWN:SpawnAtAirbase

 

http://flightcontrol-master.github.io/MOOSE/Documentation/Spawn.html##(SPAWN).SpawnAtAirbase

 

There is a lua example in the moose code.

 

Fc

 

Thanks, I've got it working.

Really good job with this framework. Brings so much life and unpredictability into the missions. :thumbup:

 

Are there any plans for an AI air to ground dispatcher also?

Something similar to AI_A2A dispatcher, where mission builder could define squadron template, airfield and the assigned ground targets?

[FlightControl]

Thanks, I've got it working.

Really good job with this framework. Brings so much life and unpredictability into the missions. :thumbup:

 

Are there any plans for an AI air to ground dispatcher also?

Something similar to AI_A2A dispatcher, where mission builder could define squadron template, airfield and the assigned ground targets?

 

Of course there will be an A2G version of it.

And a G2G too.

 

I am already working on it.

 

Can you do the framework a favour?

 

Could you upload your mission miz file and the mission script in this thread

and in the GCICAP thread?

 

Your experience may be of interest for many of your fellow dcs community members.

 

Thank you in advance!

 

Sven

[Silvern]

Of course there will be an A2G version of it.

And a G2G too.

 

I am already working on it.

 

Excellent news! If AI A2G taskings can be simulated like the A2A is now, mission builders can actually create a living "war" enviroment.

 

And G2G would be the cherry on top. Exciting times. :joystick:

 

Can you do the framework a favour?

 

Could you upload your mission miz file and the mission script in this thread

and in the GCICAP thread?

 

Your experience may be of interest for many of your fellow dcs community members.

 

Thank you in advance!

 

Sven

 

Will do! Right now I'm still learning, but as soon as I have something presentable I'll share it here. :)

[DArt]

Thank a lot for this awesome framework!!! Very useful!

[FlightControl]

A couple of updates on release 2.2.0 pre since the last communication:

 

https://github.com/FlightControl-Master/MOOSE/releases

 

 

• Added A2A LL and MGRS on top of BRAA and BULLS. Now A2G has BR, MGRS and LL and A2A has BRAA, BULLS, LL and MGRS.
  
• Fixed Zones problem with {} in AI_A2A_DISPATCHER:SetBorderZone and DETECTION_BASE:SetAcceptZones and DETECTION_BASE:SetRejectZones. Now a single zone object or multiple zone objects in a list can be given.
  
• Fixed issue where A2G cannot be selected for A2G tasks with an airplane.
  
• Fixed problem with nil value in Detection.lua
  
• Adapted task menus to know the task type for the reporting mode selected.
  
• Optimized range of template placement for AI_A2A_GCICAP to 1.5km from center of airbase.
  
• Optimized takeoff height when airplanes spawn in the air.
  
• Optimized helicopters to be included in detections.
  
• Fixed some glitches in Detection (when Detection Set is empty).
  
• Tasks now have MISSION menus under a command center on coalition level.
  
• The DESIGNATE:New() method has now an optional 4th parameter setting the MISSION object where the designate menu should be placed.
  
• Fixed double menu items in planned tasks for one task when a player joined.
  
• New targets for the same A2G task are now reported and are assigned to the task automatically.
  

Edited July 25, 2017 by FlightControl

[Rivvern]

This is looking great. Too bad im too dumb to understand how to put it all together.

 

Ive got the following to work:

A2A_GCICAP_Blue = AI_A2A_GCICAP:New( { "blue ewr" }, { "blue sq kutaisi" }, { "blue cap west" }, 4 ) 
A2A_GCICAP_Red = AI_A2A_GCICAP:New( { "red ewr" }, { "red sq anapa" }, { "red cap west" }, 4 ) 
A2A_GCICAP_Red:SetTacticalDisplay( true )

 

But what i really want is to assign squadrons to airbases each with a cap zone.

How can i do that?

moose gcicap testing.miz

[FlightControl]

This is looking great. Too bad im too dumb to understand how to put it all together.

 

Ive got the following to work:

A2A_GCICAP_Blue = AI_A2A_GCICAP:New( { "blue ewr" }, { "blue sq kutaisi" }, { "blue cap west" }, 4 ) 
A2A_GCICAP_Red = AI_A2A_GCICAP:New( { "red ewr" }, { "red sq anapa" }, { "red cap west" }, 4 ) 
A2A_GCICAP_Red:SetTacticalDisplay( true )

But what i really want is to assign squadrons to airbases each with a cap zone.

How can i do that?

 

Hey,

 

First of all, nobody is dumb here! There are only good questions! :thumbup:

 

Second, Great you have the energy (lol) to try this out and communicate here your questions!

 

Let me help you, because your questions are GREAT! They help me to improve the documentation.

 

A2A_GCICAP_Blue is an object of AI_A2A_GCICAP. It has methods (=functions) that you can call just like SetTacticalDisplay()...

And AI_A2A_GCICAP "derives" or "inherits" all the methods from AI_A2A_DISPATCHER... So all methods defined in AI_A2A_DISPATCHER are also available for your A2A_GCICAP_Blue object!!!

 

These methods of AI_A2A_DISPATCHER are documented here:

http://flightcontrol-master.github.io/MOOSE/Documentation/AI_A2A_Dispatcher.html#AI_A2A_DISPATCHER

 

- Chapter 6 talks about how to setup a squadron for an airbase using lua code.

- Chapter 7 talks about how to define for a squadron a CAP zone.

 

There are 3 methods that you need to do exactly what you want!

 

 

I need to document this a bit better in the documentation, so I'll write it here:

 

The first method is SetSquadron... It has the following parameters:

 

SquadronName is a string (text) that defines the squadron identifier. It can be any name, for example "104th Squadron" or "SQ SQUADRON1", whatever. As long as you remember that this name becomes the identifier of your squadron you have defined. You need to use this name in other methods too!

 

AirbaseName is the airbase where you want to have the squadron located. You need to type here EXACTLY the name of the airbase as you see it in the mission editor. Examples are "Batumi" or "Tbilisi-Lochini". EXACTLY the airbase name!!! In quotes.

 

SpawnTemplates is an array of prefix names of the templates (not going to explain what is templates here again), or, you can specify here one template. Examples are { "104th", "105th" } or "104th" or "Template 1" or "BLUE PLANES". Whatever, just remember that your template (groups late activated) need to start with the prefix you have specified in your code.

If you have only one prefix name for a squadron, you don't need to use the { }, otherwise you need to use them.

 

Resources is a number. From 1 to 40. It is still a bit buggy, this part. Just make this a large number for the moment. This will be fine tuned later.

 

So examples how to define a squadron for you is:

 

A2A_GCICAP_Blue:SetSquadron( "Squadron1", "Batumi", "SQ1", 40 )

This will create squadron "Squadron1" at "Batumi" airbase, and will use plane types "SQ1" and has 40 planes in stock...

 

simple he!

 

Okay, now how to setup CAP... Same method basically... Please read carefully chapter 6 and 7.

 

Note that you also may need to read all about ZONES!!!

 

 

Heres an example how to setup CAP for "Squadron1"

 

local ZoneCAPBlue = ZONE_POLYGON:New( "ZoneCAP", GROUP:FindByName( "ZoneCAPBlue" ) )

This creates a local object ZoneCAPBlue of type ZONE_POLYGON. The code will search for a GROUP (that is late activated) with the name "ZoneCAPBlue" as defined within your mission editor. The route points of the group in the mission editor define the polygon. With the retrieved GROUP object, a new ZONE_POLYGON is created and stored as an object (reference) in ZoneCAPBlue.

 

 

A2A_GCICAP_Blue:SetSquadronCap( "Squadron1", ZoneCAPBlue, 4000, 10000, 500, 700, 800, 1100 )

This makes your CAP for "Squadron1"... The CAP will take place in ZoneCAPBlue, with an altitude between 4000 and 10000 meters, and the patrol will take place between 500 and 700 km/h. When engaging, the speed will be between 800 and 1100 km/h.

 

 

There are further parameters for CAP, namely the Intervals.

That specifies how frequent new CAP will spawn or will be checked to be spawned.

 

Check chapter 7.2...

 

SetSquadronCapInterval will define how many CAP, the CAP frequency... example for "Squadron1":

 

A2A_GCICAP_Blue:SetSquadronCapInterval( "Squadron1", 4, 600, 1200, 1 )

This will change the default intervals set for CAP to 4 CAP maximum in the air in the zone, and check each 600 to 1200 seconds for CAP. Forget the 1 parameter... This is for future use to switch between CAP zones and define which CAP has preference (so if you have 3 CAP zones, i want to have a probability of ( 20%, 20%, 60% ) for example where the CAP should be performed :-)

 

Hope this helps.

 

I also encourage you to have a careful look at the other methods too!

You can change takeoff type, landing type, grouping, overhead etc.

 

More to be added later. Our community has great ideas of stuff to add!

 

Cheers!

Edited July 25, 2017 by FlightControl

[Rivvern]

So before starting building my script. Which of the following should i use? You say they got the same functions. Or is one for use with EWR and the other without? And do i need to create one one object for each side?

 

AIA2ADISPATCHER.New

AI - The AIA2ADISPATCHER creates an automatic A2A defense system based on an EWR network targets and coordinating CAP and GCI.

or

AI_A2A_GCICAP:New

The AIA2AGCICAP class is designed to create an automatic air defence system for a coalition setting up GCI and CAP air defenses.

 

 

But for example: (assuming i got two flight templates called "F-15C", and "MiG-29"

A2A_GCICAP_Blue = AI_A2A_GCICAP:New( { "blue ewr" }, { "blue cap west", "blue cap east" } ) 
A2A_GCICAP_Red = AI_A2A_GCICAP:New( { "red ewr" }, { "red cap west", "red cap east" } ) 
A2A_GCICAP_Blue:SetSquadron( "SquadronBlue1", "Batumi", "F-15C", 40 )
A2A_GCICAP_Red:SetSquadron( "SquadronRed1", "Sochi-Adler", "MiG-29", 40 )
...

 

And Im confused by the two first lines, what do i need to specify?

[FlightControl]

AI_A2A_GCICAP

 

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.

 

In other words, it provides additional logic to configure a defense system using the mission editor while AI_A2A_DISPATCHER is more powerful, but requires some coding.

And you can mix both.

[FlightControl]

But for example: (assuming i got two flight templates called "F-15C", and "MiG-29"

A2A_GCICAP_Blue = AI_A2A_GCICAP:New( { "blue ewr" }, { "blue cap west", "blue cap east" } ) 
A2A_GCICAP_Red = AI_A2A_GCICAP:New( { "red ewr" }, { "red cap west", "red cap east" } ) 
A2A_GCICAP_Blue:SetSquadron( "SquadronBlue1", "Batumi", "F-15C", 40 )
A2A_GCICAP_Red:SetSquadron( "SquadronRed1", "Sochi-Adler", "MiG-29", 40 )
...

 

And Im confused by the two first lines, what do i need to specify?

 

Write your first two lines as follows:

 

A2A_GCICAP_Blue = AI_A2A_GCICAP:New( { "blue ewr" }, { } )

A2A_GCICAP_Red = AI_A2A_GCICAP:New( { "red ewr" }, { } )

 

So, These will create you an EWR network, but won't configure you templates at airbases or CAP zones.

 

So, now you got for blue a SquadronBlue1... You can setup CAP in zone "blue cap west" as:

 

A2A_GCICAP_Blue:SetSquadronCap( "SquadronBlue1", ZONE_POLYGON:New( "blue cap west", GROUP:FindByName( "blue cap west" ) ), 4000, 10000, 700, 900, 800, 1100 )

[FlightControl]

But what i really want is to assign squadrons to airbases each with a cap zone.

How can i do that?

 

I have a question for you:

 

Which coalition has which airbases?

Which airbases have which squadron?

Which squadron has which template?

Which squadron will patrol in which CAP zone?

Edited July 25, 2017 by FlightControl

[Rivvern]

For learning and testing purpose i started a new simple mission to get things going without getting things complicated.

 

I have a question for you:

 

Which coalition has which airbases?

Which airbases have which squadron?

Which squadron will patrol in which CAP zone?

 

BLUE

Batumi, blue sq 1, blue cap 1

Kobuleti, blue sq 2, blue cap 2

 

RED

Sukhumi-Babushara, red sq 1, red cap 1

Gudauta, red sq 2, red cap 2

[FlightControl]

For learning and testing purpose i started a new simple mission to get things going without getting things complicated.

 

 

 

BLUE

Batumi, blue sq 1, blue cap 1

Kobuleti, blue sq 2, blue cap 2

 

RED

Sukhumi-Babushara, red sq 1, red cap 1

Gudauta, red sq 2, red cap 2

 

Ok. Cool.

 

Next question.

Are these CAP near each respective air base?

What templates is each squadron flying?

 

The reason for my squadron is:

- if CAP zones are near the base, or the CAP zone starts near the base, use AI_A2A_GCICAP. No coding needed.

- if CAP zones are far from the base and you cannot place the zone helicopter "near" the base, then you need to go for AI_A2A_DISPATCHER.

 

But from where I see now, I think all can be done using AI_A2A_GCICAP.

Edited July 25, 2017 by FlightControl