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
If the sensitivity for a dual axis input is less than or equal to the thresholds, the axis will never be considered "pressed". It seems extract_dual_axis_data ignores the deadzone for each axis (as it should) but applies the sensitivity, then checks the deadzone later. In the aforementioned case the inputs are never outside the deadzone. I think this is a bug. The sensitivity should be applied after the deadzone is checked?
The text was updated successfully, but these errors were encountered:
And the new with_sensitivity represents the scale of input values before further processing, i.e., how responsive the input processor is to the received input values
You could use with_output_scale to multiply the output
Version
0.13.3
Operating system & version
NixOS unstable
What you did
Set input sensitivity <= deadzone, i.e.:
What you expected to happen
Non-zero input values.
What actually happened
Zeroes.
Additional information
If the sensitivity for a dual axis input is less than or equal to the thresholds, the axis will never be considered "pressed". It seems
extract_dual_axis_data
ignores the deadzone for each axis (as it should) but applies the sensitivity, then checks the deadzone later. In the aforementioned case the inputs are never outside the deadzone. I think this is a bug. The sensitivity should be applied after the deadzone is checked?The text was updated successfully, but these errors were encountered: