AI AWACS handling - A DCS tactic

[Dojo]

With respect to AWACS calls, I've been using the following method I wanted to present for comment and adoption. If someone has a better method I'm all ears. Of course, this strictly applies to the scenarios with AI only AWACS. A human would be proactive, rendering this unnecessary.

I've begun to brief explicit instruction to my wingman not to make AWACS calls. As lead, I will manage all calls, with a rough frequency of 2 mins when "relatively clear", and ~30 seconds when proximity/situation warrants it. I've also begun to brief tactics, including selective jettison for engagements where reasonable (e.g., if you're engaged defensive, just emergency jettison, but if manageable, select jet only a preflight selection of items... more on this later).

The 3 exceptions to my exclusive lead AWACS calls is pre-briefed as follows:

1) I declare heads down.
2) I brief any shooter/non-shooter attack, and 2 calls "Ready".
3) I bail/die/disconnect

In those 3 circumstances, Wing should assume the AWACS calls immediately. This has been effective for me, and has cleaned up comms considerably.

Thoughts?

[Snoopy]

Looks like a good process to me, wingman shouldn't make any radio calls unless directed to anyways.

Watching the three twitch streams Tuesday I was shocked the AI AWACS was able to "kinda" keep up with all the requests.

I also had lotatc up for some of the flight, I wouldn't know what I was going but yeah a human controller would be able to share the information a lot quicker and to the specific flight potentially affected.

[Trigger]

I'd see comms as a flight lead responsibility unless otherwise directed by lead. Only situations I can see for wingman calling AWACS is in case of lead having comm out or lead ejecting/crashing. Even when 2 is shooter, lead is still responsible for the conduct of flight hence why lead always makes the fighter-fighter briefs.

My thoughts for what they are worth...