DualShock 3/4 testers needed
-
@headcrab said in DualShock 3/4 testers needed:
Hi, unfortunately i can't make it work.
I have a rpi3, and an official ps3 controller.I noticed the bluetoothctl commands from the Gentoo wiki didn't work for me unless I omitted "agent on" and "default-agent". Maybe you can try again...
It's probably best to hold off on testing until a new firmware is released that includes rumble support (kernel uname build #1018 or later). The sixad daemon also has better compatibility with other BT peripherals now, so it's not so urgent to find a replacement driver.
-
@psyke83
I am not interested in rumble support.I mainly want to see if analog triggers are properly supported since sixpad doesn't.
See hereThe reason i want analog trigger support is that, moonlight-embedded started using SDL2 for controller mappings and triggers mapped as buttons don't work properly.
See here.I'll give it a try with your instructions and report back.
-
Your controller is using the hid-sony driver for the USB connection. If the analog triggers work on USB, then most likely they will also work via Bluetooth as it will be the same driver.
If you can't get bluetoothctl commands working as I suggested, temporarily install sixad, pair it, then uninstall and follow the steps I outlined in the OP once more. It's a pain, but it should work.
I'll be looking more closely at the driver when the new firmware/kernel is released.
-
@psyke83
Ok, now it worked, thanks for the tip.As for which driver is being used, i observed the following.
If i change xpad driver settings in /etc/modprobe.d/xpad.conf
triggers_to_buttons=0
It affects the way triggers are mapped with the ps3 controller. This happens either with usb connection or with the new BT pair mode.
So this leads me to believe that xpad is being used. I'm not experienced with linux though, so i might be mislead.
-
Works beautifully. Connects faster and without the annoying rumble. I have paired with two PS3 controllers and they can both coexist in the system. Awesome!
-
I managed to switch vom ps3controller wrapper driver to the one by BlueZ.
It directly uses the already created ES autoconfig from the wrapper driver.One thing I miss is the controller led's are not showing anything after connecting.
With the wrapper driver LED 1 was glowing permanently. -
The unlit led appears to be a driver bug that occurs only on first connect after boot. Unpairing and re-pairing the controller will show the LED correctly. It's still an issue on the latest firmware on stretch, too.
I'd prefer to use the BlueZ driver, but it has the unfortunate issue of not respecting the BlueZ IdleTimeout setting. I leave my Pi on constantly, so it's not useful to me in its current form.
-
Does the commit 99bdad7 change something to this connection mode? Or is it only for the ps3driver wrapper?
-
It should only affect the wrapper driver, mostly to improve compatibility with Raspbian stretch (which is not supported by RetroPie yet).
-
Hello! First, thanks @psyke83 for the great work on the ps3/ps4 controllers support in RetroPie.
What is the current status of the driver/procedure for latest RetroPie 4.4 on Debian Stretch to use ps3/ps4 controllers? Are the instructions in https://github.com/RetroPie/RetroPie-Setup/wiki/PS3-Controller still the preferred method at the moment to use these controllers?
Thanks!
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.