Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

User Image
toddbbot
4 discussion posts
hi,

first off, i love this software coming from voiceattack. it's much more reliable at running macros. the only problem i have with it is whenever i run a macro with voicebot, the key that i'm pressing ceases its function until i press it again. for example, while i run away from an aoe in a game and i speak a voicebot command, my character would stop running until i let go of the directional button and press it again. is there any way to fix this issue?

thanks
Sep 17, 2017  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks for the kind words, glad to hear you like it! Are your Macro actions setup for "Press Key" or "Press and Release Key?"
Sep 18, 2017  • #2
User Image
toddbbot
4 discussion posts
hi keith,

it's setup as a key press and release with the minimum 25ms hold. however, it kills the key i press on the keyboard totally even if i hold it through the macro execution. i have to let go of the button and press it again in order for it to work. i'm getting used to it but it would be perfect if this issue is resolved so i can use both voicebot and keyboard concurrently without having them conflict with each other at all.

thanks,
todd
Sep 19, 2017 (modified Sep 19, 2017)  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ohhh, I see. I think I was getting mixed up on the original issue. So you're holding a key down, then you use a VoiceBot macro that presses a key, and the key you're physically holding down has to be released and pressed again?
Sep 20, 2017  • #4
User Image
toddbbot
4 discussion posts
yup, that's exactly the problem.
Sep 20, 2017  • #5
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ok, thanks! I'll check with our devs on this and see if there's anything that can be done there.
Sep 22, 2017  • #6
Keith Lammers (BFS)'s profile on WallpaperFusion.com
We've done some further investigating here and it doesn't look like this is something we can fix. SendKeys seems to interrupt actual keyboard input and the keyboard input doesn't get detected by Windows again until the next KeyDown event :(

Sorry!
Sep 26, 2017  • #7
User Image
toddbbot
4 discussion posts
Thanks, Keith. It's not much of a problem once I got used to it.
Sep 28, 2017  • #8
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)