libretro / libretro/RetroArch

[Feature Request] Add a "Delete Current Autoconfig" option

Open
#14,176 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

Many, MANY new users messing with controller configuration end up creating a new autoconfig, usually a beautiful mess with conflicting binds and no labels.

Unfortunately getting rid of an autoconfig atm can be pretty tricky: the user needs to know the controller driver, the autoconfig filename and then has to navigate to the RA folder and delete it manually (which can be "tricky" for new users if it requires FTP or other stuff to access it).

And at least on Android, by default the "autoconfig" folder is not accessible via the file browser without root access so it's even more complicated...

I wanted to include overrides in this issue, but I already opened a feature request a while ago about it: #11442

Expected behavior

Go to Settings > Input > Port N Controls and click "Delete Current Autoconfig", which will then try to reload the correct autoconfig.

Actual behavior

You have to navigate to retroarch/autoconfig/[controller_driver]/ then delete [autoconfig].cfg.

Environment information
  • OS: Affects every devices/OSes.

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

Start at Settings > Input > Port N Controls and trace how the current autoconfig is identified and reloaded. Implement the requested option so it removes the current autoconfig and reloads the correct one, then verify the behavior across the affected OSes.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.