@mitu welp, you solved my problem. So emulationstation if launched from c:\programfiles\emulationstation\emulationstation.exe it is v2.9.0RP-DEV which works fine. I originally set it to install in D:\emulationstation so the exe in that location launches v2.0.1A which I just realized I accidentally deleted my desktop exe and then went to that location to grab it again. Dont know why there are 2 locations but v2.0.1A is what causes a problem. Somehow when typing this I went to 2.9.0 without thinking to check the version and then just closed it but every time I tried to use a controller I was launching v2.0.1. Sorry and thank you ._. Going to leave this up unless mods wanna delete it cause maybe others might make a dumb mistake like me.

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.

@Babis said in Controllers Setup: If I install a fresh image of retropie will my roms remain or do I have to back them up and re upload them? A fresh image will have only RetroPie, no ROMs are included in the image. You'll have to back them up if you like to keep your existing files.

@SinisterSpatula That's great indeed and I'm glad I could help. I can't wait to see the next iteration you produce. The advanced mapping method with case statement really works well if you have a lot of code. My arcade machine's runcommand-onstart.sh has about 4,300 lines of code for 4 arcade joysticks, a PS4 wireless controller and an 8BitDo Zero covering about 60 systems. I also use it for all of the libretro cores too now. It doesn't miss a beat, so I reckon you're going down the right path. Going back to my GPi vice code, with a bit more testing I'm finding that it's definitely not working for every game, so I reckon your newly produced code will be more successful than mine in "universalising" the controls for the c64. Please feel free to experiment with my code of course and make any changes you think are best.

The USB is rather OK, has been from the start. Only issue is that the home hotkey doesn't work. But I bought this for BT, and as I have no experience, I thought it really is 8Bitdo. I was fooled by the ebay sellers having 8Bitdo in the topic. I only yesterday found out it is not 8Bitdo :(

