perhaps try disabling hibernation.

"powercfg /h off" in an elevated command prompt

Thanks, I will try !
Edit : work great, thanks.

Hello!

I don't want to hijacked this thread, but i have this EXACT same problem.
My controllers (one fake, one genuine) are working with a cable, but when i connect them over bluetooth, the controllers are detected (led in the controllers, device manager too) but no input detected in games or with the Windows tool..
I have an Intel AX200 card, so my bluetooth version is 5.1.

Shibari window when i connect my genuine PS3 controller: 2020-06-08_14-56-44_Shibari_Dom_Server.png

Device manager:
2020-06-08_14-58-46_Gestionnaire_de_périphériques.png

Thanks, and have a nice day!

yes, that´s what i tried but it doesnt seem to work

ok yeah that's fair. guess i'll see if I can get SCP working again

Since auto-pairing has been implemented the PowerShell commands became obsolete and do nothing anymore.

Please do, without the log there's little to recommend.

Cheers

Follow this.

Cheers

Or, just abandon SCP and use BthPS3?

Thank you!

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

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.

TL;DR: vibration/rumble over Shibari isn't really that well tested and I bet it's way from perfect.

@feiplane said in [Issue] Weird rumble behaviours on epsxe and pcsx2:

I remembered things were normal when using scp drivers/motioninjoy on win 7/win xp, the rumble are just normal as console liked vibrations especially with directinput configuration, but it's weird now with xinput, why no more directinput support on win10?

There was definitely no DirectInput rumble support via SCP. SCP and PCSX2 in combination with the modified LilyPad plugin is probably what you meant/experienced.

@feiplane said in [Issue] Weird rumble behaviours on epsxe and pcsx2:

the vibration just worked with xinput configuration, no vibration at all with directinput(button mapping ok) on pcsx2 whereas epsxe cannot detect the ds3 at all with directinput configuration.

Shibari (using ViGEm) doesn't expose anything DirectInput related in regards to rumble, it works via XInput only.

Cheers