Voice attack not working for some commands

[onejeremias]

Hello all,

 

I'm a brand new user to DCS, Voice Attack, and VR (HTC Vive) all at once. I'm working to set up a voice attack profile for use with the Vive due to not being able to see the keyboard while wearing the headset. I'm using the Training mission for the SU-25T takeoff-runway scenario for my testing.

 

The first few commands explained by the tutorial work fine (Electrical Power On, Navigation Lights, Close Canopy), but then when it says to turn on the left engine, the voice attack command fails to do anything.

 

I have tried both Windows Standard and DirectX mode, tried recording the keystrokes instead of selecting them using the command builder. I've also tried the option of sending the command directly to the program instead of using the active window. I am running Voice Attack as administrator, and I have confirmed that the command is recognized.

 

When setting up my voice attack for another game (Elite Dangerous) I learned that some commands required me to enter a hold value (~.3 seconds) for the keystroke in order for it to be recognized properly, so I tried this with DCS, but still no dice.

 

Has anyone else had trouble setting up Voice Attack manually like this? I've looked at the VIACOM option, but it seems overmuch for the way I'll be using the simulator.

 

Thanks in advance for any help.

[onejeremias]

Well I figured it out myself, in case anyone else has this problem. The how-to guide for Voice Attack (http://www.voiceattack.com/howto.aspx) provided some help, but basically I had to define each press and release of each key manually. In the case of a R-Alt / Home key combo, I had to do the following:

 

Key press R-Alt down

Pause 0.15 secs

Key press Home down

Pause 0.15 secs

Key release Home up

Pause 0.15 secs

Key release R-Alt up

 

In other cases, using the "Hold key down for xx.xx secs" worked, but for alt-key combos, the above was the only way to get it to take.

 

Hope this helps someone.

[Questlove]

yes. it helped!

[Chic]

I've encountered this on occasion. Most often I'll remap the key command with varied success.

Nice job on your workaround. Thanks for putting it out there.