libretro / libretro/RetroArch

Player 2 Cant Map Hotkeys to Any Button.

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

When using Controller set to Player 2 it is impossible to map any of the Hotkeys to any Button on the P2 Controller, you go to set a Hotkey (FF for example) but when it comes to press a Button to map, none of the Buttons will work.

Expected behavior

You should be able to set a Button from the PS2 Controller to a Hotkey just like you can with P1 Controller

Actual behavior

When you go to set a Button to a Hotkey with P2 it wont recognize the Button presses

Steps to reproduce the bug
  1. (When using P2 Controller/P3 Controller etc etc..) Goto Settings>Input>Hotkeys
  2. (using a PS Controller) Press O to select your Hotkey
  3. Attempt to map it to a Controller key (it wont respond to any key press)
  • OS: WiiU but I suspect it happens on all Retroarch Platforms (not confirmed)

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 issue on WiiU by opening Settings>Input>Hotkeys with a Player 2 controller and attempting to assign a hotkey. Trace the input handling for hotkey assignment and compare Player 2 behavior with Player 1. Done means buttons from the Player 2 controller are recognized and can be assigned to hotkeys.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.