Suddenly weird VAICOM/Voiceattack issues

[Jayhawk1971]

All of a sudden (I noticed it after Monday's update, but haven't had used VAICOM for a couple of months), I got a number of issues that I haven't experienced ever before. I'm at a loss where to even look for the problem.

It began with VAICOM suddenly not connecting to DCS. I normally delete the VAICOM entry from the Export.lua after every DCS patch. Usually it get's rewritten after starting VAICOM and then DCS. Turns out, not this time. So I manually added the entry, which at least connected both apps.

Next, VAICOM diag told me that my Voice Attack version was outdated. So I downloaded and installed the latest version. 

I also manually re-entered (=clicked through the respective folders) the installation path to the DCS exe again (bin-mt), just in case something got messed up with the DCS's switch to MT only.

I have "REL HOT" under PTT disabled, but for some reason, as soon as I start a mission in the Tomcat, sometimes it's on (light is on). 

Anyway, after all those above steps, I finally got voice commands to be recognized again, only for the microphone on my VR headset to suddenly behave weirdly.

I noticed that my commands were suddenly (in mission) no longer acknowledged (no beep). Checking the VA window I saw that the microphone bar was all the way to the right (with the "too loud" icon showing). Which is wasn't at the start of the mission.

Then, after opening Voice Attack settings to see if I can do something about it, the mic was no longer "active" (no sound bar, with or without PTT pressed). Also not working in Windows all of a sudden. VR headset mic was recognized, available, and Windows diagnostics couldn't find any problem, but no sound was recognized (no volume bar, nothing on test recording). Unplugging the VR headset and plugging it in again helped. Everything back to normal with both Windows and Voice Attack (without DCS running). I gave up and went to bed.

Does anyone have any idea what the hell might be going on?! 

Next step would be to test with another microphone. But before I go full diagnostics mode, maybe someone already has encountered something similar and could save me a lot of work and frustration. I'd rather fly than fiddle around with hardware and software.  

Edited October 2, 2024 by Jayhawk1971

[MAXsenna]

Didn't see that one. Was it VAICOM or VoiceAttack that needed the update?
Latest version of all three parts works for me. No issues.
I have made a VoiceAttack command to turn REL/HOT on and off. VAICOM has all these incredible nifty features. Need it because I always forgot to turn it off in the Tomcat.
Sometimes Windows messes with my mic setup, and VoiceAttack and or Windows Speech loose it. And then I have to select it again in Speech. All I can think of now.

Sent from my SM-A536B using Tapatalk

[Jayhawk1971]

vor 3 Stunden schrieb MAXsenna:

Didn't see that one. Was it VAICOM or VoiceAttack that needed the update?
Latest version of all three parts works for me. No issues.
I have made a VoiceAttack command to turn REL/HOT on and off. VAICOM has all these incredible nifty features. Need it because I always forgot to turn it off in the Tomcat.
Sometimes Windows messes with my mic setup, and VoiceAttack and or Windows Speech loose it. And then I have to select it again in Speech. All I can think of now.

Sent from my SM-A536B using Tapatalk
 

It was a VoiceAttack update. I do have this nagging thought in the back of my mind that somewhere, some time ago, I read that one should not update VoiceAttack when using VAICOM Pro, but that could very well be either outdated info, or my memory playing tricks on me.

Other times when I lose the mic (happens from time to time), using the Windows 10 troubleshooting button (Windows settings-> system -> sound -> microphone) fixes the problem. This time it didn't even recognize that there was a problem. 

 

Edited October 2, 2024 by Jayhawk1971

[MAXsenna]

It was a VoiceAttack update. I do have this nagging thought in the back of my mind that somewhere, some time ago, I read that one should not update VoiceAttack when using VAICOM Pro, but that could very well be either outdated info, or my memory playing tricks on me.
Other times when I lose the mic (happens from time to time), using the Windows 10 troubleshooting button (Windows settings-> system -> sound -> microphone) fixes the problem. This time it didn't even recognize that there was a problem. 
 

I have never had issues VAICOM with VoiceAttack being updated. So that would be strange.
So, right now. VoiceAttack doesn't have a mic? Then I would double check what mic Speech is using.

Sent from my SM-A536B using Tapatalk

[Jayhawk1971]

vor 20 Minuten schrieb MAXsenna:

I have never had issues VAICOM with VoiceAttack being updated. So that would be strange.
So, right now. VoiceAttack doesn't have a mic? Then I would double check what mic Speech is using.

Sent from my SM-A536B using Tapatalk
 

It does have a mic at the start of the mission, but after 10 minutes or so, it suddenly loses the mic. A restart usually fixes it, until it happens again. As I said, weird.

I hope it's not my VR headset.....

[Jayhawk1971]

@MAXsenna

I got the issue resolved! It was actually two separate issues turning up at once:

One was that I had the folders mixed up after the merging of openbeta and stable, and the path to my DCS install was set to bin-mt instead of the root folder. Fixed that, now everything works again as it should.

Second was that my Vive Pro headset doesn't work well with USB 3.0, so using a USB 2 port fixed it.

[MAXsenna]

@MAXsenna
I got the issue resolved! It was actually two separate issues turning up at once:
One was that I had the folders mixed up after the merging of openbeta and stable, and the path to my DCS install was set to bin-mt instead of the root folder. Fixed that, now everything works again as it should.
Second was that my Vive Pro headset doesn't work well with USB 3.0, so using a USB 2 port fixed it.

Excellent!

Sent from my SM-A536B using Tapatalk