[#beta-bugs] [input-alpha, windows 10]A bit of a hard-to-explain situation, but I figured I'...

Marked for crossposting by: Ashe-No-Longer, Legendary Seeker

Message (jump):

<Zephyr0> [input-alpha, windows 10]
A bit of a hard-to-explain situation, but I figured I'd post it anyways in case:

Pressing Shift + A has a random chance of activating either "Melee attack nearest enemy" command (Shift + A) or "Ability Picker" command (A). This is especially perplexing since my key bindings have diverged between beta and input-alpha, and Shift + A doesn't appear to be bound to anything at all in input-alpha.

To me, this presents two unexpected behaviors:
1.) Why is an A key binding getting activated when Shift modifier is held down (I would expect a Shift + A key binding to activate if bound, otherwise nothing)
2.) Why is the new input-alpha input manager activating a key binding that's bound only in the old input manager?

Behavior #2 gives me some wild hypotheses, despite not knowing anything about how the code actually works:
Could it be possible that the old input manager is still around and is sometimes handling the key event with the old key bind for Shift + A, exhausting the key event in the process, thus preventing the new input manager from handling the key event? Could this cause a race condition to determine which input manager gets to handle the key event first?

To (hopefully) reproduce: hop between beta/input-alpha branches, setting the following key bindings, and in input-alpha spam Shift + A a bunch as you walk through Joppa swamp zones:

Key bindings in [beta] input manager:
- "Melee attack nearest enemy": Shift + A
- "Use Ability": A

Key bindings in [input-alpha] input manager (after I removed [user].Keymap2.json file, to fix a previous issue in the channel https://discord.com/channels/214532333900922882/459482205635215360/1100325870293499935):
- "Melee attack nearest enemy": None
- "Ability Picker": A

Comments (3)