Several pads of different kinds

DJMoss

@alien it's a shame no one was able to help you with this - I have the same problem when switching between snes and megadrive pads.

mitu

@alien Why don't you connect one pad at a time, depending on the system you play ? The configuration for each pad is kept and applied when the pad is connected/detected by the emulators.

Alien

@mitu Thanks for your reply. The behavior you are referring to is the one I expect, but unfortunately it is not the one that I face. What I have as a behavior is that only the latest pad setup is kept, forcing me to setup again when I switch console, even when ensuring that I have one kind of pad only plugged to the console at the same time.

Any idea, please?

mitu

@alien said in Several pads of different kinds:

Any idea, please?

Did you configure your gamepads in EmulationStation, as explained in Controller Configuration ? This should create configurations for each controller for both EmulationStation and the emulators.

One thing to check - are your controllers named similarly, despite the different layout ?

busywait

@djmoss , @Alien - I think that it's working for me, in the EmulationStation UI at least. (Version 4.7.1)

I've got 4 Sega Saturn/Genesis 6 button controllers plugged in and one XBox One controller. They all work fine to control the EmulationStation UI with the button configurations that I expect. In a RetroArch game, the Xbox controller is always player 1, and the Sega controllers can control player 2, etc.

Is that what you need? (Usually I end up unplugging the Xbox controller until I want joysticks.)

busywait

@alien About the setup... when EmulationStation sets up the controller configuration it creates a .cfg file in /opt/retropie/configs/all/retroarch/autoconfig/

The file has the "Device Name" at the top and the device name is also used as the name of the config file. If both of your pads have the same name then you'll only have one filename (.cfg and .bak) in /opt/retropie/configs/all/retroarch/autoconfig/

Have you looked in that folder to see what gets created after you do the input configuration?

mitu

@busywait What I suspect it's happening is that both controllers have the same name - there were a few reported cases here in the forums. The vendor took one off-the-shelf BT/USB chips and didn't bother to personalise its HID name, so both controllers - although with different button/joystick layouts - end up with the same configuration file, which obviously causes conflicts.

busywait

@mitu Were the Vendor Id and Product Id numbers also the same?

This example of a retroarch autoconfig file shows that they can be included in the file format:
https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/dinput/SNES%20USB%20Gamepad.cfg

Can RetroArch make use of that extra info if it's there? (And, sorry if this is going off-topic, or maybe it's helpful :D )

mitu

@busywait said in Several pads of different kinds:

@mitu Were the Vendor Id and Product Id numbers also the same?

Could me, but let's not get ahead of ourselves :).

Alien

@mitu Thanks men, that's exactly what occurs! Both my pad have the same name. What shall I do, then?

Alien

@mitu But no, they don't share their IDs. But maybe my other ones do... I'll check that later, when the first two are sorted up. Cheers!

mitu

@alien said in Several pads of different kinds:

@mitu Thanks men, that's exactly what occurs! Both my pad have the same name. What shall I do, then?

If they have different Vendor/Model IDs, then configure them one by one, then rename the auto-config files in \\retropie\configs\all\retroarch-joypads\

configure the SNES controller, then rename it's .cfg by adding -snes to it (i.e. mycontroller.cfg becomes mycontroller-snes.cfg).
same for the N64 controller.

You should get the 2 .cfg files for each controller. Edit each file and add 2 lines with

input_vendor_id = "x"
input_product_id = "y"

x and y you can determine by running cat /proc/bus/input/devices and choosing the Vendor/Model numbers, then converting them decimal using http://www.binaryhexconverter.com/hex-to-decimal-converter. An example is on how the new lines should look is here.

See if adding the vendor/model ids to the configuration file makes RetroArch pick the correct auto-configuration for the gamepads.

Alien

I tried this, unfortunately I lose the A button which is used to select options. Hence I can not play a game anymore. Weird... Any ideas, please?

Alien

I mean: I lose it both on SNES pads and on N64 pads...

mitu

You mean, in game or in EmulationStation ?

Alien

In EmulationStation, which means I can not select an emulator or a game anymore... :-(

mitu

The last configured controller should work in EmulationStation, since its configuration is kept. Didn't this work before ?

Alien

@mitu Yes, it worked before but since I did the advised setup I have this strange behavior.

I've just realized that the A (selection) button works in the menu of EmulationStation which appears with start button. But it does not select an emulator (when this menu is closed): when on the home page, the A button only skips to the next emulator, so I can not enter in the emulator game selection menu. I'm lost...

mitu

Save the .cfg files you created, then reset your input configuration from RetroPie-Setup -> Configuration/Tools -> Emulationstation. After you reset the configuration, configure just the SNES pad, make sure you can navigate and operate EmulationStation. Copy back (to their original location) the .cfg files and then start an emulator and see if the SNES controller works.

Alien

@mitu I've just resetted the configuration, I'll let you know how the remaining goes.