Has anyone else experienced keyboard input being ignored when playing zerg and using hotkeys to make units?
If I do 4sh5sh6sh7sh really fast, some of the hatcheries just won't produce anything. I can reproduce this with a single hatchery as well - if I do 4sh fast, sometimes it will work, sometimes it won't. There seems to be a delay after larva selection until a key press is recognized for some reason.
Is there a workaround for this? It's driving me mad to the point of making me not want to play zerg anymore. I tried using a brown switch vs blue switch mechanical keyboard. I'm gonna try to get a cheap membrane keyboard to see if that changes anything.
edit: I've seen top zerg players with keyboard input view, and they seem to be pressing buttons super fast and not dropping any inputs after larva selection, so I don't understand what's going on..
A few days ago I had some issues with my mouse. Left clicks would be ignored. When i changed my mouse everything was fine. Maybe your Keyboard is malfunctioning.
On August 08 2018 16:43 NOtoRiouS_ wrote: A few days ago I had some issues with my mouse. Left clicks would be ignored. When i changed my mouse everything was fine. Maybe your Keyboard is malfunctioning.
I tried it with two different keyboards, so I don't think this is the case
Here is a video someone else made that clearly demonstrates the issue.
or you're just not really pressing all the buttons to the point of registering (most likely I'd say, happens to me or anyone else too sometimes with 1a2a3a4a5a) or your keyboard is not working properly or your computer has a specific problem with the game.
Did you try opening any normal text-field (word-document, browser-website-field, some chat) and doing the 1sh2sh3sh-thing? To see if it actually registers everything? (and not only when you concentrate really hard, but just on the fly any time, like in a normal game situation)
There you have it. For those who have issues with it it's probably rather a problem of modern games "helping" you by registering simultaneous inputs whereas BW just takes that extra bit more of accuracy. Whether you like this or not is up to opinion.
I'm not 100% sure but I have the impression this keyboard input issue got worse with SCR. When I'm spamming early game, I often send my overlord back to my base by mistake. This never happened to me in the past.
With the new 1.22 patch I've had some issues like not working "P" button after 2 minutes in the game, I restarted my computer and everything was fine until the next game where the lights of my buttons went off and I could not start them again with my sensor button (Razer - Lycosa).
On August 08 2018 19:59 HaN- wrote: I'm not 100% sure but I have the impression this keyboard input issue got worse with SCR. When I'm spamming early game, I often send my overlord back to my base by mistake. This never happened to me in the past.
Arent you supposed to say it "got better with SCR."? Pretty sure less responsive = better game
On August 08 2018 19:59 HaN- wrote: I'm not 100% sure but I have the impression this keyboard input issue got worse with SCR. When I'm spamming early game, I often send my overlord back to my base by mistake. This never happened to me in the past.
It might feel like it got worse if you're playing in laggy games. On TR12 or lower that happens to me a lot. TR8 is pretty awful. On iCCup you may have been using MCA launcher's setting to recover lost input or just playing less laggy games.
or you're just not really pressing all the buttons to the point of registering (most likely I'd say, happens to me or anyone else too sometimes with 1a2a3a4a5a) or your keyboard is not working properly or your computer has a specific problem with the game.
Did you try opening any normal text-field (word-document, browser-website-field, some chat) and doing the 1sh2sh3sh-thing? To see if it actually registers everything? (and not only when you concentrate really hard, but just on the fly any time, like in a normal game situation)
On August 08 2018 17:38 quirinus wrote: keyboard keypresses also block other keypresses. so if you didn't release a previous key, it blocks other keys.
These are tested in the video that's posted above and it's not what's causing the problem. All keys register as shown in the virtual keyboard in the video, and the guy isn't clicking his mouse. It has something specific to do with larva selection
Watch the video in .25 speed to see how inconsistent this really is.
The entire first macro cycle is just hilarious. If the keyboard tracker is to be believed (for it's preciseness) then it seems concerning how unable I am to predict which presses actually resulted in hydras.
On August 09 2018 01:46 kaboombaby wrote: Watch the video in .25 speed to see how inconsistent this really is.
The entire first macro cycle is just hilarious. If the keyboard tracker is to be believed (for it's preciseness) then it seems concerning how unable I am to predict which presses actually resulted in hydras.
I tested this myself multiple times, and the inconsistency is baffling. I cannot tell what is causing the input to be dropped because sometimes the 4sh5sh goes through even when sh is pressed super fast, but other times it just gets randomly dropped.
I also don't know if it has something to do with a specific setup because some people just don't have this issue. I was watching Sacsri's stream yesterday and he had his keyboard tracker up, and he was pressing his macro keys SUPER fast (like 500 APM) and none of his inputs were being dropped.
I am going to get my friend's dt-35 and try it later this week to see if it is something specific to mechanical keyboard (although I doubt it). I'll also try ps/2 and USB keyboard connections.
Well this happens to me, but always happened to me, so i thought the game was just like this. So i just press 5SHH to register the hydra production, but could be cool if it was indeed fixed (even more if some people dont get this input loss).
I used to think the same "when i macro slow everything is fine, but when i go faster keys dont register/work..."
Then I realized that I was actually doing it a little bit off, basically having 2 keys pressed at the same time. For some reason BW cant deal with 2 keys at the same time.
If u think this is not the problem just make a macro with your keyboard software and tell it to 4sh5sh6sh with 0.2 sec interval and see if it works, if it does then this is the problem, if not then keep looking, good look?
On August 08 2018 19:59 HaN- wrote: I'm not 100% sure but I have the impression this keyboard input issue got worse with SCR. When I'm spamming early game, I often send my overlord back to my base by mistake. This never happened to me in the past.
I have the same impression. It's harder to split workers by cloning, especially if it lags.
On August 09 2018 08:43 MadJack wrote: I used to think the same "when i macro slow everything is fine, but when i go faster keys dont register/work..."
Then I realized that I was actually doing it a little bit off, basically having 2 keys pressed at the same time. For some reason BW cant deal with 2 keys at the same time.
If u think this is not the problem just make a macro with your keyboard software and tell it to 4sh5sh6sh with 0.2 sec interval and see if it works, if it does then this is the problem, if not then keep looking, good look?
If you watch the video I linked above, the guy does separate key press vs overlapping key press and it makes no difference.
Just to report back, I've tested this with a brown mx switch, blue mx switch, membrane (dt-35), USB vs PS/2, and it all makes no difference - the problem still persists. At this point I am fairly certain it is an issue with BW itself, so I have given up trying to solve it myself. I doubt Blizzard will fix this since they haven't done so in a year since SC:R release. I guess I will just have to press 4sh5sh6sh slower...
I used to have this problem, then I started to play more cleanly. I stopped having this problem. I think it has to do with not allowing ample of time to select the larva before issuing a morph command.
I haven't done any testing because I don't have this issue ever since I acquired a proper rhythm in pressing s+d.
On August 08 2018 19:59 HaN- wrote: I'm not 100% sure but I have the impression this keyboard input issue got worse with SCR. When I'm spamming early game, I often send my overlord back to my base by mistake. This never happened to me in the past.
I have to agree. Maybe it comes from coming back to BW after playing years of SCII where this problem doesn't exist, maybe it comes from using MCA64 launcher back in the day, but I definitely don't remember this being an issue when I used to play a decade ago on iccup.
In brood war to make units you must tap each key in sequence lifting the previous key before pressing the next. 6 > s > d = create a drone : This is what you want to do 6>sd = selecting larva : Avoid this
I watched your video on .25 speed holding down space bar. On hatcheries that failed to create units it is because you did not lift "f", your select larva key, before pressing "a", your hydra key.
In SC2 some layouts allow key presses you are doing such as if your select larva is q and drone is q, you can just hold q to make drones. However this is not the case for brood war for you have to press keys sequentially
Have been watching this thread for a while now since my post and almost felt bad for treating this like the usual "he pressed two buttons at once"-problem.
But after squishy's post I checked the video again like he did and found two things: - like he wrote, the keyboard-display actually indicates that sometimes you do press two buttons at the same time (larva-button still pressed while unit-button pressed), e.g. the second and fourth and fifth hatchery at 24-25 seconds. Now, the fourth hatchery still does produce hydras, the third hatchery though, where your inputs were "correct" according to the display, does not, which brings me to: - the keyboard-display doesn't seem to be an accurarte indicator for inputs in the first place, at least in this video. For several hatcheries that you cycle through (around 24-25 seconds), you can already see the visual-indicators that show that you have selected a hatchery (the green circle around the building, the screen at the bottom-middle showing a picture of the building and it's stats) but the number-button that you pressed only appears a bit later on the keyboard-display. So it's not a way of telling when you actually press what, not precise enough. Maybe there is a small delay, maybe only for some inputs, who knows. That would mean it doesn't proof much if sometimes the display shows the "right" inputs, but still the hatchery doesn't produce.
I always found these complaints a bit over the top to begin with. It not hard to "slow down" a bit - talking about deci-seconds here - and get the right pattern for your BW-inputs; and you won't lose any game because of THAT lost fraction of a second... I know this is a hassle for s.o. who switches between games a lot, but I for my part like that the game is yet a little different (harder you might say). But that's only my opinion about it and you can go on trying to get Blizzard to do s.th. about it.
On August 15 2018 19:23 reps)squishy wrote: I watched your video on .25 speed holding down space bar. On hatcheries that failed to create units it is because you did not lift "f", your select larva key, before pressing "a", your hydra key.
If we're assuming the tracker is a precise tool to be used in this fashion and that the overlay isn't subject to any kind of recording lag...
I watched the first macro cycle (00:25) closely on .25 with spacebar held and see evidence of inconsistencies.
First hatch has a tiny overlap: makes hydras. Second hatch has a longer overlap: no hydras. Third hatch has no visible overlap: no hydras <--- This is the case I find inconsistent. Fourth/Fifth have slight overlaps: one makes hydras, other doesnt.
The third hatch seems like good evidence of this inconsistency, though overlap on the first hatch seems longer to me than some of the others that dont make hydras. I don't know the internal machinations of the BW client all that well. His cadence is definitely weird when he strikes that third hatch striking the hotkey for the next hatch immediately after pressing 'a' but the inputs according the tracker should still be valid.
I think the practical solution is to play cleaner but it makes you wonder. Some minor buffering could probably fix this 100% but with such a purist community I guess we just pray the client is indeed as consistent as we hope it is.