FEATURE: CAS / BAI

[132ndNeck]

Will it be possible to add a script that lauches RW from FARP's to support RED with CAS/BAI.

FARP's in the following location:

FARP JIROFT (RUS) FARP JENAH (IRAN).zip (Unzip and put in static templates)

In addition to RW from FARP's, also FW support from Shiraz and/or Kerman with A-G aircraft

Will be needing some randomization:

• 20% chance for this to be triggered.
• Random from which FARP or Airfield
• From FARP JENAH use Iranian UH-1.
• From FARP JIROFT use Russian MI-28.
• From Shiraz or Kerman use A-G aircraft.
• Use a group with veichles or infantry to be used for spotting enemy targets to be able to trigger calling in CAS or BAI. (dedicated in the ME with a pre-fix. (Same as for Issue #7 )
• Will need to launch once, and NOT keep retasking for as long as the target detected exists.

Engagement will be somewhere along the FLOT: (Marked in yellow, but will vary from mission to mission)

What other information will be needed?

[thebgpikester]

I'm tempted to advise avoiding A2G_Dispatcher because it's a closed system beyond editing. It's easier and more flexible to just create a small system, but will vastly be affected on additional constraints. The reason I say that is that once you use it, something tends to come up in requirements for more granularity and then we get stuck.

Believe it or not, it's way easier to create 2-3 "template" groups with waypoints and roll a dice for which and when they go. The target area will remain the same, thus no magic really required. Easier to do something simple that works with a small set of randomisation parameters. Something will go wrong with detection with Dispatcher, it's overly complex and reliant on DCS.

If you have a specific place to go that changes or a specific unit in mind that is supposed to be a spotter, the group can simply travel to that unit's location and be released. Devil is in the detail.

What group are they going to? What happens if that group is dead? How many simultaneous attackers? Maximum and period of spawning

[132ndNeck]

Makes very much sense. I have edited the title to better reflect what I want us to achieve.

[132ndNeck]

What group are they going to? What happens if that group is dead? How many simultaneous attackers? Maximum and period of spawning

• The groups should be dedicate Fire Support Teams/Recon teams (that supports artilley and avation).
• If the group are dead, ideally the flight will get airborne, but return back to base, as they will not get comms with th unit.
• Should not be more than 1 such flight (with 2 AC either RW or FW) at a time.
• Should spawn 2-6 per 24 hours

I think the most important is to set it up so it happens 2-6 times per 24 hours. And limiting the effectiveness of the flights. For example limiting it to one attack (so they do not annhiliate the blue forces).

The intention is to create activity, in a dynamic / "random" way so that AWACS, JTAC's, RW and FW can encounter activity during missions.

[132ndNeck]

Fire support teams , and using this: https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Functional.Detection.html

[thebgpikester]

OK seems much more moderate than I expected. Sounds OK.