[BUG] "Suppress Auto" doesn't work for "Overhead" CV

[iantron]

Describe the bug
With "Aircraft Carrier Comms" and "Suppress Auto" selected, the CV responds to an overhead call when I am close enough, but I believe the audio call from my aircraft is successfully suppressed. If this is a bug, it is that the CV is still registering that I'm overhead when I haven't made the call, or that the audio is being suppressed but the actual message isn't.

To Reproduce
Follow the case 1 procedure in an F-14. Marking moms, see you at 10, then fly overhead CV (w/i like 3 nm). Listen for "[num] overhead angels [num]" from your pilot (you shouldn't hear it). Listen for the response from the carrier, you should hear it.

Expected behavior
The carrier should not respond until I have made an "overhead" call with Vaicom.

Screenshots
N/A

Additional context
N/A

[iantron]

Oh FWIW this is not a new bug. This has happened in VAICOM as long as I can remember.

[rcflyinghokie]

Have you tried replicating this with vaicom not running to confirm its not a DCS issue?

[iantron]

Now that I think about it, no. I'm not sure if that communication would normally be automatic. I'm assuming so, since I don't think VAICOM ever initiate carrier comms on its own. I don't think the F-14/supercarrier have an auto-comms option, but I'll have to confirm.

[iantron]

I don't have time to fly a case 1 right now, but I did confirm that there are no F-14 or Supercarrier options in the special options menu related to auto/suppress carrier comms.

Ok I just checked the Supercarrier manual. Here are some excerpts...

This has both pilot tx suppressed, but no automatic initiation of the marking mom's:

At 50 miles or closer, you should select ‘INBOUND’ from the ATC carrier radio menu. Upon doing so, the
following message is sent from you to the marshal controller:
“Marshal, [SIDE NUMBER] holding hands with [SIDE NUMBER], marking mom’s [BEARING FROM SHIP
TO PLAYER] for [RANGE], angels [ALTITUDE], [NUMBER IN FLIGHT], low state [REMAINING FUEL].”
The carrier MARSHAL will respond with:
“[SIDE NUMBER], mother’s weather is [VISIBILITY], [CLOUDS], altimeter [PRESSURE]. CASE I recovery
expected BRC is [HEADING OF CARRIER]. Report a see me at 10.”
You will automatically acknowledge with:
“[SIDE NUMBER].”

This has the pilot Tx voice suppressed, but the state is nonetheless triggered and the carrier responds. I think the side number response voice is suppressed, but I'm unsure if DCS registers it:

Once you are within 3 nm of carrier and enough interval exists between you and other landing aircraft, you will
automatically send:
“[TOWER], [SIDE NUMBER], overhead, angels [ALTITUDE], [NUMBER IN FLGHT], low state [REMAINING
FUEL].”
The tower responds with:
“[SIDE NUMBER], Tower, Roger. BRC is [CARRIER HEADING], your signal is Charlie.”
You will auto-respond with:
“[SIDE NUMBER].”

This sort of makes me wonder if the other side number responses are actually required or if they are still happening under the hood, but with just the voice suppressed. I am positive that the "see you at 10" call must be initiated by the player.

[iantron]

Ok I was able to confirm last night that in multiplayer my aircraft's "overhead" message is transmitted to other players despite the audio being suppressed locally. All players (including myself) hear the response from the carrier.

If it is possible to prevent the overhead message happening everywhere, that would probably be the preferred approach. If not, the local audio should not be suppressed by vaicom.

This also brings up the question of whether the pilot voice is played overtop of the SRS comms for other players on a multiplayer server. Hopefully not.

[clutchtomcat]

I can confirm this also happens in CASE III with just about everything after initial check-in: readback, fuel states, needles.

[rcflyinghokie]

Can you see if this is still an issue on the latest release?

[iantron]

Yes I can. It might be a few days before I get around to it. Feel free to ping me next week if you haven't heard by then.

…

On Sun, Jul 9, 2023 at 8:26 AM Ryan Callaway ***@***.***> wrote: Can you see if this is still an issue on the latest release? — Reply to this email directly, view it on GitHub <#23 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHANEFCVCUV53BVJNE5U4HDXPLERJANCNFSM6AAAAAARWN7X3Q> . You are receiving this because you authored the thread.Message ID: ***@***.***>