Two PS3 controllers which used to work with SCPToolkit (1 working 1 not)
-
Also, I’m currently using vigem with fireshock, bthps3 drivers, and shibari
-
@chocolove said in Two PS3 controllers which used to work with SCPToolkit (1 working 1 not):
As reflected from the log, the controller with mac that starts with 02:... connects properly via BT, but for the controller with mac 06:..., it only connects using usb, then after disconnecting the cable, it fails with some error code.
I see now, indeed. Well, the FireShock exception is always there, that's "normal". But the controller doesn't even show up on the system wireless, what a bastard! I'll prepare a troubleshooting guide for the driver, as this unfortunately isn't trivial to the untrained
Cheers
-
@nefarius
Haha!
You’re quick!Cheers!!
-
@chocolove you're in luck, I'm just coincidentally lurking around
-
Haha. You’re the best!
-
Hi,
Happy new year nefarius.Just checking in if you have posted any troubleshooting guides anywhere?
If none yet, take your time.
-
Nope
-
That's alright mate. In your own time.
-
@nefarius Do you intend to support fake ds3 devices like in the scp days?
I'm asking this because I basically have the same problem as @chocolove.
The original ds3 works fine. The other one does not. I know the difference between them is the first byte sent to the device in order to get it to work.
I think original one uses a hid output report starting with 0x52 (raw request), but this fake I have wants a 0xa2 (output request)... at least in the scptoolkit code.
They have the same problem on linux.
https://github.com/RetroPie/RetroPie-Setup/pull/2263/commits/017f00f6e15f04b3272ff1abae8742dc4c47b608#diff-293af5b19ba1d1f50c86e8b9b0b1feaf -
@mmbossoni all devices I wanna support are already supported. If the reports differ that's not the business of BthPS3 but of Shibari or a function driver and I don't have the capacity to further dig into that with my current resources. So I guess no, I won't follow that route as long as I'm solo on this.
