Uploaded a player awacs script into the server scripts folder. (player_awacs_v1.lua)
Script is standalone, does not require any other scripts eg (MIST)
Function:
The mission designer can designate any aircraft group as an AWACS (group name with "AWACS" in the name)
The AWACS unit when on station will have all air contacts with LOS within 70 NM drawn on it's F10 map, updated either every sec or every 5 sec based on user preference (defaults to 1 sec)
Whoever is the AWACS should relay via voice comms to coordinate the air battle.
Best used with 2 player AC, 1 to fly and the other be the battle manager/AWAC operator.

Known issues:
Slight stutter on marker draw in high threat environments (tested up to 28 concurrent threat AC), most evident using the 1 sec update, less so with 5 sec.
Game freeze on disconnect.

Planned improvements:
Reduce stutter with staggered draw commands.
AI AWACS/EWR downlink

Awesome! Have to think about how to best implement it, but that's pretty damn cool.

Uploaded version 2
Features:
Fixed the stutter issue, tested up to 128 threat ac without major problems. Thanks Roy and Cook for the help
Increased minimum scan rate to 5 sec.

Known Issues:
Game freeze on disconnect still an issue. I think it is DCS clean up function not liking the number of marks, don't know how to fix

That's a crash when the AWACS script-enabled client disconnects or just anyone who happens to be present while the marks are up?

And am I assuming correctly that's a freeze-to-crash, or are you just talking about a healthy lag spike?

Unfortunately the issues will manifest for all parties present when the script is employed. The game will freeze for the disconnecting client, leading to a crash. My guess is the game is running a clean up function on the marks and the longer the script is run the longer the clean up function takes to complete, effectively freezing the game. However this issue will only affect the client on disconnect and to only the disconnecting client. The server and other clients won't experience any detrimental effects. That being said, the issue will cause the server to freeze on mission completion/change.

Ahh okay. So still an issue, but something we can work with as long as we have people on to RDP in for mission changes.

There is a possibility that the server given enough time will unfreeze by itself once the cleanup function completes, I just haven't been patient enough to wait to see if it does come back