[BUG?] "Sticky" movement keys (in EDO settlements only)

[rootsrat]

Does anyone experience this from time to time? Basically, sometimes - not very often, but often enough to be annoying - when you press a movement key, it "sticks" for a couple of seconds even after you relase the actual key on the keyboard.

I.e. I'd press "A" to strafe left, I release "A", but my character will keep moving in that direction for 1-2 more seconds. It does feel a bit weird as well - it's not the same continuous movement when the key is pressed, it... I don't know how to describe it... it feels "stretched" (?) or "less fluid" somehow.

Did anyone else come across this issue?

Another one is when I quickly select an item from the quick-wheel, like a medkit or energy cell, the movement keys do not react at all until 1-2 second after I release the "show wheel" hotkey. It is really disturbing especially in a dynamic fight, where I feel I need that extra second or two after using an item, until I can press the movement key. My character is obviously motionless for that duration which makes him an easy target. It's a matter of life and death in certain situations.

Anyone for this one too?

 

[zimms]

I guess that's also performance related. I mostly experience sticky mouse clicks in combat zones. Meaning my weapon keeps zooming in or firing even though I'm no longer pressing the mouse button. Some other input like reloading or switching weapon usually fixes it.

 

[Vandaahl]

Did anyone else come across this issue?

Do you have a bluetooth/wireless keyboard?

 

[rootsrat]

I guess that's also performance related. I mostly experience sticky mouse clicks in combat zones. Meaning my weapon keeps zooming in or firing even though I'm no longer pressing the mouse button. Some other input like reloading or switching weapon usually fixes it.

Yeah, I reckon it's tied to the performance.

Do you have a bluetooth/wireless keyboard?

No sir! Good old boomer wired keyboard with mechanical Cherry red switches. Works perfectly in other games.

 

[metatheurgist]

Yep, occasionally when the game stutters it tends to keep the last input.

 

[Guyperson]

No sticky keyboard input so far but the mouse button likes to stick any time there's interface lag. Especially on the galmap leading to unintended course plotting. Meanwhile the shipyard UI will either fail to register mouse clicks or they'll click through to the next screen and try to sell the ship I'm attempting to get into.
Oddly the HOTAS buttons are completely unaffected by this phenomenon so it's just the mouse that's impacted from what I've experienced.

 

[Rat Catcher]

Interesting.
I had the odd effect that when switching weapons with keyboard my character would stop, requiring a fresh push of the key to move again, this effect didn't show when using the mouse wheel to switch.

Checking the bindings I found that the weapon switch keys had had other properties added by the emotes update, so the keyboard keys had been mapped twice. I sorted that out by moving wheel select and another function to alternate keys - problem solved.

Suggest checking your bindings to see if keys used by you have not been hijacked by default ones added later.

 

[rootsrat]

Interesting.
I had the odd effect that when switching weapons with keyboard my character would stop, requiring a fresh push of the key to move again, this effect didn't show when using the mouse wheel to switch.

Checking the bindings I found that the weapon switch keys had had other properties added by the emotes update, so the keyboard keys had been mapped twice. I sorted that out by moving wheel select and another function to alternate keys - problem solved.

Suggest checking your bindings to see if keys used by you have not been hijacked by default ones added later.

Thanks, I'll have a look!

 

[Frop]

Checking the bindings I found that the weapon switch keys had had other properties added by the emotes update, so the keyboard keys had been mapped twice. I sorted that out by moving wheel select and another function to alternate keys - problem solved.

Source: https://www.youtube.com/watch?v=BYzQq5hIL4A

 

[Rat Catcher]

Source: https://www.youtube.com/watch?v=BYzQq5hIL4A

When it comes down to ED bindings, the whole jar would be needed!

 

[KingTurtle]

I actually experienced the opposite effect OP. I had my forward key (w) randomly not respond only on settlements. I would have to hit escape twice to get working normally. Meanwhile this never happens at the station when I use it the most running between NPC, Pioneer Solutions, and the Terminal.

 

[Wizz15]

I actually experienced the opposite effect OP. I had my forward key (w) randomly not respond only on settlements. I would have to hit escape twice to get working normally. Meanwhile this never happens at the station when I use it the most running between NPC, Pioneer Solutions, and the Terminal.

I believe I have this effect after using the on-foot radial menu after selecting an energy cell or turning my light on/off, then I cannot turn for a certain amount of time (usually when under fire in a on-foot CZ). Strafing and moving forwards/backwards still works for me then. It's like certain inputs are still mapped to UI elements that have already disappeared from my screen, almost like some kind of timeout needs to expire after UI elements disappear before the the inputs are mapped to movement again.

I usually play with a controller though, I have not tested if I see the same effect when using my mouse to aim. It could be a binding issue for me as well (since turning and navigating the menu happens using the same gamepad stick). On keyboard I would navigate the menu differently, so not sure if the menu navigation overlaps with movement keys when not playing with a controller.

 

[rootsrat]

I believe I have this effect after using the on-foot radial menu after selecting an energy cell or turning my light on/off, then I cannot turn for a certain amount of time (usually when under fire in a on-foot CZ). Strafing and moving forwards/backwards still works for me then. It's like certain inputs are still mapped to UI elements that have already disappeared from my screen, almost like some kind of timeout needs to expire after UI elements disappear before the the inputs are mapped to movement again.

I usually play with a controller though, I have not tested if I see the same effect when using my mouse to aim. It could be a binding issue for me as well (since turning and navigating the menu happens using the same gamepad stick). On keyboard I would navigate the menu differently, so not sure if the menu navigation overlaps with movement keys when not playing with a controller.

This the 2nd issue I described in the OP. Thanks for confirming!