@caver01 I second this. On the BYOAC forums there's lot of advice to find regarding the build itself, but note that not everyone thinks very highly of Raspberry Pi's there, so questions regarding this is better asked in this excellent site :)

I'm having the same problem where none of my controllers are working in game, however, I know what you're talking about, as I had that same thing (with the having to basically hold all the buttons to get it to open the remap screen) happen to me. Unfortunately, I have no idea what caused it, and I was only able to fix it by doing a clean install. If it's any consolation, since the install I haven't had that problem (just my current one where my controllers aren't working in game)

@bisantium

Any of the 'lr-' (RetroArch) emulator cores can easily be remapped per system. When in game, pull up the menu (hotkey+x). Next select 'Quick Menu' and then 'Controls'. Rework them to your liking and then be sure to select the save option for the system from the same menu.

@DTEAM I managed to get it fixed with the help of this comment: https://www.reddit.com/r/RetroPie/comments/7r4vr8/how_do_i_reset_control_mapping_in_ppsspp/dsyj3ya/?utm_source=reddit&utm_medium=web2x&context=3

This restored my keyboard functionality and I was able to remap the controller and that worked.

@mattemma

There's no way to know for sure, but the chances are generally good, as a lot of work has gone into making RetroPie, Emulation Station and RetroArch as controller friendly as possible. Do you have a link to the specific controller you're considering?

I am experiencing the same issue, did you ever find the cause? or a solution? Thanks

@nosed07 said in PS3 Gamestop Controller not recognized:

Thoughts?

About what ? If you having a problem with your controller, please open a new topic and add the information requested in https://retropie.org.uk/forum/topic/3/read-this-first.

@simonster @demesauce Okay thanks

@mitu , thanks for your reply.

I have not used Pastebin before, so I hope I am doing this right.

I have one controller plugged in; the GameCube controller through the Mayflash adaptor. I have remapped the controller to use the xboxdrv using these instructions and I only configured the xboxdrv controller through the EmulationStation Configure Input tool, which explains why the runcommand.log says the controller on Pad #0 does not have a profile but the xboxdrv controller on Pad #1 does have a profile.

[INFO] [udev]: Plugged pad: Wii U GameCube Adapter Port 1 (0:0) on port #0. [INFO] [udev]: Pad #0 (/dev/input/event0) supports force feedback. [INFO] [udev]: Pad #0 (/dev/input/event0) supports 4 force feedback effects. [INFO] [Autoconf]: 4 profiles found. [INFO] [Autoconf]: no profiles found for Wii U GameCube Adapter Port 1 (0/0). [INFO] [udev]: Plugged pad: Wii_GameCube_Port_1_(xboxdrv) (0:0) on port #1. [INFO] [udev]: Pad #1 (/dev/input/event1) supports force feedback. [INFO] [udev]: Pad #1 (/dev/input/event1) supports 16 force feedback effects. [INFO] [Autoconf]: 4 profiles found. [INFO] [Autoconf]: selected configuration: /home/pi/.config/retroarch/autoconfig/Wii_GameCube_Port_1_(xboxdrv).cfg [INFO] [Joypad]: Found joypad driver: "udev".

In the RetroPad section (see the full runcommand.log in the pastebin link below) it looks like the Start Button is mapped correctly. If the Start Button worked for me, I can see how to edit the config file to fix the button mapping.

For what it is worth, I first configured the Gamecube Controller without the xboxdrv and I had the same results; the Start, DPAD, A and B buttons worked fine in EmulationStation and seemed dead in the RetroArch emulator. Here is the complete runcommand.log

http://paste.ubuntu.com/26183051/

Thanks for your time.

Here are some tests i have done :

$ jstest /dev/input/js0 Driver version is 2.1.0. Joystick (PowerA Xbox One wired controller) has 6 axes (X, Y, Rx, Ry, Hat0X, Hat0Y) and 13 buttons (BtnX, BtnY, BtnTL, BtnTR, BtnTR2, BtnSelect, BtnStart, BtnMode, BtnThumbL, BtnThumbR, ?, ?, ?). Testing ... (interrupt to exit) Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off 12:off $ lsmod | grep xpad xpad 18566 0 ff_memless 5315 1 xpad $ evtest /dev/input/event[0] Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x24c6 product 0x543a version 0x101 Input device name: "PowerA Xbox One wired controller" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 304 (BTN_SOUTH) Event code 305 (BTN_EAST) Event code 307 (BTN_NORTH) Event code 308 (BTN_WEST) Event code 310 (BTN_TL) Event code 311 (BTN_TR) Event code 312 (BTN_TL2) Event code 313 (BTN_TR2) Event code 314 (BTN_SELECT) Event code 315 (BTN_START) Event code 316 (BTN_MODE) Event code 317 (BTN_THUMBL) Event code 318 (BTN_THUMBR) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 1 (ABS_Y) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 3 (ABS_RX) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 4 (ABS_RY) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 16 (ABS_HAT0X) Value 0 Min -1 Max 1 Event code 17 (ABS_HAT0Y) Value 0 Min -1 Max 1 Event type 21 (EV_FF) Event code 80 (FF_RUMBLE) Event code 81 (FF_PERIODIC) Event code 88 (FF_SQUARE) Event code 89 (FF_TRIANGLE) Event code 90 (FF_SINE) Event code 96 (FF_GAIN)

@cyperghost yeah, I will try to do that

@megahertz Nice!

Make sure you didn't inadvertently disable the "Run Command" option.

Seems like RetroPie... I think the guy took it, added the rest to it and uploaded to share.

My arcade build got derailed temporarily, and was split between using a Pi or a PC based system... had lots done on it and files etc, but never got everything working quite right.

Niece was really interested in it though and likes the old NES/SNES games so, figured for Xmas I'd get one of those NesPi cases and a 16GB card and well, time's a factor so hoped the 16GB Mad Little Pixel image would be better than what I accomplished on my own, but, seems to be a pain in the @$$. :D

That said, attract mode works... though not sure I like it more than the standard RetroPie/ES screen. Has sound and video... but also lag and takes longer to scroll through stuff.

I'll give those a try when I get home. Hopefully a quick fix. :)

Thinking again, once I have all 4 controllers configured and buttons mapped, I could modify the udev rules so that Joy1 and pad1 are both mapped as js0 while joy2 and pad2 are both mapped as js1. Any clue if that would work or create a conflict?