-
-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using other input devices #517
Comments
Basically adding this into my own main.py for a project was able to read my wheel axis and buttons:
I suppose a generic joystick would be a better name for any device with axis and buttons |
I found a problem with current input handler, it tries to filter the " up" movement for a button, but ends filtering any key ending in "up" I open a PR #524 |
By now I I call my |
Showing a use case for this change: Allow to use a wheel for a drive game (still only hat, not axis, but input is there to code some logic) |
@albfan : I wonder weather this patch might be required to set-up the |
This help yo recognize other input, so with modification you can use whatever input, and then write some logic around that |
You should make a PR if you've got something working and it's stable. |
Ok, will try to code some PR to cover devices with axis and buttons |
Out of curiosity dig a bit on gamepad and add this patch:
Which outputs:
I'm sure ursina tries to stay simple, but wonder if support other devices would be an accepted PR.
Same as buttons remap, it can accept a map for button names and axis names and send that data as gamepad.py does to input function.
The text was updated successfully, but these errors were encountered: