Sony DualShock 3 - call for testers: "sixaxis" script module

Sano

@psyke83 For information, at first glance your sixaxis version works like a charm on newest 4.14.30 kernel.
I'll continue the tests, but no ghost input (unlike the native driver).
just had to remap my controller.

steeeb

On Shenwan Controllers I get a Timor Out error and need to plug and unplug it a few times to get it to pair the first time. But works good.

Also get a sixad.service could not start error on the Bluetooth screen.

Button mapping is better for those emulators that hard code button 1 and 2 which is now X and O instead of SELECT and I think L3.

Keep up the good work will happily help solve the Shenwan issues.

xadox

I have lost overview about this.

Is this new driver already in the 4.4 release?
Since I will try to install RetroPie for new on a Ubuntu 17.10.1 amd64.

Iriman

I'm having an awful time trying to sync my Shenwan controllers. It finds the controllers but then asks me to input a 6 digit pin number, which of course is not possible. Any recommendations?
Edit: I've tried all the different pair options that pop up when initially pairing and all of them are requiring a 6 digit pin. :(

sirhenrythe5th

@iriman had this input too with genuine PS3 Sixaxis Controllers. I just ignored the message and canceled the process when the input of the code was required.

The Controller works fine anyway, only issue is that i cannot configure the analog sticks in Emulationstation, but this will have nothing to do with the Bluetooth Connection

tupc10

Hello guys, are you planning to include the old configuration of the sixad driver named "Gasia-only"? I have a bunch of ps3 clone controllers that shows "SZMY PS3 Controller" when connected through usb and just work on BT when using the option "Gasia-only". Anyway, just thanks for your great job!!

psyke83

@tupc10 said in Sony DualShock 3 - call for testers: "sixaxis" script module:

Hello guys, are you planning to include the old configuration of the sixad driver named "Gasia-only"? I have a bunch of ps3 clone controllers that shows "SZMY PS3 Controller" when connected through usb and just work on BT when using the option "Gasia-only". Anyway, just thanks for your great job!!

The native sixaxis driver seems to have problems with pairing on Gasia clones, so this solution probably won't work. Until the problem is resolved, you'll be stuck with the ps3controller driver. I don't own a Gasia clone, so I can't do much to troubleshoot.

See: https://bugzilla.kernel.org/show_bug.cgi?id=200009

RetroPie on Raspbian stretch (without this PR) is quite messy for DS3 controllers at the moment. The ps3controller driver now has different button mappings to the hid-sony kernel driver (what the pad uses when connected via USB).

tupc10

I see @psyke83 , so this is bad news for me.. Thanks for your reply! Best regards

MadHorse

@psyke83 I have just one Gasia clone controller, but if can be of help I may send it to you.
If the shipment price is not too high it can be done.
Please let me know.

MadHorse

@psyke83 do you think it will be possible to integrate in the next release both the sixad driver and the sixaxis even if it's not working with gasia controller?
It seems to me that it is working much better than the sixad driver, it allows me to connect multiple controller without problem while the sixad driver it givesme problem very often.
Thank you very much

psyke83

This post is deleted!

psyke83

I've updated the PR with a potential fix for Gasia pads if anyone is interested in testing. The fix is specific to the customhidsony module which should get installed along with the sixaxis module, but you also need to manually install custombluez so that the BlueZ compatibility for third-party sixaxis controllers will work.

@MadHorse,

Unfortunately, sixad will interfere with the native driver, so both can't be used at the same time. We've no plans to remove sixad, however, so it'll always be available for manual installation. Perhaps the sixad daemon could at least be updated to use the newer controller button map so that it will better co-exist with the new driver, but I haven't touched that yet. In the meantime, I'd appreciate if you could test the PR.

Silent

I'm willing to give it a try soon with my 2 legimate DS3 controllers, but I have a doubt I'd like to clarify first - how is the situation with analog triggers? Normally they are not an issue but now with Steam Link being available for rpi and Retropie, and with Moonlight Game Streaming, lack of pressure sensitivity on triggers with a sixad driver is somewhat annoying.

edge3000

@psyke83 Thank you for your work on the sixaxis scripts!

After I setup a new Stretch build on my Pi 3B+ I found I could no longer get more than 4 dualshock3's to connect at the same time using the ps3controller driver. I installed your sixaxis PR and am happy to report I can get 5 official dualshock3's working great! I will borrow at least 1 more PS3 controller and do some more thorough testing to make sure 6player Xmen arcade still works.

Inputs seemed very responsive as if the input lag is reduced as well.

Thanks again!

Silent

So I removed ps3controller and installed sixaxis (rebased on the most up to date RetroPie-Setup) and ran into a weird issue...

After pairing my two legimate DualShock 3's I did not need to reconfigure them in EmulationStation, they worked as is! However, I can't get them to work in any of RetroArch emulators.

I tried removing all gamepads from es_input.cfg and it did not help - later I'll try resetting ES controls completely and maybe re-pairing the controllers.

What worries me is that nobody else mentions an issue like this... puzzling.

pjft

@Silent Have you tried re-configuring them in ES, though? That's what then sets up the controls in the remaining emulators - maybe there's something missing there, even though they paired and worked just fine?

Silent

@pjft Yes, I have. One thing worth noting is that libretro joystick configuration shows both pad 0 and 1 as "not connected".

That said, I'll try one more time.

EDIT:
I have repeated the steps (including removing es_input and re-adding onfinish action for it), and it works fine everywhere (including Retropie-Setup and runcommand), but not in game. Interestingly, when launching the game it says "controller connected" but no button works.

EDIT2:
An entry in retroarch-joypads is also being created, so I think there may be something I need to re-set in retroarch configs.

Silent

Update - I tried installing ps3controller driver again and it didn't even want to pair - but thankfully, I had a full SD card backup I made just before swapping drivers (guess I expected problems) and everything works flawlessly now.

So all in all, I am not using this driver yet, but I have a clean starting point I can re-try from at a later point. I'll make use of this opportunity to compare retroarch config files with what I remember from the "broken" install and see if I can find the difference.

EDIT:
I can't find any differences in config files (other than different files in retroarch-joypads, of course). However joypad assignments in Configuration Editor now show PLAYSTATION(R)3 Controller, as expected - after migrating drivers this menu claimed pads are not connected.

edge3000

@Silent Good call making a backup beforehand! The version of sixaxis and related scripts I am running is psyke83's PR test branch of sixaxis, its working great for me. I never had much luck with the up to date RetroPie-Setup version you tried.

These are the steps I did to install it, quoting from earlier in this thread:

@psyke83 said:

You need to be relatively comfortable with using the command-line to test.

These commands will enable the PR branch:
cd RetroPie-Setup
git remote add psyke83 https://github.com/psyke83/RetroPie-Setup
git fetch psyke83
git checkout sixaxis
Make sure to go back to the official branch after testing the PR! Uninstall sixaxis from the menu, then:
cd RetroPie-Setup
git checkout master

Silent

@edge3000 Then the steps are identical, the only difference is that I rebased this PR on top of up-to-date RetroPie-Setup because I didn't want to lose newest Setup features. I may try again without rebasing, however. After all, if it ends up working fine I can restore Setup back to master.