libretro / libretro/RetroArch

XInput Controller Driver Bug

Open
#15,325 2 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

Device:

  • 8bitdo pro2
  • Hitbox Arcade Controller

If I set A, B, X or Y button to Left/Right Trigger, something going wrong (XInput driver controller only)

  • auto button still works on this button
  • one button(from ABXY) doesn't work , but it can be pressed by other not mapped button(two presses by one other button)
Expected behavior

I expected ABXY should works on any Device

Actual behavior

ABXY got messed

Steps to reproduce the bug
  1. Set A - to 0 value( gamepad device buttons)
  2. Set B - to 3 value
  3. Set X - to +4 value(left trigger)
  4. Set Y - to 1 value
    Now any gamepad test shows what going wrong with ABXY
Bisect Results

[Try to bisect and tell us when this started happening]

Version/Commit

You can find this information under Information/System Information

  • RetroArch: [1.15] /from release
Environment information
  • OS: [Windows 10 64x]
  • Compiler: [Any]

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

No source file, test, or entry point is named. Start by reproducing the issue in RetroArch on Windows with the listed ABXY and trigger mappings, then trace the XInput controller handling. Done means the described mapping no longer causes missing or duplicated ABXY presses, verified with a gamepad test.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.