VoiceAttack makes some of my keys not press or press the wrong key.

[Thomas Harvey]

When I run VoiceAttack for Elite: Dangerous some of my keys press the wrong thing or have no response. For example if I have VoiceAttack running and want to do  a google search then when I press E, U will press down. L and X won't respond at all and other keys don't work either. How can I fix this? I'm using the EliteDangerous voice pack profile. Can I make VoiceAttack only listen/work when I am tabbed in to Elite? Thanks

[Gary]

I keep seeing posts where Frontier has changed the key bindings after some release.  My, 'E', 'U', 'L' and 'X' seem to be doing alright in both modes.

Also, see the section on the VoiceAttack website regarding, 'Commands are recognized, but, nothing is happening in my game' on the How-to page: http://www.voiceattack.com/howto.aspx

Gary

[Brian Hillard]

I had the same problem.

While VA was running, certain keys on the keyboard would not work at all.

As my granddaughter found out when trying to message someone on Facebook.

And then last night I noticed it too.

I switched to another profile (I too bought the Voice Pack for ED), and the key in question started working again.

But oddly enough, I switched backed to the ED Voice Pack profile and the key was still working?

(I wasn't in in-game at the time).

[Brian Hillard]

I think I found the reason for that now. Or at least in my case.

The Voice Pack for ED has some of the keys configured as hotkeys in Voice Attack.

So for instance, if you press F10 to take a screenshot. Voice Attack will play a sound based on that event,

In that case any keys that are bound to certain functions in VA will not work outside of the game.

I have now tweaked the Go to Sleep command to not only stop VA listening, but to switch off keyboard shortcuts too.

[maarten de bruin]

I always click the keyboard icon to the right of the 'Send commands to' text in VA. That stops VA from listening to and intercepting the input from the keyboard. I do this because the profile I bought for Elite: Dangerous has a lot of commands that also have a keyboard shortcut and getting rid of all those keyboard shortcuts would take way too long. I'd appreciate it though, if you could have VA remember which input to listen to and which input to ignore, possibly somewhere in the settings because I can also understand that a one-time toggle in the program itself can be very handy for people.

[Luca D]

If you wish, you can have VA starts always with hotkeys turned off... just add "-shortcutsoff" to you command line

[Brian Hillard]

Agreed.

I have the Voice Pack too.

The only downside, is if you are typing on the keyboard outside of the game, or text chatting in-game, then all kinds of issues can occur.

The amount of times I have forgot to disable the keyboard shortcuts in VA is unreal.

And the downside is, if you go back to VA to tweak a command, occasionally the keyboard shortcuts switches on again.

Even searching the galactic map is a pain with keyboard shortcuts enabled.

I bet the guys that created the Voice Pack didn’t think of that unfortunately.

Great pack though. A must for VA and Elite Dangerous.

Sent from Windows Mail

--

---
You received this message because you are subscribed to a topic in the Google Groups "VoiceAttack" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/voiceattack/IlEczDokvlw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to voiceattack...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[alberto Molleja rodrigez]

darme de baja

---

From: brian.b...@gmail.com
To: voice...@googlegroups.com
Subject: Re: VoiceAttack makes some of my keys not press or press the wrong key.
Date: Fri, 9 Jan 2015 13:52:56 +0000

You received this message because you are subscribed to the Google Groups "VoiceAttack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voiceattack...@googlegroups.com.

[Brian Hillard]

That is extremely useful thanks.

I totally overlooked that command line :)

On Sunday, 14 December 2014 21:29:24 UTC, Thomas Harvey wrote: