[BUG] [Apache] Vaicom commands don't work in air unless F10 menu is displaying

[DarthZyll]

Describe the bug While on the ground, you can use the Vaicom commands to talk to ATC, JTAC, AWACS etc fine. However, once you are in the air, you will only get confirmation from the recipients if you have the F10 menu up (either initiated before or after issuing the voice command).

To Reproduce Easy Comms Off Vaicom - Disable Menus unchecked In an Apache - using PTT Norm mode issue the Vaicom test, communicating with ATC (e.g. Request Hover). It will work fine because you are on the ground next go into a hover, and then try to communicate with ATC (e.g. Inbound). ATC will only acknowledge you if you first toggled the F10 menu on (call radio menu keybind) Because its buggy, you may need to initiate the call radio menu multiple times before it actually appears

Expected behavior Regardless of whether you are in the air or on the ground, the radios should work without requiring the F10 menu to be displayed

Screenshots not applicable

Additional context running Vaicom Community download 2.8.0

[rcflyinghokie]

I believe this is the same case for all newer or 3rd party aircraft. Apache features were never refined after released and its on our radar. I get the same behavior for instance in the A4, but aircraft like the F14, F18, and Harrier have no issues with this behavior.

[DarthZyll]

Is Vaicom also the cause for the fact that you need to often times hit the call radio menu keybind over and over again to get the F10 menu to display?

[rcflyinghokie]

Is Vaicom also the cause for the fact that you need to often times hit the call radio menu keybind over and over again to get the F10 menu to display?

The radio menu is tied to the DCS binding, I always get mine up on the first press of a DCS bound PTT or the default radio menu keyboard binds.

[Raskil]

I've tried to reproduce the issue but it's not happening on my machine. I can talk to ATC when on ground and after I've taken of and left the airfield. What I am experiencing is the issue with the f10 spam to get the menu to display.

Can you elaborate more on this? Is it an MP mission or single player, is it happening with two human players in one Apache or not? Do you see it on different theatres or not? Do you have a dcs.log and VAICOM.log of a session withj the issue happening?

[DarthZyll]

I experience this in both MP and SP missions. I am in the bird alone, with no CPG. I have seen it in both my SP Marianas mission, as well as a MP Caucasus mission.

VAICOMPRO.log

dcs.log

[Stappers1]

I too have experienced this issue in SP flying f-16. It seems lots of the voice instructions are buffered , and not actioned , and then all of a sudden, they get spewed out? Just wondering if there has been any headway on this bug being resolved?

Kind regards,

mark

[Stappers1]

Here is the VA output- you can see all the buffered commands come through in one go!

[Stappers1]

I have reverted back to vaicom pro version 2.8.0 community version- and although a quick test- I do not see the buffwering issue0 which happens very wuickly and consistently in the latest 2.8.1.1 version

[Penecruz]

Fixed for next release