Wheel + Joystick Suppot
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the attached support log and the Batocera configuration around controller handling, especially the reported global.use_wheels setting. Reproduce with a Logitech G29 connected and compare controller assignments in a non-wheel game and a wheel game. Done means wheel games use the wheel while other systems keep using the joysticks; the issue does not name relevant files or tests.
Written by the indexing model from the issue text.
Description
Batocera build version
42
Your architecture
X86_64
Your Graphic Processor Unit(s) (GPU)
Nvidia Integrated
Issue description
I have an Xtension 4 Player as my main controller - as well as 2 Aimtrak guns. I just recently added the Logitech G29 and i'm experiencing some weird behavior.
Right now for say a non-wheel game - while the Wheel is plugged in (say MAME 1941) - the P1 controllers seem to work for P2.
For other systems such as NAOMI - i am able to start a game from the Wheel (say 18 Wheel Trucker).
My hope and ask is that out of the box - wheel games (Wheel Collection) will use the wheel and other systems will default back to the Joysticks.
Detailed reproduction steps
Plug in G29 Logitech - Joysticks start acting strange - unplug G29 all controllers work fine
Details of any attempts to fix this yourself
Attempted
global.use_wheels=false in batocera.conf to no avail.
Details of any modifications you have made to Batocera.
none
Logs and data
- Dominant language
- Python
- Stars
- 3.2k
- Forks
- 748
- Avg merge
- 9h 51m
- Merged PRs (30d)
- 170
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from batocera-linux/batocera.linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
batocera-linux/batocera.linux#17423 ·
Maintainers usually reply within 1 day
-
Bump `ledspicer` to v0.7.8 - Corrects Bug with newer Ultimarc IPAC Ultimate boards w/ newer firmwareOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
batocera-linux/batocera.linux#17329 · 1 reaction ·
Maintainers usually reply within 1 day
-
evmapy dies at startup if an input device disappears during its device scan -> game runs with no hotkeys (Select+Start exit etc.)Possibly taken @jonathanroehm claimed this 30 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
batocera-linux/batocera.linux#17210 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
batocera-linux/batocera.linux#16092 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
batocera-linux/batocera.linux#17422 ·
Maintainers usually reply within 1 day
All issues in batocera-linux/batocera.linux
Similar issues
-
hive size:simple
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
painted-porch/marcus#977 ·
Maintainers usually reply within 1 day
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FAIRmat-NFDI/sand#239 ·
Maintainers usually reply within 1 day