Elite Dangerous Half of VoiceAttack / Verity Commands work, and Half Don't. HELP!

[Tom Birkinbine]

Hello everyone,

I've been with Elite Dangerous for over a year with the oculus rift.  I'm a pretty savy guy with computers as long as the direction is there.  My issues are that every command I say gives me the correct response back from Verity and is recognized BUT only about half of the responses do anything in game.  

1 - Half of my commands work.  Boost works, cargo scoop works, deploy and retract hardpoints, balance power works just fine.

2 - Open Galaxy Map, Open System Map, lower landing gear etc only make the response from Verity back to me but they do nothing in game.

3 - I've googled this and am trying everything.  I can't seem to find the option ANYWHERE in Voice Attack for "Key input method" as some people are saying to change that from standard to Dirext x for games.  WHERE IS IT?

4 - Why are only some working and others not??? but everything gives me a verity response back so it is recognized.

Very frustrating.  Happy to have some help please.

[Tom Birkinbine]

Also, I do have the drop down in Voice Attack set to ELITE DANGEROUS and not active window.  

[Gary]

Hi, Tom.

If *half* of the commands work, you are probably running a profile that is pressing keys that are different in your configuration than what comes with Verity.  You will need to go into each command that is not working and look at what it is doing to make sure it is pressing the right keys for you.

Gary

[Tom Birkinbine]

Thanks Gary.  Very cool of you for the prompt response man.  Says alot about you.

Ok back to the issue.  But I never changed any keybind for open galaxy map or open system map.  Opening those maps is simply something I always did my looking at the panel and using the built in commands.  So, I can't figure it out.  Do I really need to get in there and re-write the script ?   I am using x52 and its software but, again, I never changed anything special for simply opening the maps.  Hmmmmm.  Wonder if I could somehow have you remotely look at my comp and assist.  I'm a bit lost.  

Also, can you please tell me how to find where the "key input method" thing is?

Thanks and talk soon,

[Gary]

Hi, Tom.

You'll need to go into each malfunctioning command and see what keys are being pressed.  There will be an action in the list that indicates what key is pressed.  Just double-click on the action and you can edit what the key is.

Gary

[Tom Birkinbine]

Will do.  

Additionally, can you please help me with this question I keep asking as well -

   "" I can't seem to find the option ANYWHERE in Voice Attack for "Key input method" as some people are saying to change that from standard to Dirext x for games.  WHERE IS IT?  """

[Chris Milner]

There is a .binds file that needs to be copied over from the profiles directory where the voice pack is installed that sets up the keybindings in Elite Dangerous. This is because Elite Dangerous does *not* bind everything needed as standard, so the voice pack guys made the .binds file so that it was (even more bizzarely, in Elite Dangerous, it has *as standard* different keys set for the same action depending on which default setup you start with. This isn't with ALL commands, but enough to make it annoying).

[Chris Milner]

When you set a keypress action in voice attack, you have the option to set it as "standard" or as "DirectX". THis is NOT the "shortcut" button that can be set ("When I press a key" on the edit command window), but in the actual *command* itself (where the actual "code" of the command is)

[Tom B]

Ok fellas, I have most of this working now.  Almost all commands are working except when I say "jump drive" it reads in Voice attack "job drive".  No matter how I try and pronounce it.  Any tips on how to fix this so it picks it up correctly?  I already did 2 runs through the windows speech recognition learning software so ....any thoughts?

Thanks!  Almost all working well now Gary : 

[Chris Milner]

I would suggest running through the training a couple more times. Even now, if I get a command that doesn't seem to work properly on a regular basis, I will just retune the training later on. If it is *consistently* picking up the wrong phrase, then I would just add that "incorrect" pronounciation as a "correct" command.

[Gary]

Thanks, Chris!

There's also a way to train individual words with the speech engine.  VA does not have that built in, as it's already in the one built into Windows:

http://windows.microsoft.com/en-us/windows7/add-or-edit-words-in-the-speech-dictionary

Gary