Skip to content
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

Logitech G27 steering wheel use different axe (0 in stead of 2) for steering -> should be configerable (Gamepad API) #850

Closed
joostaafjes opened this issue Apr 24, 2021 · 4 comments

Comments

@joostaafjes
Copy link

I am using a Logitech G27 steering wheel and found out that it using axes 0 for steering in stead of 2 as used currently main.js

It would be nice to make this axes configurable (preferable in config.py/myconfig.py) but than this value should be propagated to the main.js in some way.

Created this little tool to find the HTML5 gamepad key mapping: https://github.com/joostaafjes/html5-gamepad-tester

@sctse999
Copy link
Contributor

Interesting. Can you submit a PR? I will look into this.

@Ezward
Copy link
Contributor

Ezward commented Jun 12, 2021

@joostaafjes we do have a joystick mapper. See Joystick Wizard in docs. It is a general facility for mapping any game controller that mounts on /dev/input/js0. You create a mapping, then use CONTROLLER_TYPE="custom" in you config to use it.

@TCIII
Copy link
Contributor

TCIII commented Jun 12, 2021

@Ezward,

Executing Joystick Wizard on a Nano 4GB running JP 4.5.1 will cause an unrecoverable core dump due to an illegal instruction.

See issue #807

Also, Joystick Wizard does not create the same hex keycodes as jstest does on a Nano.

@Ezward
Copy link
Contributor

Ezward commented Mar 4, 2023

I believe @TCIII you have successfully used the Joystick Wizard on the Jetson Nano. I have also. So that is a work-around. Also, we intend to refactor the game controller system in a way that would allow a user to implement support for a new or unique controller simply by mapping the codes that come out of it. #1097

So I am going to close this issue.

@Ezward Ezward closed this as completed Mar 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants