If you accidentally go on device index disabled for port 1 when setting up controllers,there's no way to go back
Open
Nobody has claimed this yet.
bug: input
input
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
allowing player 1 to disable the controller they're currently using in the menu isn't a good idea,you have to do a hard reset and hope retroarch didn't save the configuration...this problem has been around a while
Contributor guide
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.
Research direction
Start by reproducing the controller setup flow described in the issue, focusing on the menu action that lets player 1 disable the currently used controller. Trace the relevant input and menu handling, then verify that the active controller cannot leave setup unusable and that recovery no longer requires a hard reset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100