xbox 360 usb controller not working in retroarch and cores
-
While trying around many things for my last reply here, I changed a lot of input configs within the Amiga emulators. I didn't change anything within EmultationStation.
The net outcome was that at the point I wanted to get to into the ES menu, it didn't work anymore: the "start" button didn't react. However the DPAD as well as the "a" still seem to work correctly.
A reboot didn't fix it.
I then went in with SSH, into the setup, into "Configuration / tools" / "emulationsation" / "Clear/Reset Emulation Station input configuration", then rebooted and was prompted to configure the controller again.
DANG! Now it works in the NES emulator ?!?!
Investigating…
-
Literally no idea.
Yes, I did switch USB ports but now that it works I can connect the controller into any USB port and when being with in the RetroArch configuration application, it always gets recognized and works (it always says port
#0though; but maybe that's just the virtual management and not the actual USB port?).Something here is very easy to break. I wonder if it's the controllers fault. Though I've been and still using it for years, in the past primarily under Windows and for all I know and see, it does work.
-
There are some major issues with Xbox controllers on 4.4. A friend run into same issues on the 3B+. Before the release of 4.4 everything worked fine, but after the update the troubles started. It looked like the config for the controllers was removed somehow. I removed all the controller configs and tried to add them again but I ran into some issues. When configuring the input both trigger buttons are recognized as axis buttons (saw axis 2 and 5). I thought it was an issue with 3B+ and Xbox One S controllers, but my own 3B with a Xbox 360 controller shows the exact same behavior.
So far I tested:
- 2 Xbox One S (wireless, but connected with wire) controllers on the 3B+
- 1 Xbox 360 (wired) controller on the 3B
All of them show same behavior as you described.
Edit: In all cases xboxdrv was installed.
-
Ok, thanks for sharing!
What I don't understand is the uncertainty. I could swear I tried for hours and nothing worked and then tried again and simply "clicked".
I'm hesitant to try again after shutdown of a few hours … 🤔
-
@max I have the exact same issue as you, though I downgraded to 4.2 thinking that would help but it didn't. So would you say that all you ended up doing was resetting Emulation Station input configuration then rebooted? After reading through this thread I can't see what steps I would need to take to get the joysticks working (I have 1 xbox 360 wired and 1 generic one).
Thanks -
I'm getting similar odd behaviour with a wired 360 controller as well on 4.4 and a 3B+
Works fine in ES, but after launching a game, the start or select buttons won't do anything at first...
But - if I mash random buttons for a little bit first, then they start working in that game all of a sudden, and I can then add coins and start a game.
Exiting also works fine then, but next game I startup I have the same problem again and have to repeat the mashing trick.
-
I have the same behavior on XBox One Rpi3 with RetroPie 4.4 onboard.
One point to add, due to I've tested different emulators - I found that gamepad works fine in particular games (Like Alladin or Worm Jim on Sega32X) but still not working in others (Like Sonic and many more - as on the same Sega32X , so on PSX), SEGA CD.
For me, it looks like an emulator-specific controller mapping failure. -
@tricko I have got the exact same issue. Xbox controller (well Afterburner clone), works fine in ES, but in Mame games, buttons don't work..
..or they don't work for a bit. Mashing random buttons brings things back to life, and then I can add coins and play
I've tried looking through the debug file, but nothing looks amiss.
Anyone else have this issue? Better still, anyone else have a solution for this issue? :-)
-
Try uninstalling and reinstalling the xpad driver. That worked for me several months ago.
-
@jasonw Dude - that worked! Thank you so much.
What I did was uninstall xpad driver, reinstall, reboot, reconfigure the joypad in ES. And bingo! Back in business :-)
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.