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
Each axis would correspond to up to two "virtual" buttons (not sure on the terminology). E.g, "Axis 1+" would be considered pressed when Axis 1 is pushed in a positive direction and "Axis 1-" would be pressed when pushed in a negative direction.
Virtual buttons would appear in the Controller tab and collect statistics like normal hardware buttons. This is also how the d-pad buttons currently work.
Virtual buttons would only be created if an axis can be pushed in a direction. E.g., if an axis' range is 0 to +1 and its neutral is 0, then it cannot be pushed in the negative direction and so only a positive button is created.
There should be some threshold so that very small movement doesn't create a button (e.g., has to be more than 0.1 units away from neutral).
The text was updated successfully, but these errors were encountered:
Each axis would correspond to up to two "virtual" buttons (not sure on the terminology). E.g, "Axis 1+" would be considered pressed when Axis 1 is pushed in a positive direction and "Axis 1-" would be pressed when pushed in a negative direction.
Virtual buttons would appear in the Controller tab and collect statistics like normal hardware buttons. This is also how the d-pad buttons currently work.
Virtual buttons would only be created if an axis can be pushed in a direction. E.g., if an axis' range is 0 to +1 and its neutral is 0, then it cannot be pushed in the negative direction and so only a positive button is created.
There should be some threshold so that very small movement doesn't create a button (e.g., has to be more than 0.1 units away from neutral).
The text was updated successfully, but these errors were encountered: