evtest continuously sending ABS_Z from zero delay (deadzone problem?)
dsstrainer last edited by dsstrainer
I'm trying to setup xboxdrv with my Zero Delay encoder by following this guide:
When I get to this step:
it seems like the encoder is continuously sending ABS_Z movements so it just prints rapidly to the screen. Hard to test the other buttons as I see them fly by. I assume it's some sort of deadzone issue and found another person with a similar problem with other joystick types: https://steamcommunity.com/app/221410/discussions/0/558748653738497361/?ctp=3#c618460171328711779
I don't see a way of setting deadzones for evtest though. I suppose I can just filter them out with grep while I grab the other button events. Wasn't sure if there were any other tips
Wasn't sure if there were any other tips
None that I know of. I ran into the same problem while mapping my Wavebird controller. When I would press a button, a stream of unrelated input from the analog triggers would follow and stop when the button was released. At the time I just scrolled up to the top of the readout and the button press was always the first listing, but the situation was not ideal. After it was mapped and the deadzones were corrected within xboxdrv it behaved very well. I really like your idea to filter the garbage with grep. If it works out well for you I'll be sure to add it to the guide.
dsstrainer last edited by
Well I didn't touch anything... just went to bed.. woke up and was going to try the grep method... but now it just works fine. Weirdest thing is that it was spewing about ABS_Z which is the analog stick but the zero delay doesn't have an analog stick
Well I didn't touch anything... just went to bed.. woke up and was going to try the grep method... but now it just works fine.
Luck favors the well rested. Glad to hear it's working.