|
On April 01 2017 12:29 GoShox wrote:Show nested quote +On April 01 2017 08:59 outscar wrote:On March 30 2017 23:03 outscar wrote:
I got some input issues related to spamming. On 1.16 if you holded key f.e. 3 (CC) and while holding that key if you clicked to minerals you could switch between CC and minerals. In this version if I click to minerals while holding my CC key and then release my click my screen doesn't go back to CC thus I need to push my 3 (CC) hotkey again. Hope I could explain. If not I will try to rec a video. Nice that someone finally noted this out. This thing should be fixed immediately! I mean just give back before input. Please post this on Battle.net forum as well. I believe this issue is due to the difference between L1 and L2. My guess is that when Blizz switches to L2, this will go back to the behavior in 1.16
I already tried it on single player and it has nothing to do with latency. What Randomprecision is saying right. Hope it will get added to TT1's issue list as different input behavior.
On April 01 2017 11:57 rand0MPrecisi0n wrote:
Can someone else test this? I tested on 1.16 and what happens is that the game accepts key repetition (like when you're using word or notepad), so if you hold down a key it starts repeating. I can't run PTR here to see what is going on.
Someone kind enough please test if you can't hold a key down and it keeps repeating (for example, group a unit to 1, tell the unit to go somewhere and hold down 1, if the screen keeps centering it's repeating, if not it isn't)
Yeah it's not working if you hold that key, only works if you press it quickly two times. That sucks...
On April 01 2017 11:57 rand0MPrecisi0n wrote:
Second test would be try to press the mouse when you have a key pressed down, see if the mouse click is registered
Mouse click is registered but like I said above post after you relese mouse button you should go back to your pressed down key which is not happening in this new patch.
On April 01 2017 11:57 rand0MPrecisi0n wrote:
Third would be to group something to any number, box somewhere empty, hold down the number you grouped, wait a second and then release the mouse button. See if the screen jumps to your grouped unit
Same answer like to your 1st question. Screen is not jumping to those grouped units. It only works now if you press it quickly 2 times.
EDIT: Reread 3rd question and didn't understand it well. You mean hotkey f.e. 4 scvs, hold that hotkey then left click and drag somewhere on ground and then release mouse button? So I should jump to my scvs? Hmm that doesn't work on 1.16.1 too if I get your question right.
EDIT 2: If you click somehwere on minimap while holding your hotkey and then release mouse button then yeah it goes back to your hotkeyed units on 1.16.1. Lemme check this on new patch. Yeah of course this one also is not working on new patch.
|
|
|
Someone needs to go out and record all the input delays for LoL, Dota2, SC2, SC BW 1.16 Lan Lat and SC BW 1.18. Because right now only people with fine senses suspect something is off and most people and those coming for games with huge input delays like LoL/SC2/DOTA2/WC3 will not notice.
|
It has nothing to do with any input delay. It's just that keyboard clicks don't register while you are holding a mouse button. Same thing happens in BW 1.16, and as LaLush pointed out, it was happening forever.
|
So you are saying you know for sure, 100%, that 1.18 bnet has the same latency as 1.16 LAN?
|
I also noticed sometimes trying to select all units of same kind by using Ctrl+click works and sometimes it only selects this one unit. Would that be an example of this problem?
|
Germany1307 Posts
This has been freaking me out ever since and in my first few games after 1.18 I was already struggling with this again. I sent 1a2a3a4a only to find out only 1 and 4 are actually moving because I did not release my mouse quickly enough. Not sure why but I do that all the time and being over 30 I don't think I'll ever get my head around doing this right.
Thank you OP for bringing this up in a constructive manner and definitely hoping this gets fixed. This has nothing to do with how hard the game should be or the skill ceiling, this is plain frustration.
EDIT: since some people seem to confuse this issue with input lag or other issues, here a more visual description:
(button up is - button pressed is _ M is mouse button)
This DOES work
1--__-------------------
2-------------__--------
A-----__--------__----
M--------__--------__-
This does NOT work.
1--__-------------------
2-------------__--------
A-----__--------__----
M--------____----___
While the mouse button is still pressed, SC ignores that I press the "2" on the keyboard and never selects group 2. You need to relese the mouse button BEFORE pressing a keyboard button. If there is an overlap it does not work.
|
I had no idea that's why this happened. I always thought I was just messing up which keys I hit.
I wouldn't miss it if it was updated. Sure there's timing to it, and under pressure you're more likely to screw up that timing, so there's something a little interesting about that but... it sucks when you're just doing your normal thing and you're like why didn't they go? So you just teach your self to do 1a2a3a4a5a6a7a multiple times to make sure they all go, when you'd probably be playing a more interesting game if you could do that, then go back to macro or something else. The fact that the answer to the problem is so boring means I think it might as well be fixed.
|
On April 20 2017 22:45 Eridanus wrote:
So you are saying you know for sure, 100%, that 1.18 bnet has the same latency as 1.16 LAN?
I have no idea about latency issue. Just about the input thing that is the same regardless whether you play offline/online
|
First I discovered this issue when I bought cherry mx switchers keyboard. Some of my actions were just "ignored". I realized at that time that holding one of the mouse buttons pressed completely blocked the keyboard input. I ran WC3 and I was surprised that there was no such problem there. I contacted MCA, described the problem and he figured out how to fix it. So now you have an option in MCA Launcher - Shitty Plugin > Keyboard Access > Fix keyboard ignoring (it could sound differently in english version of MCA cause I've translated it from russian).
Conclusion: In my opinion this issue should be completely fixed at least in Remastered.
|
This bug gets me too.
I've learned to be more careful
aka slower.
|
Blizz should fix this issue first. It's very annoying in 1.18.0 ver.
|
As this in fact affects balance, only the opinions of professionals should be considered when messing with aspects like this.
If Flash, Jaedong, Effort, Bisu,.. agree that it can be fixed, I will not complain.
If you're a noob, learn to play cleaner.
|
Not registering commands because keys block clicks and vice versa should be addressed and possibly fixed.
On April 20 2017 23:48 marwin wrote:
First I discovered this issue when I bought cherry mx switchers keyboard. Some of my actions were just "ignored". I realized at that time that holding one of the mouse buttons pressed completely blocked the keyboard input. I ran WC3 and I was surprised that there was no such problem there. I contacted MCA, described the problem and he figured out how to fix it. So now you have an option in MCA Launcher - Shitty Plugin > Keyboard Access > Fix keyboard ignoring (it could sound differently in english version of MCA cause I've translated it from russian).
Conclusion: In my opinion this issue should be completely fixed at least in Remastered.
It is "fix lost keyboard input", but it doesn`t work all the time.
Or maybe I press 2 keys at once (3a for ex.) and this is the issue, maybe the plugin/game registers both key commands and ignores clicks afterwards? (not necessarily ignores the keys, just the click, because the units won`t move)
|
Been jumping on 1.16 and 1.18 back and forth.
On April 01 2017 08:59 outscar wrote:Show nested quote +On March 30 2017 23:03 outscar wrote:
I got some input issues related to spamming. On 1.16 if you holded key f.e. 3 (CC) and while holding that key if you clicked to minerals you could switch between CC and minerals. In this version if I click to minerals while holding my CC key and then release my click my screen doesn't go back to CC thus I need to push my 3 (CC) hotkey again. Hope I could explain. If not I will try to rec a video. Nice that someone finally noted this out. This thing should be fixed immediately! I mean just give back before input. Please post this on Battle.net forum as well.
This is the intended behavior that we're supposed to have. When mouse button is down, all inputs are 'ignored' until its lifted up (this is same for 1.16, not just exclusive to 1.18). The only difference is that when mouse is lifted up, 1.16 will still accept the key press that's held down vs 1.18 ignoring it completely. I wonder if this also has to do with repeating key not working in 1.18 (previously, if you held down a control group hotkey, it would 'repeatedly' send the input).
This also means that people who used the fix keyboard input for MCA was basically gaining unfair advantage over other people.
On April 20 2017 23:48 marwin wrote:
First I discovered this issue when I bought cherry mx switchers keyboard. Some of my actions were just "ignored". I realized at that time that holding one of the mouse buttons pressed completely blocked the keyboard input. I ran WC3 and I was surprised that there was no such problem there. I contacted MCA, described the problem and he figured out how to fix it. So now you have an option in MCA Launcher - Shitty Plugin > Keyboard Access > Fix keyboard ignoring (it could sound differently in english version of MCA cause I've translated it from russian).
Conclusion: In my opinion this issue should be completely fixed at least in Remastered.
I had to whip out my DT-35 to double check: keyboard doesn't really matter.
|
There is something obviously wrong with hotkeys in 1.18 compared to 1.16. I have tested it and creating camera locations were possible holding m1 down in 1.16 and i find my self constantly having to redo them because it is not working in 1.18. Also shift queing units into control groups also fail sometimes and I suspect people who dont notice these things have only played 1.18 and dont know how the game should feel.
|
I consider this to be a critical quality of life change.
This is one of the main reasons why I will continue to use mca64launcher.
Not providing a fix to this is unacceptable. This goes far beyond just "playing cleaner." It borders on frustration. If I input a command sequence, it should work. I should not have to check to see if my camera location was set properly every time I re-rally. I should not be punished for holding my mouse down a millisecond too long after I pressed a camera location key to set it.
This seems to happen far more in 1.18 than it did in 1.16, and I'm not sure why. Please fix!
|
I think many agree, that something feels different. It is however difficult to draw a conclusion based on just a feeling. In this post I'll show you a more scientific approach to compare the reaction of both starcraft versions. Unfortunately I tried it myself and did not find a difference in the behavior, so maybe this is not the best idea. But just in case someone wants to try:
1. Get the program Window Detective
2. Start starcraft in window mode and Window Detective
3. Use "Pick Window" and drag the cross on the starcraft window, there is now one window in the list on the left selected
![[image loading]](http://i.imgur.com/2zC6gkd.png)
4. Right click on the window, then click on "Messages..."
5. Click on the filter icon, then "Exclude All"
![[image loading]](http://i.imgur.com/onXIXxT.png)
6. Select WM_KEYDOWN, maybe WM_KEYUP (probably not interesting), WM_LBUTTONDOWN, WM_LBUTTONUP and click OK
7. Now you can see all the inputs starcraft receives from windows, if you want you can clear the list with the rubber icon and expand the entries using the triangle
![[image loading]](http://i.imgur.com/u10XALN.png)
One thing I noticed is that if the click comes too fast after the a button ~20ms starcraft will ignore it. But this seems consistent in both versions. Unfortunately I have not found a difference between the versions, but at the same time I don't know a better way to get objective data.
|
TL;DR explanation:
In 1.16.1 mouse blocked keyboard input when pressed but when key pressed it didn't block mouse like in 1.18. What we need for 1.18:
- When key pressed it shouldn't block mouse
- When mouse pressed it shouldn't block key
- When hotkey hold screen should follow hotkeyed unit/building (worked on 1.16.1) instead of pressing that key again and again.
|
Germany1307 Posts
On April 21 2017 08:51 Qwyn wrote:
I consider this to be a critical quality of life change.
This is one of the main reasons why I will continue to use mca64launcher.
Can you still do this for 1.18 on regular Bnet?
|
|
|
|
|
|
EPT
