@pirossi said in multiple controllers with hotkey access?:

@dinierto

i have the solution!
i writre here
https://retropie.org.uk/forum/topic/5191/accidentally-changed-button-mapping/12

That's it! Can I kiss you?

Thanks for the reply. The mobile gamepad is only for testing the retropie. If it is a success, which I belive it will, I am buying USB controllers. :)

@phrazelle you can fix the ES L/R by editing the es_input.cfg file.

go to /opt/retropie/configs/all/emulationstation/ open es_input.cfg and switch the values for right and left. This will only effect the controller for Emulation Station and not effect the emulators.

I got mine working as well, the trick, I think was to copy in the ini file (changing the name) and let the config file generate it's own information based on the ini file (device id etc). I did set the number to 0 (full manual) for the controller, but it doesn't seem to matter as it changes back automatically once you launch a mupen64* emulator.

The controller will only work in mupen64 emulators though, so I may still return the adapter for something better. N64 is SOOOO much better with a real N64 controller though.

Not sure why this failed for me the first time, I think by taking in the cfg file I corrupted something.

After a lot of investigation, I didn´t found a working key configuration, online.
Also I could not access /dev/input/ to use jstest... Whatever, testing, testing, testing made the deal:
Working xBox360 wired USB Controller:

[Microsoft X-Box 360 pad] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = Start = button(9) DPad U = hat(0 Up) DPad D = hat(0 Down) DPad L = hat(0 Left) DPad R = hat(0 Right) Z Trig = button(6) C Button U = axis(3-) C Button D = axis(3+) C Button L = axis(2-) C Button R = axis(2+) R Trig = button(7) L Trig = button(8) A Button = button(0) B Button = button(1) X Axis = axis(0-,0+) Y Axis = axis(1-,1+)

And to complete it, the iNext USB N64 Controller:

[Generic USB Joystick ] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button D = button(2) C Button L = button(3) L Trig = button(4) Start = button(9) Y Axis = axis(1-,1+) DPad U = hat(0 Up) A Button = button(6) DPad D = hat(0 Down) X Axis = axis(0-,0+) R Trig = button(5) DPad R = hat(0 Right) B Button = button(8) DPad L = hat(0 Left) Z Trig = button(7) C Button U = button(0) C Button R = button(1)

Seems all fine now, except connecting 2 N64, 1 xBox360 USB and 1 xBox Wireless-Adapter. ES displays, that no Controller is connected. They probably suck to much energy or it is related to the NesPi-Case I´m using :(

But that is another Topic :)

So wanted to give a small update regarding this so that those who want to try what I'm doing don't end up wasting the same time and effort I have. Apparently the reason my controller configurations for my test emulator, the n64 one, didn't work is because I was using the wrong emulator for that one system. Which, yes, is also the default emulator and no, was not really obvious even after studying the docs and other resources for close to two weeks now. No, you first have to manually click a before the emulator boots up (also after selecting a game) and choose a different default emulator, the lr-mupen64plus. Then retroarch will work properly. Only two real problems though: the games look like arse when compared to every other option and the volume becomes so low you'll need to raise it up quite a deal just to hear it. This is true even if you have an external two-speaker and bass boost setup like I've got. And before anyone suggests otherwise yes, I have tried all seven possible emulator options. I did so after reinstalling a freshly downloaded copy of retro-pie on my sd card. The only one retroarch registers is the one with the worst possible graphical and audio fidelity. And for those wondering I have a raspberry pi 3 m so it is the top of the line model. Soon as I figure out how to get this thing to work like I want it to I'll post another update.

@Starcade2084 Cool, I have 2 ps4 controllers for my main use. These are for my 4 year old. I want something basic, easy to use and cheap for her to play seasame street and little mermaid with. She has a few good years before is ready for analog sticks! I also have this: Post with my Donkey Kong 3 Cabinet and I am currently working on a TMNT bartop arcade for my office as well, so i have plenty of authentic controls for my arcade, FBA/Capcom/Neogeo games!

Just thought I'd throw this out there and mark this as resolved. For anyone looking to do what I did which is fully configure your RetroPie, then remove your controller configuration for a clean backup solution (Where you can then restore and configure whatever controller you want as it came Out of the Box) all you have to do is this.

Configure your Raspberry Pi fully (with RetroPie) Make sure all settings are exactly as you'd like with splash screen, themes, core configs, scrapes, roms Delete any save files for the cleanest backups Go to RetroPie > RetroPie Setup > Manage Configurations > EmulationStation > Clear input Configuration Exit to ES, press start on controller and Shutdown System Remove MicroSD card, and insert in computer Create your backup with your favorite backup software, then "Pi shrink" it

@G2bb

While there are a few good ways to make a standard controller be seen as a keyboard, I don't know of anything that would do the reverse. There's a proposed way to do it with xboxdrv, but the project hasn't been touched since late 2015. However, seeing as how all these emulators and ports are first and foremost computer software, they all have keyboard support that can even be a bit more versatile in many cases.

Using RetroArch as a jumping off point, if you can determine which keys are assigned to which buttons, the controls can be added manually to /opt/retropie/configs/all/retroarch.cfg. Below is an example of my setup that you can use as a reference.

input_player1_a = "a" input_player1_b = "b" input_player1_y = "y" input_player1_x = "x" input_player1_start = "t" input_player1_select = "e" input_player1_l = "l" input_player1_r = "r" input_player1_left = "left" input_player1_right = "right" input_player1_up = "up" input_player1_down = "down" input_player1_l2 = "d" input_player1_r2 = "f" input_player1_l3 = "c" input_player1_r3 = "v" input_player2_a = "k" input_player2_b = "m" input_player2_y = "o" input_player2_x = "n" input_player2_start = "num9" input_player2_select = "num0" input_player2_l = "p" input_player2_r = "q" input_player2_left = "g" input_player2_right = "h" input_player2_up = "i" input_player2_down = "j" input_player2_l2 = "s" input_player2_r2 = "u" input_player2_l3 = "w" input_player2_r3 = "z"

@TMNTturtlguy yup. But if i need a bulk set of games that use the same core options or same retroarch.cfg options, i have their individual configs pointing to a different core-options or retroarch.cfg file that i created. So for example psx games that use analog option, i would point their individual config to a different core-options config that i created just for psx that has the analog enabled. That way if the core options ever have any changes made, i dont have to change each config, just the one.

@edmaul69 Tried it (I updated retroarch and all the other cores), and now it magically works! Thanks a bunch, edmaul :)

@alrdtakn1 , yes, it also happens to me in vram settings.
i just installed 4.2 retropie last weekend and did not have this problem for the first couple days.
i think this might have started happening after i ran the update all option for updating everything.
i hope it gets fixed.

does anyone know the config file for setting the ES system volume in sound settings since I can't seem to do it with a controller or keyboard?

@meleu , thanks! that will work great then. i'll try it.

@backstander
It's the layout of most PS3/4 fighting stick (including Hori).
But Retroarch has a native option to switch to

Y X R1 R2 B A L1 L2

Very useful for street fighter like controls :)

@capeman I completely understand, dont worry about it for now, im out on holiday for the next three weeks, then my kids are back, so its game over, if you have a chance then I will do it at some point, but as of now it doesnt look like i will touch it again for the next month.