Comms not working in VR

[moggel]

Haven't done all that much in VR yet so I thought I'd try a campaign. I picked the P51-D "Charnwood" campaign is I thought most other campaigns would be too much for my potato PC (my new one should arrive "soon" but until then ...). In the campaign I have not been able to use comms at all. VAICOM PRO doesn't pick up _any_ commands. I then tried without Voice Attack and just rely on the plain comms menu by pressing my binding to present the menu does nothing.

Actually, very often as the mission starts, I get the comms menu to appear but only a few times. After that (usually after takeoff) pressing my HOTAS keybinding for comms menu yields no result whatsoever.

I can still press WIN+R to have my flight attack the primary (a pain as I need to lift the headset to find the key combo) but no other comms option seems to be available to me.

Am I missing something here or does stuff work differently when in VR? Or is it just my machine that can't cope?

[dburne]

Not sure what might be going on with ya there, I can only say I use Voice Attack with Vaicom Pro and it works fine for me flying in VR.

[Tom Kazansky]

With easy comms set to OFF the comms menu key does work on the ground but not in the air. When airborne you have to use the keybinds of comm switch(es) of the aircraft. There are several threads discussing this and some people find this is not a problem. Threads like yours prove the opposite.

[Tshark]

Make sure Voice Attack and Windows are using your VR microphone.  On my system there are two microphone settings.  One for my normal system and one for the VR headset.

[moggel]

22 hours ago, Tshark said:

Make sure Voice Attack and Windows are using your VR microphone.  On my system there are two microphone settings.  One for my normal system and one for the VR headset.

Thank, I did that and it is the VR mike. 

[moggel]

Update: The reason I didn't get the COMMS menu was two fold: First off I had mistakenly bound a HOTAS button not to the PTT item in the configuration but to the line below it. Just a silly mistake. The other reason (when I corrected that) was that i was running VAICOM PRO at the same time (was trying to fix two problems), which is configured to suppress the COMMS menu. Duh!

My remaining problem is that VAICOM does recognize what I am saying but the log says there's no recicpient. I interpret that as meaning I've pushed the wrong channel (in the P-51D). To get more control over testing I created a simple mission with just one wingman and made sure channel A is the one both me and my wingman is sharing. Still, I get this error. Any ideas what I might be missing?