VoiceBot RSS: Windows wide keyboard block https://www.voicebot.net/Discussions/RSS/?TopicID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d VoiceBot RSS: Windows wide keyboard block Wed, 22 Apr 2026 20:55:43 GMT en hourly 1 https://www.voicebot.net/Discussions/RSS/?TopicID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d RE: Windows wide keyboard block https://www.voicebot.net/Discussions/View/windows-wide-keyboard-block/?ID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d#4 Tue, 08 Aug 2017 19:49:08 GMT Binary Fortress Software https://www.voicebot.net/Discussions/View/windows-wide-keyboard-block/?ID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d#4 VoiceBot No worries, glad to hear it was an easy fix! ]]> RE: Windows wide keyboard block https://www.voicebot.net/Discussions/View/windows-wide-keyboard-block/?ID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d#3 Fri, 04 Aug 2017 20:03:19 GMT Binary Fortress Software https://www.voicebot.net/Discussions/View/windows-wide-keyboard-block/?ID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d#3 VoiceBot
Quote:
It sounds like the Ctrl key is getting stuck down. Are your macros setup to send Ctrl + num as a "Press and Release Key" action, or just "Press Key?"


Thank you for that response, that was indeed the wrong setting I chose. Press instead of Press and Release.
I knew it was something stupid like that somehow :P

Cheers! ]]> RE: Windows wide keyboard block https://www.voicebot.net/Discussions/View/windows-wide-keyboard-block/?ID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d#2 Fri, 04 Aug 2017 14:33:35 GMT Binary Fortress Software https://www.voicebot.net/Discussions/View/windows-wide-keyboard-block/?ID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d#2 VoiceBot It sounds like the Ctrl key is getting stuck down. Are your macros setup to send Ctrl + num as a "Press and Release Key" action, or just "Press Key?" ]]> Windows wide keyboard block https://www.voicebot.net/Discussions/View/windows-wide-keyboard-block/?ID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d Thu, 03 Aug 2017 19:39:53 GMT Binary Fortress Software https://www.voicebot.net/Discussions/View/windows-wide-keyboard-block/?ID=bfb6e187-8ea4-44d4-a2bc-a03644dcca2d VoiceBot Hey there!

Now I know the title is not all that precise but I didn´t know how else to call it.
So a colleague at work suggested using Voicebot and surely enough I got home and installed it, primarily to use it for World of Warcraft.

I set it up for 2 voice commands specifically for that game when it´s running.

Now this is what happens. I start the game and I can play just fine. Until I make a sound, it could be a cough, sneeze or whatever and it sometimes recognizes that as the word "fuck" (one of the commands) or "ouch" (the second one).
Now that uses CTRL+1 or CTRL+3. Once one of those have been executed, things get weird but only as long Voicebot is active. If I shutdown the game doesn´t matter, Voicebot has to be deactivated using the Taskmanager to get rid of the problem.

The problem is, I can still use WASD for movement in the game, I can type enter to start chatting but at the same time, I cannot type any letters at all. Even WASD are not being recognized, yet I can walk using those while not in chat. (all ingame still)
At the same time, if I click escape ingame (or anywhere) it recognizes the Windows button and opens up my start menu instead - until I close down Voicebot completely.

Now my first thought is: I´m doing something wrong, maybe a shitty setting on my end? But what, where?

I´m using Windows 10.

Kind regards,
Chrotesque ]]>