Flight calling wrong AWACS callsign
-
I am not a regular on the forums, so apologies if I am posting on the wrong topic.
I am currently running a campaign mission where my originally scheduled AWACS(Chalice 3) has aborted. I was able to get a new AWACS flight/package (Dragnet 5) in the air and I hear them talking on their designated frequency. The problem is, my flight is calling the wrong callsign for the AWACS (Chalice 3) even though I changed my tactical channel to their frequency (Dragnet 5). Any help would be greatly appreciated!
I am on 4.35.
-
U1?
-
Yep, U1…lol, shoulda specified.
-
I mentioned something similar - before U1.
In my experience, AWACS names are mixed up quite often.
Unfortunately, I could not get any answers. -
Is it broken, or just superficially wrong (does Dragnet respond, even when addressed incorrectly)?
-
Is it broken, or just superficially wrong (does Dragnet respond, even when addressed incorrectly)?
I don’t want to ‘take over’ from the original poster here - just dropping my own observation.
I think it is rather superficial, as the AWACS callsign is not really important.
(At least for the “non te-builders”, to whom I definitely belong.)
Most of the time, you hit the “Q”-commands and get the information you need - no matter if it’s from Dragnet, Chalis, Sentry or whoever.Especially since (in BMS) AWACS, JSTARS and CAS-scouts all share the same UHF frequency/preset.
But many, many times (and regardless which theater), I first check the briefing, find the agencies I am going to deal with…
… and then, inflight, I find myself talking to completely different callsigns as expected. -
Need a repro case and proper bug report if confirmed.
-
Dee-Jay, I was able to get a work around going, by cancelling the package I was in and fragging a new one. Once the new package was created the new AWACS (Dragnet) was automatically assigned through the briefing and when I called out to it, there were no issues. I think its definitely a bug, but i am not sure what caused it. I might have a copy of the campaign save to recreate it. What do I need to do to make an “official” bug report? Just put it in the bug thread?
-
I don’t want to ‘take over’ from the original poster here - just dropping my own observation.
I think it is rather superficial, as the AWACS callsign is not really important.
(At least for the “non te-builders”, to whom I definitely belong.)
Most of the time, you hit the “Q”-commands and get the information you need - no matter if it’s from Dragnet, Chalis, Sentry or whoever.Especially since (in BMS) AWACS, JSTARS and CAS-scouts all share the same UHF frequency/preset.
But many, many times (and regardless which theater), I first check the briefing, find the agencies I am going to deal with…
… and then, inflight, I find myself talking to completely different callsigns as expected.Unfortunately in my instance, it seems to matter who we are calling. Chalice 3 was my assigned AWACS but for some reason they RTB’d and would not respond to my calls. Dragnet also would not respond to any of my calls, even though I had their new frequency punched in. Neither frequency gave me any replies, but I could talk to other members of my flight just fine.
-
Is it broken, or just superficially wrong (does Dragnet respond, even when addressed incorrectly)?
Dragnet does not respond whatsoever. I get on the new frequency, but I am only calling Chalice and Dragnet does not respond.
-
Are you sure you’re using your package UHF frequency, not the AWACS’? It looks like you’re switching to the AWACS UHF frequency, which is not supposed to happen at any point.
-
Are you sure you’re using your package UHF frequency, not the AWACS’? It looks like you’re switching to the AWACS UHF frequency, which is not supposed to happen at any point.
LorikEolmin, Thank you for that input. I think you maybe right. I don’t remember at this point but I think I did look for the UHF frequency and input it manually instead of just using channel 6. I will try and replicate tonight.
-
I think it is rather superficial, as the AWACS callsign is not really important.
(At least for the “non te-builders”, to whom I definitely belong.)
Most of the time, you hit the “Q”-commands and get the information you need - no matter if it’s from Dragnet, Chalis, Sentry or whoever.You certainly make a good point. Though, to be fair, it is a simulator going for realism, and for the non “non te-builders” and those who may be using voice control for immersive radio interactions, it can be immersion breaking to give/hear seemingly incorrect callsigns. I also use my briefing, getting info before mission and displayed on the Data Card in WDP on another monitor during flight - I have also had the experience of these being different from the briefing but never payed much mind to it as I felt I was perhaps using the simulator incorrectly or getting incorrect information of my own fault. If this is confirmed and a proper bug report can be provided with a repro case, I suppose we’d know for sure if it was the sim or some quirk of ATO, user error, or w/e.