VoiceAttack not following default input devices changes?

[Tenebrous]

Just setting up some new VA profiles to work with SteamVR & the HTC Vive.

However, one thing that happens when you enable SteamVR is that the default input device changes, and it doesn't seem as though VA detects this and remains listening on the old device.

This is a slight pain!

e.g. I can say a command "Start VR", and SteamVR starts and the Vive initialises etc... but then I can't issue further commands using the mic on the Vive.

Any suggestions?

Tene

[Pfeil]

Perhaps you could have VoiceAttack restart itself? I find the speech recognition gets a little spotty after a while(my mic picks up a lot of background noise, which probably doesn't help), so I use a command to call a .bat file which restarts VoiceAttack for me:

Command "Restart VoiceAttack"
Run application 'C:\Program Files\VoiceAttackBeta\Apps\RestartVA.bat' (hidden)

"RestartVA.bat"
taskkill /im voiceattack.exe
PING -n 2 127.0.0.1>nul
start "" "C:\Program Files\VoiceAttackBeta\VoiceAttack.exe"

The ping is in there to provide a delay to make sure VoiceAttack is shut down before it attempts to start again. Bit ghetto, but it seems there's no "pause" function otherwise.


Starting the .bat as hidden will prevent it from "stealing focus", however the VoiceAttack window itself may still do so. I don't use SteamVR, so I can't say what will happen if it loses focus.

[Tenebrous]

SteamVR wouldn't care in that case.

However the problem here is that I've started a bunch of log-monitoring event loops and stuff... in the middle of which the default audio device changes.

So it's do-able but quite the pain!