Controller Autoconfigs

Issue #1877 new
Ciarán McCarthy created an issue

Hi Jason,

I encountered an issue recently while setting up a Gamecube pad and Brad mentioned to maybe log a ticket for it.

The settings for controller automation are currently saved globally. As many users like to use original or replica pads for certain systems, the settings for exiting emulators, i.e., hold Select and press Start, will not work for all controllers as the value for buttons on each pad may differ.

I had to create a workaround for this by checking to see which button values were common to all three of my pads, an iBuffalo SNES pad, a 360 pad, and an original Gamecube pad using a Mayflash adapter.

Could LaunchBox/Big Box use a similar system to what RetroArch uses in that when it boots up, it detects the ID of the connected pad and loads that profile automatically?

This would be so handy for users as not all of use use just one pad or have an arcade tankstick setup and prefer to use original pads for different systems when possible.

Charco.

Comments (12)

  1. damageinc86

    quite a few duplicates. didn’t know I was in good company. We really need to be able to map controls per controller, and not globally. Definitely a vote from me.

  2. Michael Benavidez

    Agreed, I even looked for duplicates and didn’t find them, I’m surprised this issue has been raised for four years. Hopefully if more of us bring attention to it we can get it addressed in a future update.

  3. damageinc86

    12 votes lol. darn. Time to take out a billboard or something. I still use my keyboard because none of my buttons across my 4 differents sets of controllers match up with each other.

  4. damageinc86

    At this juncture, I'd pay Jason personally just to get someone on the team started on this issue. This is a pretty big usability issue.

  5. Wanderman

    I think this would be a great addition to Launchbox and also I think this goes hand in hand with issue #7003 since implementing SDL will bring support to many input devices and will make easier the implementation of this issue.

  6. Log in to comment