Steam input weird state, possibly related to Asus Chakram mouse and steam input

crystalshadow

New member
I have seen this bug twice. I generally have steam input on for all my games by default.

I recently got an asus chakram mouse. I do not use it in the mode that simulates controller input (I use the default mode that simulates keypresses) and use the "Joystick" (Mapped to arrow keys) for my abilities. When the bug occurs, the following issues happen sporadically, sometimes partly resolving. A client restart does not fix the issue entirely (Seemed to help when I tried it the first fime I hit the bug, the second time I realized disabling steam input fixed it)

1: Mouse appears on normal gameplay screen as if in menu. moving mouse to the edges still lets me continue turning the camera
2: Have trouble clicking on anything in the shop or in menu. (Note: This can even make it hard to click "reconnect" when attempting to restart the client)
3: Sometimes the hotbar on the screen will show controller button prompts (I suspect my mouse is being seen partly as a controller which could be the cause of all this)? At other times this appears "normal". I sort of try frantically hitting escape and such when the bug happened, and this particular symptom would go away but not others.
4: Independent of if 3 is happening or not, my "1" ability can't be used. Sometimes, pressing "1" (Or up arrow key, I have both mapped) will cause the hotbar to animate as if I were trying to use an unavailable ability. Other abilities are fine.
5: Once, the right click (Zoom aim) will get stuck "on". It took me a bit to understand what was happening, as I was slowed and unable to use the zipline.

The first time this happened, I tried restarting the client which did not immediately solve the problem, but it went away on it's own during that game.

The second time this happened, it was still occurring while I was on the menu trying to click "Reconnect". I realized this might be steam input related, used shift-tab to get to that and disable it. The bug immediately went away.

I had multiple perfectly fine gameplay sessions between instances of this bug, despite not turning steam input off the first time (Since it was not my suspect). One instance was tonight, and the other was whenever I posted my recent bug about my party being separated after restarting my client (Because this bug was happening, but with so many strange things that I didn't want to try to articulate it at the time)
 
Back
Top