Follow this. Cheers

Or, just abandon SCP and use BthPS3?

Thank you!

I believe so, it's version 1.5.171 (latest entry on buildbot).

Hm, must consult the unholy SCP sources once again then. There's an invalid packet sent over BTH but I was a 100% confident that I fixed that in Shibari... hm, will take a 2nd look I guess

As I already commented in another thread the rumble code in Shibari (which is the responsible component) is not well tested and probably faulty. Watch the commits, if I get around to it I'll take a look at it.

I have Intel Bluetooth integrated in my laptop

@nefarius said in [Issue] - DS3 as DS4 : select button / touchpad: Here are the button mappings, a simple 1:1 relationship. Oh, good. But the touchpad click is not described here. It should look like this: {DualShock3Buttons.Select, DualShock4Button.Touch} ? P.S. I'm sorry to bother you, but I really want to continue playing Thank you for your work.

Never mind didn't notice the actual PS Button in the Nav controller is actually called, well, the "Ps" button fixed.

Sneaky glad you got it to work

Don't hijack threads please, especially already solved ones

Hi there, I came across this thread when I realized some strange behavior with my combo of FireShock / ViGEm / Shibari causing occasional BSoD or causing my USB Host controller to crash, in this state I couldn't plug any new devices into my machine via USB. I was running FireShock 3.0.0.0, ViGEmBus 1.16.116, and Shibari 1.5.171 as a service. When it worked, it worked great. But as I've been working on some video projects lately with long render times I had to uninstall it all so I wasn't risking system stability. I don't use Bluetooth with my DS3, just a MicroUSB cable. Right now I have all of the above still uninstalled, but I'd like to get it back in place as this seems like the best solution for straight-forward PS3 controller usage. Running Windows 10 Enterprise LTSC 2019, which corresponds to Build 1809. If it would help for testing, I can disable driver signature enforcement and try using the FireShock unsigned CI drivers 3.0.1.0 and see if I get similar symptoms. If there's a better combo of drivers / software for PS3 dualshock usage, I'm game to try anything. Edit: The error on the BSoD was DRIVER_POWER_STATE_FAILURE, seemed partially similar.

Oops, I should've documented that we indeed got it working! Hopefully I can continue on the work necessary soon!