MOOSE framework - ESCORT class

[FlightControl]

Hello all,

 

For those interested, I've created a mission design training video how to use ESCORT class in MOOSE, the Mission Object Oriënted Scripting Environment. The video walks you through the location where to find the ESCORT class, the different functions, a couple of scenarios where the ESCORT class is used, and how to use the ESCORT class in your missions and lua code.

 

Find it attached here: [ame]

[/ame]

 

 

 

The ESCORT class is a first working version with the core functions available, but the code and its documentation will evolve over time. More APIs, flexibility and features will be added as more users are using it.

 

The test mission of the ESCORT class is to be found here: https://github.com/FlightControl-Master/MOOSE/tree/master/Test%20Missions/Moose_Test_ESCORT

 

Am interested in what you think of the ESCORT class and the video. Foregive my non-native English though :-)

 

cheers,

FC

Edited April 13, 2016 by FlightControl

[Bearfoot]

This is AMAZING. THANK you so much for your work.

 

Will give it a try this week!

 

I am wondering how easy/hard it would be to adopt this for the OPPOSITE mission, i.e., where the player is the escort and the AI is the escorted.

 

I think this can minimally be achieved by just removing some tasks (e.g., Scan targets, Attack targets)? It would be nice to add some tasks (e.g., "withdraw to 4000 ft AGL and orbit", or "switch to waypoint 1 and orbit", followed by join/resume)?

[gunterlund21]

Well done Flightcontrol. Answers alot of questions for me.

[FlightControl]

Thanks guys for the feedback. I am working to extend the ESCORT class now with more flexible APIs to break down the core functions into pieces and parameters, so that you basically can configure the ESCORT process patterns as you want and how many you want.

 

FC

[FlightControl]

While developing, I have a question regarding the real-world "protocol" of AFACs interacting with their home base or other units.

 

Consider the scenario where an AFAC plane would request a ship to fire a missile on an identified target.

 

I am not knowledgeable how in real-life the communication would be done.

Are there people in the community who can advise on:

- What parties are involved in the communication? Would there be a coordination centre, or would the pilot contact the ship directly?

- What standard sentences are exchanged?

- Are there any important terminology that i need to reflect in the communication?

- Are there any verification steps? f.e. if the target is hit or not?

...

 

Please, i would really appreciate if some of the more knowledgeable people could shed some light on this.

 

thanks in advance,

Sven

[FlightControl]

This is AMAZING. THANK you so much for your work.

 

Will give it a try this week!

 

I am wondering how easy/hard it would be to adopt this for the OPPOSITE mission, i.e., where the player is the escort and the AI is the escorted.

 

I think this can minimally be achieved by just removing some tasks (e.g., Scan targets, Attack targets)? It would be nice to add some tasks (e.g., "withdraw to 4000 ft AGL and orbit", or "switch to waypoint 1 and orbit", followed by join/resume)?

 

 

 

 

Hey,

 

 

 

Working today to make the escort class more flexible. This, making initialisation APIs on the class to let the designer choose what menus they want.

 

 

 

Also looking at your suggestions what can be implemented.

 

 

 

Sv.

[FlightControl]

Have implemented the APIs, published them on GITHUB so you can update the version.

 

The APIs available for the moment are:

 

1. ESCORT:MenuFollowAt: Creates a menu to make the escort follow the client.
   
2. ESCORT:MenuHoldAtEscortPosition: Creates a menu to hold the escort at its current position.
   
3. ESCORT:MenuHoldAtLeaderPosition: Creates a menu to hold the escort at the client position.
   
4. ESCORT:MenuScanForTargets: Creates a menu so that the escort scans targets.
   
5. ESCORT:MenuFlare: Creates a menu to disperse flares.
   
6. ESCORT:MenuSmoke: Creates a menu to disparse smoke.
   
7. ESCORT:MenuReportTargets: Creates a menu so that the escort reports targets
   
8. ESCORT:MenuAssistedAttack: Creates a menu strucure to allow assisted attacks executed by other escorts.
   
9. ESCORT: MenuResumeMission: Creates a menu structure so that the escort can resume from a waypoint.
   

You can watch the video here that explains how to use these APIs:[ame=

]

[/ame]

 

 

Or, you can study this test mission, and specifically the lua file of the test mission here: https://github.com/FlightControl-Master/MOOSE/tree/master/Test%20Missions/Moose_Test_ESCORT

 

Hope you like it and find it useful.

 

kind regard,

FC

[FlightControl]

Hi guys, may I remind you of the following script, that allows you to interact with escorting AI on your flight and take the lead.

 

 

Demo scripts here:

 

https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/master-release-2.1/ESC%20-%20Escorting/ESC-001%20-%20Escorting%20Helicopters

 

Each escorting group can be commanded with a whole set of radio commands (radio menu in your flight, and then F10).

