can't use controller in retropie setup menu

Protocultor

One of the runcommand options is "use old joytokey", have you tried it?

stevejp1978

@Protocultor no I haven't, i've done another fresh run and just didn't update the retropie script.... so far so good.

Chuckgofer

I think I'm having this issue too. I'd rather watch this thread rather than make a second for the same issue. As soon as I updated, my controller stopped controlling the Retropie setup menu, Or any menu like it, including the splashscreens menu.

mitu

@Gimkit76 said in can't use controller in retropie setup menu:

Let me know if anyone has found a solution.

Do the gamepads start working after a restart ? Please add your system info, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Chuckgofer

@mitu I'll add my system info too.

Pi Model: 4 4GB
Power Supply used: Official Pi power supply
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.8.9
Built From: Pre made SD Image on RetroPie website
USB Devices connected: 8bitdo Pro 2 and Keyboard
Controller used: 8bitdo Pro 2
How to replicate the problem: Update retropie,

I suspect Joy2Key. The gamepads don't work in the menus with issues after a reboot for me.

mitu

@Chuckgofer said in can't use controller in retropie setup menu:

I suspect Joy2Key. The gamepads don't work in the menus with issues after a reboot for me.

Can you run the following command and post the output. Gamepad must be connected.

python3 /opt/retropie/admin/joy2key/joy2key_sdl.py kcub1 kcuf1 kcuu1 kcud1 0x0a 0x20 0x1b 0x00 kpp knp -d

If the gamepad has been configured in EmulationStation it should pick up the configuration for it and enable it.

Chuckgofer

@mitu said in can't use controller in retropie setup menu:

python3 /opt/retropie/admin/joy2key/joy2key_sdl.py kcub1 kcuf1 kcuu1 kcud1 0x0a 0x20 0x1b 0x00 kpp knp -d

2025-04-07 05:17:39,748 DEBUG  Debugging enabled, running in foreground
2025-04-07 05:17:39,748 DEBUG  Cannot determine input code for "0x00", value ign                                                                   ored
2025-04-07 05:17:39,748 DEBUG  Cannot determine input code for "0x00", value ign                                                                   ored
2025-04-07 05:17:39,748 DEBUG  Joy map:
 {'left': 105, 'right': 106, 'up': 103, 'down': 108, 'a': 28, 'b': 57, 'x': 1, '                                                                   y': 0, 'pageup': 104, 'pagedown': 109}
2025-04-07 05:17:39,850 DEBUG  Parsing config "8BitDo 8BitDo Pro 2 Wired Control                                                                   ler.cfg"
2025-04-07 05:17:39,853 DEBUG  Added config for "8BitDo 8BitDo Pro 2 Wired Contr                                                                   oller" from "8BitDo 8BitDo Pro 2 Wired Controller.cfg"
2025-04-07 05:17:39,856 DEBUG  Parsing config "Generic X-Box pad.cfg"
2025-04-07 05:17:39,858 DEBUG  Added config for "Generic X-Box pad" from "Generi                                                                   c X-Box pad.cfg"
2025-04-07 05:17:40,081 DEBUG  Using SDL Version 2.0.10, PySDL2 version 0.9.3.
2025-04-07 05:17:40,082 DEBUG  Creating uinput keyboard devices with events: [(1                                                                   , 105), (1, 106), (1, 103), (1, 108), (1, 28), (1, 57), (1, 1), (1, 0), (1, 104)                                                                   , (1, 109)]
Traceback (most recent call last):
  File "/opt/retropie/admin/joy2key/joy2key_sdl.py", line 621, in <module>
    sys.exit(main())
  File "/opt/retropie/admin/joy2key/joy2key_sdl.py", line 613, in main
    event_loop(configs, joy_map)
  File "/opt/retropie/admin/joy2key/joy2key_sdl.py", line 382, in event_loop
    vid = joystick.SDL_JoystickGetVendor(stick)
AttributeError: module 'sdl2.joystick' has no attribute 'SDL_JoystickGetVendor'

mitu

@Chuckgofer Thank you for the test. Seems one of my last updates to joykey is at fault. I've backed out the change - can you update again RetroPie-Setup and see if it fixes the problem ?

Chuckgofer

@mitu The issue is solved for me, hopefully this is the issue the others were also having.

mitu

@Chuckgofer Thanks for the confirmation.