[Known] 638 Sticky keyboard in Linux

2/20/2018 6:51 PM
Title: 638 Sticky keyboard in Linux
Reproduction Rate: 100%
Blocker? Yes.
Details: If I hold down a key, like say a movement key, then that key appears to stick down. I believe this is something to do with buffering as it will stop when the buffer is empty. This is a blocker for me.
Steps to Reproduce: Attempt to play using the Linux client.
User Specs:
OS: Linux 4.15 unknown 64bit
CPU: AMD Ryzen 7 1700 Eight-Core Processor (16) System RAM: 32158
GPU: GeForce GTX 1070/PCIe/SSE2 GPU RAM: 8192
SotA.EarlyAccess.QA.Linux.64.638.Date.02.20.18
Area: PRT_island_metropolis_01/Parrot's Roost
Area Display Name: Parrot's Roost
Loc: (-459.1, 77.5, 434.8)
Debug: UFJUX2lzbGFuZF9tZXRyb3BvbGlzXzAxfFBhcnJvdCdzIFJvb3N0fCgtNDU5LjA1NSwgNzcuNTQzLCA0MzQuODE0KXwoMCwgLTAuNDkyLCAwLCAwLjg3MSl8LTU4LjgzMDc1fDMxLjUzNDExfDcuNTc5MjQ2

 

Just to help with additional info, I am not getting this issue in my OSX client running build 638.

 

i am not experiencing this on linux 4.14. ...i did deliberately keep back an upgrade to libinput some months ago due to other in-game mouse oddness, and am still on 1.8.4

 

same here. Keystrokes seems to be buffered and placed in a queue.
linux 4.4 using libinput on wayland
This was also present in build 634 and 636

 

I try it as soon as I get home this evening.

 

@Undone
The client (639) wont start using -force-wayland... SIGABRT.

Starting normally, it's unplayable for me.

 

Thanks for the help testing! We are pretty sure this is a Unity bug in 2017.3, which is already 'fixed' but not released in a build that we can use yet, hopefully very soon! In the meantime, we will be using Unity 2017.2 still for Linux, so the Live build for R51 should not have this input issue.