The radio commands will vary according the category of the group. The richest set of commands are with Helicopters and AirPlanes. Ships and Ground troops will have a more limited set, but they can provide support through the bombing of targets designated by the other escorts.

 

RADIO MENUs that can be created:

Find a summary below of the current available commands:

Navigation ...:

Escort group navigation functions:

"Join-Up and Follow at x meters": The escort group fill follow you at about x meters, and they will follow you.

"Flare": Provides menu commands to let the escort group shoot a flare in the air in a color.

"Smoke": Provides menu commands to let the escort group smoke the air in a color. Note that smoking is only available for ground and naval troops.

 

Hold position ...:

Escort group navigation functions:

"At current location": Stops the escort group and they will hover 30 meters above the ground at the position they stopped.

"At client location": Stops the escort group and they will hover 30 meters above the ground at the position they stopped.

 

Report targets ...:

Report targets will make the escort group to report any target that it identifies within a 8km range. Any detected target can be attacked using the 4. Attack nearby targets function. (see below).

"Report now": Will report the current detected targets.

"Report targets on": Will make the escort group to report detected targets and will fill the "Attack nearby targets" menu list.

"Report targets off": Will stop detecting targets.

 

Scan targets ...:

Menu items to pop-up the escort group for target scanning. After scanning, the escort group will resume with the mission or defined task.

"Scan targets 30 seconds": Scan 30 seconds for targets.

"Scan targets 60 seconds": Scan 60 seconds for targets.

 

Attack targets ...:

This menu item will list all detected targets within a 15km range. Depending on the level of detection (known/unknown) and visuality, the targets type will also be listed.

Request assistance from ...:

This menu item will list all detected targets within a 15km range, as with the menu item Attack Targets. This menu item allows to request attack support from other escorts supporting the current client group. eg. the function allows a player to request support from the Ship escort to attack a target identified by the Plane escort with its Tomahawk missiles. eg. the function allows a player to request support from other Planes escorting to bomb the unit with illumination missiles or bombs, so that the main plane escort can attack the area.

ROE ...:

 

Sets the Rules of Engagement (ROE) of the escort group when in flight.

"Hold Fire": The escort group will hold fire.

"Return Fire": The escort group will return fire.

"Open Fire": The escort group will open fire on designated targets.

"Weapon Free": The escort group will engage with any target.

 

Evasion ...:

Will define the evasion techniques that the escort group will perform during flight or combat.

"Fight until death": The escort group will have no reaction to threats.

"Use flares, chaff and jammers": The escort group will use passive defense using flares and jammers. No evasive manoeuvres are executed.

"Evade enemy fire": The rescort group will evade enemy fire before firing.

"Go below radar and evade fire": The escort group will perform evasive vertical manoeuvres.

 

Resume Mission ...:

Escort groups can have their own mission. This menu item will allow the escort group to resume their Mission from a given waypoint.

 

Note that this is really fantastic, as you now have the dynamic of taking control of the escort groups, and allowing them to resume their path or mission.

 

Kind regards, Sven

Edited May 27, 2017 by FlightControl

[funkyfranky]

The escort class is really great feature. Thanks FC :thumbup:

 

I have a few questions/comments:

 

1.) Regarding the assisted attack option, which is very handy for the mission I'm building.

Like in the example, I have an artillery group which can assist the attack. It starts to fire at the targets but I can't make it stop again. If I set ROE to weapon hold, it has no effect.

 

2.) Could it be that the resume waypoint action is not working atm? At least I don't get any waypoints shown, when I activate it.

 

3.) In my mission, I have set up quite a few escorts. This means that the menu gets pretty crowded. Maybe it would be a good idea to have an separate submenu for all defined escorts?

 

Thanks again for all your lovely work!

[FlightControl]

The escort class is really great feature. Thanks FC :thumbup:

 

Thank YOU for looking at the function and your feedback!

 

I have a few questions/comments:

 

 

1.) Regarding the assisted attack option, which is very handy for the mission I'm building.

Like in the example, I have an artillery group which can assist the attack. It starts to fire at the targets but I can't make it stop again. If I set ROE to weapon hold, it has no effect.

 

The assisted attack works with a task. I might want to add a "cancel attack" option to the menu, which would clear the task...

 

2.) Could it be that the resume waypoint action is not working atm? At least I don't get any waypoints shown, when I activate it.

 

Yeah, that function of the ESCORT needs a revision. Thanks for telling. Can you do an issue log on the github site please? It used to work though, but haven't really tested this anymore.

 

3.) In my mission, I have set up quite a few escorts. This means that the menu gets pretty crowded. Maybe it would be a good idea to have an separate submenu for all defined escorts?

 

You mean? You have setup a lot of ESCORT classes?

 

Another feature that is fun, is that the ESCORT flies ahead, and leads the attack, and you control the attack from the helicopter. So, if two AH-64D are flying ahead as an escort, following its path. And you can let them scan the area, and attack detected targets. Once clear, you can move on with your MI-8...