4.33 AWACS/GCI Comms clutter.

[sir_quacksalot]

I didn’t see if anyone else has posted about this but it is certainly something that is driving me nuts.

With the update to 4.33, I am sure that the way AWACS AI works is very different. However, the Radio chatter on UHF 13 (307.3) is ridiculous now. Not only is the information that it is putting out not useful, but it is extremely distracting to us as pilots. It pretty much kills my SA. Also, when I do send a request for info to AWACS it doesn’t seem like it replies as all it sends is a constant stream of updates about radar contacts somewhere around the theater.

This seems like a pretty obvious issue but hopefully someone can shed light on it or that the AWACS AI is being addressed in some future update coming soon that will reduce the amount of chatter we are getting on the primary frequency. Not being able to get GCI to targets very much reduces our ability to find and attack air threats.

[Sting]

Yes it is a known issue. The work around is to use the radios. If you are on channel 13 you are gonna get hammered. These days I usually hangout on VHF 1 and UHF 6 (Package), only going to 13 if I get bored.

In the UI I would recommend changing the F1 channel from 307.300. Otherwise briefing is painful.

[Dee-Jay]

Use of CH13 i flight has never been useful nor realistic.

[Blu3wolf]

Im seriously thinking about setting our wing default to take this into account. I am thinking of setting the UI default UHF channel, and the ‘AWACS/COBRA’ channel, to both something other than 307.300 because of the clutter.

Is there any chance an update might deliver the ability to filter the type of radio calls you hear in the UI? And possibly 4.34 can dynamically assign radio frequencies to operating areas, so that each area gets its own ABM and control frequency.

[Red Dog]

Yeah we agree it’s unbearable. We’re trying to find ways to overcome the chatter….