AWACS not responding when I need it most!
-
-
To complete the effect, decreasingly audible/intelligable radio voice modeling is needed to reflect increasingly distant/weak radio signals.
Since there is code in that that tries to do this for AI radio traffic already, just not well, I’d say rather that better effects processing is required. I suppose in theory we could lift the signal processing code from the IVC client that does the same job and apply it to the AI. I haven’t seen much feedback about how IVC does this effect though so I’m not sure if that would be considered an improvement or not; the few opinions I have seen seem to vary.
-
Hi guys! I want to restart this thread because I disagree with the answer. I have also had this problem when bogeys are approaching my package and where I have been getting the AWACS calling out nonstop targets to other planes in my package but when I lock up a bogey and call out declare with Q-2, the AWACS just continues to call out the targets to the other planes and seems to ignore me. But then about 1-3 minutes after I make the request, suddenly the AWACS responds and says something like Cowboy 11 contact confirmed hostile, ID’ed as MIG 29. By this time the bogey is behind me shooting a heater in my tail! It is obvious that the AWACS are hearing me no matter how far I am away from them, they are just too busy to give me a response until it is too late. This has never happened to me in earlier versions and I don’t think that being out of range is a reasonable explanation under the circumstances. Anybody else notice this kind of behavior? It is getting quite annoying and I have had to start just shooting at whoever appears to be an enemy because I no longer get any help from AWACS. I would appreciate any help!!
Bizerker
-
…. But then about 1-3 minutes after I make the request, suddenly the AWACS responds and says something like Cowboy 11 contact confirmed hostile, ID’ed as MIG 29. By this time the bogey is behind me shooting a heater in my tail! It is obvious that the AWACS are hearing me no matter how far I am away from them, they are just too busy to give me a response until it is too late. …
Bizerker
This can happen (although I can’t say I’ve had to wait 3 minutes … ). I would suggest switching to an alternate Uniform channel. A channel designated for a flight or a package. If you’re on a guard or tower channel, the number of AI calls can be … distracting.
-
(using standard presets)
Advised is:
VHF on CH1 to 5 (For Intra-FLight)
UHF on CH6 to 10 (For AWACS Tactical)Forget about any other if you want to optimized your chance of responses on tactical comm’s.
Before push, you might monitor 13 or 14 to listen AWACS broadcasting. Use it as a sort of “Check In” freq, then after check in and just before Push, switch to 6 to 10 (any of them as they are the same) for “Tactical” freq.
-
Thanks Dee-Jay! I’ll give it a try!
Bizerker
-
Add TGP, and mind your RWR. Also hard locking and listening for buddy spike can be helpful as well. You should be able to ID target with picture on TGP display once they are 20-25 miles out.
Try another freq. with less chatter can also be helpful. AWACS broadcasts on more than one channel.
Of course if you get launched on by ARH missile, you can be sure that the guy you have locked up isn’t your friend!
HTH
-
Hi guys! I want to restart this thread because I disagree with the answer. I have also had this problem when bogeys are approaching my package and where I have been getting the AWACS calling out nonstop targets to other planes in my package but when I lock up a bogey and call out declare with Q-2, the AWACS just continues to call out the targets to the other planes and seems to ignore me. But then about 1-3 minutes after I make the request, suddenly the AWACS responds and says something like Cowboy 11 contact confirmed hostile, ID’ed as MIG 29. By this time the bogey is behind me shooting a heater in my tail! It is obvious that the AWACS are hearing me no matter how far I am away from them, they are just too busy to give me a response until it is too late. This has never happened to me in earlier versions and I don’t think that being out of range is a reasonable explanation under the circumstances. Anybody else notice this kind of behavior? It is getting quite annoying and I have had to start just shooting at whoever appears to be an enemy because I no longer get any help from AWACS. I would appreciate any help!!
Bizerker
AWACS always takes about 3 mins to reply? Have you tried using the wingmen and NCTR to ID the bogeys.
Definitely recommend you start ID of bogeys when they are much further out than 3 mins (about 40 miles assuming 800 kt closure).F1
-
Wingmen auto ID is cheating, and only works with AI anyway. NCTR only works for high aspect.
3 minutes is an eternity, but the reason for the delay is well established and will hopefully be fixed soon. In the meantime, use of TGP, NCTR, and RWR correlation should be a good solution - that or change frequency as recommended above.
-
Thanks, guys! I haven’t tried the TGP for A-A and I definitely need to give it a try! I don’t know if it actually takes 3 minutes for the AWACS to respond but it always SEEMS that long when you really need them! The RWR didn’t identify the MIG-29’s until they were behind me so that wasn’t much help. Maybe they had their radar turned off. I will try the TGP and the different frequency when I get back in town and let you know how it goes. Thanks so much for all your help!
Bizerker
-
What is NCTR?
-
What is NCTR?
Non Cooperative Target Recognition.
In the F16 it used the radar return to identify aircraft type. Shows up in the top center of the FCR when available.
-