New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple Controllers' Buttons Not Working in RetroPie #1092
Comments
I have a similar problem. Retropie with Amiberry and Gamecondriver (db9_gpio_rpi). Gamecondriver is installed and loaded (options db9_gpio_rpi map=1,1). I checked all the buttons on my two joysticks with jstest /dev/input/jsX. They all work. In Amiberry, however, the fire button of the second joystick does not work. All other functions are available. With UAE4ARM it worked. |
If you need help with the test or logfiles, I can support you |
Do you have the same problematic behavior on a diagnostic tool? Check that you have your controllers correctly configured in the Input Ports as well (Port 0 and 1). The mode is important, the EDIT: for the record, I cannot recreate this in a normal environment outside RetroPie, using 2 PS4 controllers and AmigaTestKit. So it may be related to retroarch mapping only, which I didn't get a chance to try yet. EDIT2: I can recreate it when using Retroarch mapping, so it must be a bug in there somewhere |
Hi Dimitris, Thank you very much for your answer. Thanks and greetings |
I've tried it with DiagROM. It's exactly the same as with a game. Set up Port 0 as first controller in list, type default or joystick; all movement and fire button on Port 0 registers. Set up Port 1 as second controller, either type; all movement registers on Port 1, no button register on Port 1. Swap controller positions in list >> Set up Port 1 as first controller in list, type default or joystick; all movement and fire button on Port 1registers. Set up Port 0 as second controller, either type; all movement registers on Port 0, no button register on Port 0. If I map second controller (Port 0) directions to Joy1 fire button input it registers, e.g. dpad up can work as fire button, up registers as Port 0 fire. Button inputs do not work when manually mapped, e.g. north button or leftjoy press on second controller (Port 0) to Joy1 fire button, no fire registers on Port 0. First controller buttons can be mapped to the other port fire button and this works correctly, e.g. first controller (Port 1) North button mapped to Joy1 fire, North button register Port 0 fire South button registers Port 1 fire. Obviously, both these configurations are useless because either you lose a control direction or the fire button is on the wrong controller, but they prove that the button inputs of the second (or third or higher) controller are not being picked up inside the emulator. |
fixes #1092) When using retroach mappings, only the first controllers buttons would trigger
fixes #1092) When using retroach mappings, only the first controllers buttons would trigger
Bug located and fixed. Will be part of the next release. |
Great, thank you |
Excellent, thanks! Can confirm this works. Buttons now working on the second and subsequent controllers in the emulator. Great work! The bugs with the hotkey combos and analogue sticks in the GUI are still present and are obviously separate (extremely minor) issues. The amiberry.conf joy0 thing is probably just a typo in the documentation. |
I am having an issue when using multiple (identical) controllers where only the first registered controller's buttons work. I'm running Amiberry 5.6 on Retropie.
In the emulator, the D-pads and analogue sticks work correctly on all controllers whichever port they are assigned to but the buttons only work on the first controller.
In the GUI, the D-pad and buttons only work on the first controller but the analog sticks work on all of them.
It might be related or not but in the amiberry.conf file under default_controllerX and default_mouseX, joy0 doesn't represent the first joystick, joy1 does.
A little bit more info, hopefully relevant. All controllers can enter the GUI with the Retroarch hotkey combo. Only the first controller can exit with this combo. Oddly, this behavior is the same whether the menu combo is disabled or not. Disabling the quit combo seems to work correctly, though, and only the first controller can quit when it's enabled
The text was updated successfully, but these errors were encountered: