SHIFT released by Keystroke Action in 'Pressed or Released'?

Game: Diablo 3

I think I found related (or a new) issue in a development build.

Scenario:
1. I have round-robin set for Shift+1
2. I don't have active binding for Shift+Mouse1. Shift+Mouse1, when pressed, makes character attack while standing in place
3. I remapped Mouse1 to Mouse5. Mouse5 forces character to run around
4. I press and hold Shift+Mouse1. All characters stand in place and start attacking
5. When I press Shift+1 - character that receives round-robin loses Shift status and starts running around
6. Pressing Shift+1 multiple times makes all characters run around except of active one

I did not check if it is only round-robin problem.

[MiRai]

I've split your prior topic since you have a new issue, and a new thread should be created for it in the proper forum.

Beyond that, you will probably need to share your profile.

Done: http://pastebin.com/5RTybnLH

Btw, http://privatepaste.com is down.

[lax]

The character loses Shift status because the Hold option is not enabled on your Shift+1 Mapped Key. It is being instructed to release held any modifiers (due to not having the Hold option), press shift+1, and then release shift+1, as part of your Mapped Key.

In the top left pane under Key Maps, select Combat. Then in the bottom left pane select Round-robin Shift+1, and in the bottom right set "Hold any Keystroke . . ." to On. This will disable the "pressed OR released" because that option is incompatible with the Hold option.

I would do the same thing for your 1 key, but that is more because it probably shouldn't be pressing 1 twice when you press it once.

I am a bit confused by your Mouse1 and Mouse5 mappings though. Chances are they should also be set to Hold...

[bob]

Oh well, had a post, and then Lax said it all anyway.
But I had a picture

diablo_hold.png (11.31 KiB) Viewed 14115 times

The hold option.

Thank you!

Is this recent change? This is pretty old configuration file (from mid 2014) and I think it was working differently back then.

Regarding Mouse1 -> Mouse5 - it is working fine, because I either release the mouse or press shift to start attacking which ends Mouse1 binding.

OK, I was able to test it with "Hold keystrokes" and I still have same problem.

Current version of the configuration: http://pastebin.com/dNzLWmwQ



Just in case, current development build. Also tried different options with Mouse1 remapping and it makes no difference.

[bob]

You've mentioned development build a couple of times now. Does this mean that you don't have this issue when not using the InnerSpace development build?
i.e. if you revert back to 6089, does it work as you expect?

I did not test that particular issue in current stable, because only reason I moved to development build is due to bug with modifier keys not working (see here - viewtopic.php?f=2&t=6849). I know that everything was working fine few versions ago (build 6066).

Probably I can just roll back to 6066, but thought it is worth reporting the issue.

So, I tried 6066 and it crashes Diablo 3 on Windows 10. So for now I'm stuck with development build.