No AWACS in multiplayer when not in the same flight as host?
-
I’ve noticed the following issue when flying BMS 4.33.5 in multiplayer. Whenever I am NOT in the same flight as the host, I do not have AWACS? (AWACS menu only shows the “Call rescue chopper” option, everything else is greyed out).
We mainly fly with 3 people and the problem happens when we are fragging flights during our campaign and we cannot get a 4-ship, so we frag 2 2-ships instead - though are part of the same package. UHF and VHF are set to common frequencies and we have no problems communicating in flight. Also data link between the different flight works fine. We always coordinate saving our DTCs as part of our briefing as well so that should be fine too I think?
More interestingly, my human wingman in our 2-ship doesn’t have this problem and always has AWACS. Not having AWACS is a bit of a pain as I either need to outsource the verification to my human wingman or just get up close and personal to ID the aircraft with the Mark I Eyeball.
Is there some kind of setting I need to be aware of?
-
I’ve noticed the following issue when flying BMS 4.33.5 in multiplayer. Whenever I am NOT in the same flight as the host, I do not have AWACS? (AWACS menu only shows the “Call rescue chopper” option, everything else is greyed out).
We mainly fly with 3 people and the problem happens when we are fragging flights during our campaign and we cannot get a 4-ship, so we frag 2 2-ships instead - though are part of the same package. UHF and VHF are set to common frequencies and we have no problems communicating in flight. Also data link between the different flight works fine. We always coordinate saving our DTCs as part of our briefing as well so that should be fine too I think?
More interestingly, my human wingman in our 2-ship doesn’t have this problem and always has AWACS. Not having AWACS is a bit of a pain as I either need to outsource the verification to my human wingman or just get up close and personal to ID the aircraft with the Mark I Eyeball.
Is there some kind of setting I need to be aware of?
Not a common problems in my sessions. I know you flew in Baba Yaga, you had this problem there? Not my case.
-
The launcher under Campaigns has a ‘awacs required’ box.
-
Not a common problems in my sessions. I know you flew in Baba Yaga, you had this problem there? Not my case.
No, the problem is not specific to theaters - I have the issue in different theaters.
-
I have had similar issues with more than one flight on KTO, it seemed to be hit or miss, but some points flying the same TE I would have or not have AWACS. We had one on station, and AWACS Required was checked. Same thing, Some members would have it, others would not, whether they were part of the same flight as the host or not. It was on a privately hosted server, I.E. another person, not a server. Since, I’ve turned off AWACS Required and that fixes it (Band Aid in my mind) though if there isn’t an AWACS on station, its kind of cheat-y.
-
This post is deleted! -
This post is deleted! -
A “Q” menu that doesn’t represent an AWACS present has nothing to do with radios. Even if you have both radios off you’ll still see a populated “Q” menu. I checked in a TE and >1000nm apart you still get a valid “Q” menu so range is no factor.
The only reason for not having a populated “Q” menu is if it thinks there’s no AWACS doing the EW task. So there’s some issue where the two clients disagree. Host thinks there is and client thinks there’s not. Maybe host has option AWACS available even when not present and client doesn’t. The reverse should be checked: same mission but swap who is host and who is client.
-
This post is deleted! -
Also, might be worth checking you have set g_bServerHostAll 1.