You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the left and right shoulder trigger, my controller creates spurious inputs which wiggle between two adjacent integer values, most of the time only the right one. In rare cases, the left control stick is also affected.
These spurious inputs cause complications in button remapping when the trigger buttons are triggered all the time without applying force.
I am not sure what is the best approach. The udev input absmin values for the left and right trigger is too low, in my case it needs to be at 35. Not sure, if changing it in my code copy would be a good solution. A command line option might help. A more consistent solution could be a resolution or deadzone option which ignores button input updates whose value only differs by 1 but I guess, checking the difference against a memorized value could require slightly more effort than just setting the absmin/absmax value via command line option.
Ah, I just found the documentation and it is simple, the absfuzz member determines a tolerance for ignoring this noise. The absflat member is said to be the deadzone value. Instead of absmin, absflat needs to be set for the R and L triggers.
At least one Pull Requests changed this already.
I am just mentioning this here as a potential idea.
The text was updated successfully, but these errors were encountered:
In the left and right shoulder trigger, my controller creates spurious inputs which wiggle between two adjacent integer values, most of the time only the right one. In rare cases, the left control stick is also affected.
These spurious inputs cause complications in button remapping when the trigger buttons are triggered all the time without applying force.
I am not sure what is the best approach. The udev input absmin values for the left and right trigger is too low, in my case it needs to be at 35. Not sure, if changing it in my code copy would be a good solution. A command line option might help.
A more consistent solution could be a resolution or deadzone option which ignores button input updates whose value only differs by 1 but I guess, checking the difference against a memorized value could require slightly more effort than just setting the absmin/absmax value via command line option.Ah, I just found the documentation and it is simple, the
absfuzz
member determines a tolerance for ignoring this noise. Theabsflat
member is said to be the deadzone value. Instead ofabsmin
,absflat
needs to be set for the R and L triggers.At least one Pull Requests changed this already.
I am just mentioning this here as a potential idea.
The text was updated successfully, but these errors were encountered: