Gamepad doesn't work
-
@rbaker: When I'm in EmulationStation's input config and press a button on my gamepad, it doesn't do anything. My gamepad is a Zolid Potent Pad which registers itself as a Jess Technology Co., Ltd. USB Game Controller. The gamepad works fine inside RetroArch. I'm having this problem on a Pi B+ and 2 with the latest RetroPie build as well as on my desktop with a freshly compiled copy of RetroPie's EmulationStation fork. Are you happy now?
-
@wb9688 said in Gamepad doesn't work:
Are you happy now?
Not really, is it wireless or definitely usb connected with a lead to the Pi?
-
@rbaker said in Gamepad doesn't work:
@wb9688 said in Gamepad doesn't work:
Are you happy now?
Not really, is it wireless or definitely usb connected with a lead to the Pi?
It's wireless with an USB receiver…
-
@wb9688 Point proved. And you still think it wasn't "relevant" to provide these details as requested by @buzz? Did you expect people to read your mind? If you had posted correctly in the first place, you might have had a solution by now.
-
@rbaker said in Gamepad doesn't work:
@wb9688 Point proved. And you still think it wasn't "relevant" to provide these details as requested by @buzz? Did you expect people to read your mind? If you had posted correctly in the first place, you might have had a solution by now.
IMHO most of that details you guys requested were relevant, some not. Of course I didn't expect people to read my mind. Sorry for that!
-
As mentioned, please leave it to us to decide what is relevant. We support various platforms, use a customised SDL2 on some platforms, and there are lots of things that can affect this behaviour.
If you really know what is relevant and what isn't I assume you are happy to debug the issue yourself. If not, please provide the output of
for dev in /dev/input/js*; do udevadm info --name=$dev; donefrom a terminal with the joypad connected and I will advise further. -
@BuZz said in Gamepad doesn't work:
As mentioned, please leave it to us to decide what is relevant. We support various platforms, use a customised SDL2 on some platforms, and there are lots of things that can affect this behaviour.
If you really know what is relevant and what isn't I assume you are happy to debug the issue yourself. If not, please provide the output of
for dev in /dev/input/js*; do udevadm info --name=$dev; donefrom a terminal with the joypad connected and I will advise further.My gamepad works fine with SDL2, that's why I initially posted it on the GitHub issue tracker.
I thought Pi model wasn't relevant as it isn't a SDL2 bug and it happens on every platform where I try to run RetroPie's (or Herdinger's) EmulationStation fork.
I'm not a C(++) programmer, so I absolutely don't know how to debug it. Atm I'm not at home, so I can't post that output, but I definitely will when I'm.
-
Are you actually running RetroPie or just our ES ?
-
@BuZz said in Gamepad doesn't work:
Are you actually running RetroPie or just our ES ?
I'm actually running RetroPie on both Pi's and just ES on my desktop…
Is it possible to manually configure my gamepad in ES to check if the input configuration screen isn't just buggy? If so, are there docs for that?
-
To debug please choose one system (Even if the problem is on many, it's better to debug one) - and please provide all the information you can regarding version etc as mentioned in the sticky topic, so I have an idea of what version of everything you are running.
The output of
dmesgandcat /var/log/syslogwould also be useful - can use a site like https://paste.ubuntu.com/ for the logs
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.