In emulationstation everything works normal. So far I tested it with NES, SNES, N64, PSX and AMIGA emulator. The start, select and shoulder buttons only work on the NES30. All other buttons work on both

@AlphaBetaPie said in Easiest Way to Remove Key Bindings?:

Would kiosk mode work equally well?

Yes, that's also an option.

@arduinoGamepad Emulationstation is using SDL's joystick sub-system to handle joysticks, my guess it's not detected as such. There's a similar sdl-jstest utility -which is similar to jstest - that tests whether the joystick is detected by SDL.

To get it detected by ES, try one of these - in order

add a local udev rule to force the device to appear as a joystick: SUBSYSTEM=="input", ATTRS{idVendor}=="<VID>", ATTRS{idProduct}=="<PID>" ENV{ID_INPUT_JOYSTICK}="1"

substituting VID and PID with the values you get for your controller from running lsusb.

Use Xboxdrv to make your device be seen as an Xbox driver.

Got it resolved by editing /etc/modprobe.d/xpad.conf and changing triggers_to_buttons to 0

In the end, I connected a mouse to play Arkanoid in lr-mame2003, and it worked from the off. Xbox 360 controller just too baggy and too huge a deadzone to make it playable. Thanks for advice though.

@nielogiczny Makes sense! I had to do that with the 8-bitdo SNES Bluetooth controller. The setup script had it as an option. Before that, only one or 2 of the key presses would do anything, and it registered as a keyboard when it did.

Glad you got it working!

If your Xbox One controller supports Bluetooth, you don't need a wireless adapter. I think newer models (after 1708 ?) have Bluetooth by default, but you can check your controller model for BT support.

@Rubencn1234 Can you post the config files on pastebin.com to take a look ? Do you have any other controller connected or configured in your system ?

Hi,

Try the followings process :

install mk_arcade_joystick_rpi driver from ~/RetroPie-Setup/retropie_setup.sh edit /etc/modprobe.d/mk_arcade_joystick_rpi.conf adding the following line : options mk_arcade_joystick_rpi map=5 gpio=5,6,13,19,21,4,26,12,23,20,16,18

I had the same issue, with the same brand PDP controller as the OP but purple controller (vVendor ID 0x0e6f, product ID 0x02bd). I followed the instructions to recompile the driver, but it still wasn't getting picked up.

I then did full update as per https://retropie.org.uk/docs/Updating-RetroPie/ and it all came good :)

Regards
Dan

Thanks, somehow I missed it.
facepalm

@mitu said in RetroArch isn't mapping the GamePad buttons correctly - RetroPie 4.4:

OK, just one last check - you modified both the retroarch.cfg in /opt/retropie/configs/all/retroarch.cfg and the gamepad.cfg file in /opt/retropie/configs/all/retroarch-joypads and put input_driver=sdl2 ?

Awesome that seemed to fix the problem!!! :-)

It seems that I missed input_driver in retroarch.cfg. Previously I only changed input_joypad_driver

So for others who might be having the same problem.

Make the following changes:
/opt/retropie/configs/all/retroarch.cfg

input_driver="sdl2" input_joypad_driver = "sdl2"

/opt/retropie/configs/all/retroarch-joypads/Gamepad.cfg

input_driver = "sdl2"

Thanks again for all the help!

Had a similar problem with an old Ipega GamePad. Pair with BlueTooth with some re-connect issues, but worked with jstest and evtest.

Adding the udev rule helped with emulationstation, but only the left joystick works in RetroArch.

Running RetroPie 4.5.1 with updates. Any suggestions?

I found the problem (or just one solution atm). There is something that libretro does not like in the driver implementation. Now I can fully play the Super Mario in the PC browser and on Android Chrome in my smartphone.

Sorry for the noise and thanks for your time, but hopefully everyone will benefit from this once I have made a demo.

@mitu my apologies, im not sure of the rules here, one topic was different(relating to multiple controllers). Im just frustrated as there is clearly meant to be an option for this and i cannot seem to find any answers anywhere.