EWR units (F7 AWACS menu) callsigns bugged

[Volator]

Long-standing issue with the EWR units serving as GCI via the F7 "AWACS" menu, already reported in the ATC bug thread, but maybe worth its own thread:

A Control and Reporting Center (CRC) providing control for a Ground-Controlled Intercept (GCI) has a callsign of course. In DCS you could simulate this by placing an EWR unit and assigning a callsign in the EWR task in the ME. Unfortunately, there is this bug that whatever callsign you assign to the EWR unit in the ME ("Pinpoint", "Playboy", "Whiplash",...), in the simulation it always reverts to "Axeman". This would not be such an issue if you only had one single EWR unit in the simulation, but if you want to cover a country like Germany with radar coverage, you need more EWRs. Here the trouble begins, because

1. in the F7 AWACS menu only the unit type names are given (see screenshot), not the callsigns, so you don't know which unit is in your area to call to get the required information. It is NOT always the closest to the aircraft btw.; in my test mission it was #2 which was close enough to talk to me.
2. since the callsign always reverts back to "Axeman" despite being assigned a different one, you can't tell from the callsign to which agency you are currently talking to. I tried to compensate this by assigning different numbers (Axeman 1, Axeman 2, Axeman 3), but unfortunately the assigned numbers are also ignored in-game.

Screenshot and short test track attached.

This might only be a BluFor issue, since RedFor uses numerical callsigns. I haven't checked that yet.

1_CWG_022-20250609-100258.trk

[Volator]

Here's another track and the test mission I created both for BluFor and RedFor.

RedFor works as intended. The assigned numerical callsigns are visible in the F7 menu, so I know which station I have to call, and the dialogue includes these assigned numerical callsigns.

BluFor, see bug report above.

 

9_Georgia_EWR_test.miz EWR_test.trk

Edited Tuesday at 07:24 AM by Volator