Yes, I noticed. cat /sys/class/power_supply/*/capacity will give you all the controller percentages. Though I'm not that skilled enough to create a RetroPie menu item for this.

Wow... So far indeed solved... Followed : https://www.reddit.com/r/retroflag_gpi/comments/c1psvj/dpad_not_working_in_pcsxrearmed_and_gpsp/ .... and played crash bandicoot fullspeed !

I'm at my wits' end here. I've tried blacklisting the device to prevent it being grabbed by usbhidby creating /etc/modprobe.d/blacklist.conf and adding to it : blacklist usbhid No dice. I've tried creating: /etc/udev/rules.d/99-disable-usb-hid.rules and adding to it: SUBSYSTEMS=="usb", DRIVERS=="usbhid", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="028e", ACTION=="add", ATTR{authorized}="0" No dice. Before that, tried adding an /etc/udev/rules.d/ ruleset with: SUBSYSTEM=="usb",ATTRS{idVendor}=="045e", ATTRS{idProduct}=="028e", MODE="666", GROUP+="plugdev" No dice. The end result is always the same, reboot after reboot. I've tried looking at other conf files in /etc/udev/rules.d/to see that there are no conflicts. I have two identical controllers at my disposal I've tried plugging them in one at a time. Adding to that, I've tried this with FOUR identical controllers, all of which work 100% plug'n'play in Windows 7. The controller's analog LED light lights up for a few seconds and then shuts off. Here's what lsusb -v -s 001:009 shows : pi@retropie:~ $ lsusb -v -s 001:009 Bus 001 Device 009: ID 045e:028e Microsoft Corp. Xbox360 Controller Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 64 idVendor 0x045e Microsoft Corp. idProduct 0x028e Xbox360 Controller bcdDevice 1.10 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 48 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 93 bInterfaceProtocol 1 iInterface 0 ** UNRECOGNIZED: 10 21 10 01 01 24 81 14 03 00 03 13 02 00 03 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 8 pi@retropie:~ $ All help appreciated. This is especially infuriating as I already got this thing to work once with one controller, tried to get it working with two controllers of the same kind, and it all went to hell. * one huge sigh * Am I completely on a wrong track here if I'm thinking that perhaps the device ID should be added into the boot config file or somewhere alike as separately blacklisted or as an USB HID exception? Or, does the actual problem run deeper somewhere on the Raspbian/Linux kernel level? That's what a lot of my attempts to search further into the USB HID device issues w/ Linux altogether would suggest. One plausible culprit might also be that since the controller ( http://piranha-gamer.com/product/piranha-pc-ps2-ps3-controller/ ) is listed as a "PC/PS2/PS3" controller, it might auto-select its operating mode accordingly between PC and PS mode upon being plugged to an USB port. Then again, that doesn't explain how it has worked earlier from time to time (or, should I say, from RetroPie update to RetroPie update) without any problems whatsoever.

@leitmotiv If I understood it more I would tell you. If it were just a discrepancy of a name for the driver of xbox controllers, but it seems to have other uses and I don't know if it even is a xbox controller driver. When enabled it creates an assigned number of virtual controllers, gamepads can be mapped through these and there is a technical guide to advanced controller mapping on the website here regarding these two things. It is not part of the core install, I think the xpad driver works for xbox controllers. Though I still don't know for sure if this is only of significance to player two or if at all. The way I think it applies to some of the controller problems is that player two will instead be a virtual controller and the controller that you'd like to be player two will instead be player 5 or something. But these things... there are a few layers and I know maybe 1/5 of them, you'll have to try uninstalling it at least and with luck control assignments will be naturally working for you.

@funkotron77 I have a feeling it is this alternate directory I mentioned. You should be able to find it by: sudo find /home/pi -name evdev_* find /home/pi -name reicast sudo find /opt/ -name evdev_* sudo find /etc/ -name evdev_* sudo find / -name evdev_* in that order, it is most likely in /home/, but i'm not an expert with using find. If you find this directory, there should be mappings somewhere and by my postulation you should find an evdev_xbox.cfg with the correct mapping for exit and none others.

@mitu I'm going to look at it thank you very much !

@Agustinb14 said in Controls don't work in retroarch or in console games: I can't seem to be able to bind 2 different hotkey keys for my controls but that's ok. At least I can play now. Only Player1 is able to access the hotkeys' functions - P2 cannot control them (including opening the menu). Glad you got it working in the end.

@Efriim I will share if I manage to get it to work though, I couldn't get the controller to get into the "Settings" initially till I found this thread and I followed it through. Now the challenge is to get it to work in the games.

@stoney66 Thanks for that. I had a look at those cfg files and they all looked fine. So I did a completely fresh install of RetroPie. Tried it out, R-Type controls worked fine. Then I started adding nice tweaks such as ES Themes etc, and suddenly R-Type had the same problem - P1 right not working unless I re-configure the MAME2003 controls every time. Not sure what change I applied that caused this, so I'm going to do it all again step-by-step and see when it reoccurs. My gut feeling is this is a bug in the Pimoroni Picade HAT drivers.

Yeah I wouldn't think so either, but it totally works with 6 button in Picodrive

Which is your budget? If you want something with top quality and wish to spend 30, 50 or more dollars, I'd recommend you any 8bitdo bluetooth controllers. These are great recreations of controllers from older consoles such as SNES, Mega Drive and NES. They even created a SNES controller with two analogs and two more shoulder buttons, just like a PS4 controller. However, if you don't want to spend more than 10 dollars per controller, I'd recommend you USB controllers from older consoles that you can buy on AliExpress. Here's some examples: NES USB - Around 3 dollars per unit SNES USB - Around 4 dollars per unit Sega Genesis USB - Around 5 dollars per unit Sega Saturn USB - 10 dollars per unit

To update you all. I did remove the SD card and deleted everthing on it. Downloaded the lastest linked version from https://retropie.org.uk and followed again the instruction to flash, install and start the retropie. I configured the gamepad, I enabled Wifi settings, I enabled SSH, I uploaded via WinSCP some roms and then started a GBC game and it works. I don't know, what we did last time different, but it works now. Hugh thanks to all which helps on this topic. Kind regards Bigwerth

@wiggy808 When you have the 2 X-Xarcade Tanksticks connected, exit ES and run from the terminal cat /proc/bus/input/devices then post the output here. If there are 4 joysticks/gamepads detected, then they're correctly functioning. Next, you can check in FBAlpha if the gamepads are assigned correctly to inputs by opening the RGUI (Select + X) and going into Configuration -> Input to check if each player has the gamepad assigned. You can change there the gamepad index for each player to see if all 4 players would work. What ROM are you using to test the 4 players ?

@leitmotiv You can use the same topic, it's up to you if you want to use another forum or not - you might try the AdvanceMAME forums.