libretro / libretro/RetroArch

Inputs become broken after mapping more than 3 axi of a single gamepad stick

Open
#15,974 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

when mapping a controller all buttons work fine untill i map the sticks. i can map 3 axi of a single stick just fine, but after mapping all 4 axi of a single stick all input stop working from both controller and keyboard.

after deleting retroarch.cfg and restarting everything works fine and i can map everything and it works, but as soon as i restart retroarch again it stops working.

i have tried with 3 different controller with usb, 2,4ghz or bluetooth. all have the same problem

i have also tried all 4 input drivers.

on udev i can map 3 axi of a single stick before it breaks
on linuxraw it doesnt detect any gamepad at all
on paraport it doesnt detect any gamepad at all
on sdl2 i can map 2 axi of a single stick before it breaks

only happens on arch linux based distros

Expected behavior

mapping all inputs should work fine without anything breaking

Actual behavior

when mapping more than 3 axi of a single gamepad stick all inputs from keyboard and gamepad stop working

Steps to reproduce the bug
  1. delete retroarch.cfg
  2. start retroarch
  3. map gamepad buttons and sticks
  4. everything works
  5. restart retroarch
  6. all inputs stop working
Bisect Results

i think it started happening since version 1.16.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.16.0.3 (arch linux package from extra repo)
Environment information
  • OS: Endeavour OS with linux-zen 6.6.3 kernel

Contributor guide

Open the contributing guide

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.

Research direction

Reproduce the failure using the stated mapping steps on Arch Linux, comparing the input drivers and the saved retroarch.cfg behavior. Trace the input-mapping and configuration path from the point where four axes are saved, then verify that keyboard and gamepad input still work after restarting RetroArch.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.