Wheel + Joystick Suppot

Open
#14,829 17 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
game-dev

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

controllers enhancement wheel
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

batocera-support-20251118185505.tar.gz

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from batocera-linux/batocera.linux

All issues in batocera-linux/batocera.linux

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.