@edmaul69 thanks for the quick reply

@herb_fargus said in Raspberry pi 3 and Xbox 360 controller:

Microsoft really should use a standardised protocol rather than their own proprietary stuff.

Apple's guilty of this all too often as well. Neither really likes to share with the rest of the class.

@rbaker gotcha, FBA is now working with a v0.2.97.39 romset and the Dualshock. Thanks.

nevermind, seemed to fix this by hitting fn f4 and then logging in with "pi" and "raspberry".

Would be good to have more information as mentioned here - https://retropie.org.uk/forum/topic/3/read-this-first - eg are you using a ps3controller / did you install the ps3 controller driver ? Please use code formatting when posting logs to the forum.

The error above happens I believe when the ps3controller driver is installed as the standard bluetooth daemon is disabled. The isue may be an update to the ps3controller driver which was in place for a day which had a bug. Try updating retropie-setup and removing/re-installing the ps3controller driver and repairing.

I can confirm everything is working again. Many thanks.

@edmaul69 thanks gonna try this!

Nothing I know of - and I don't have one of these controllers. I have a real PS3 controller which works well.

@afoldedpage

Were you able to get the 8bitdo controller working?

if they are connected, they are not showing up as input devices and I saw little in dmesg. output of cat /var/log/syslog after they are connected might give more info. (Use an external site for that log - it will be big)

I made it work with the following combination of hardware/software:

Raspberry Pi 3 Model B Operating System: OSMC (enable Bluetooth at MyOsmc-->Network) RetroPie 4.3 (installed using retroosmc) ps3controller driver configured for "clone support shanwan" (gasia will not work)

@igmothemagus this. Both controllers are not the same- the architecture of the new controller was moved to bluetooth because it was a simpler and faster band than the one they were apparently using for the original. There was a distinct attempt to brand this new controller as "Bluetooth", even at their E3 conference.

Of course, that didn't stop them from attempting to keep it as exclusive to their platform as they possibly could. The Linux kids are having all sorts of problems using it wireless via Bluetooth on their PC's. It's a mess.

@HansWursT619
R2 is the button I'm not able to get recognized on libreto emulators :_(
I will try with the cfg that farbird has posted

@AmigaGamer Seems this post is quite old, but I couldn't find other related post yet.
I encountered exactly same problem with you but I can't get this 8bitdo zero tool because official homepage has renewed. Do you still have the tool? If you don't mind, May I ask you to upload that tool on mirror?

Another step forward! These are my controllers default calibration values:

jscal -s 18,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,0,0,536870912,536870912,1,0,0,0,536870912,536870912,1,255,-4208,3952,21931,21931,1,255,-4208,3952,21931,21931,1,255,-4208,3952,21931,21931,1,63,-1023,1023,87367,87367,1,63,-1023,1023,87367,87367,1,63,-1023,1023,87367,87367,1,0,0,0,0,0,1,0,960,960,559240,559240,1,0,471,471,1139853,1139853,1,0,32767,32767,16384,16384 /dev/input/js0

And this pacifies the gyroscope's axis. I don't need them and they cause endless events if not "deadzoned":

jscal -s 18,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,0,0,536870912,536870912,1,0,0,0,536870912,536870912,1,255,0,0,0,0,1,255,0,0,0,0,1,255,0,0,0,0,1,255,0,0,0,0,1,255,-0,0,0,0,1,255,0,0,0,0,1,0,0,0,0,0,1,0,960,960,559240,559240,1,0,471,471,1139853,1139853,1,0,32767,32767,16384,16384 /dev/input/js0

Unfortunately there is no way to calibrate /dev/iput/event0, but /dev/input/js0 (jstest /dev/input/js0) is completely silent now if the gamepad isn't in use. This should be good enough for me, as even SDL might be forced to use /dev/input/js0 (export SDL_JOYSTICK_DEVICE=/dev/input/js0).

Next step would be to recognize for how long /dev/input/js0 showed no action. Any ideas?