@nefarius I think I'm getting it. As far as I know the mapping is in Sinks/Shibari.Sub.Sink.ViGEm.DS4.dll but I can't find a way to modify it. In your link to the source code I can see the mapping and where to change DualShock4Button.Share to DualShock4Button.Select (maybe, I'm not quite sure why it is like this. Nobody uses the share button ) I don't know what else to do with that .cs file or at least how to modify the .dll I really don't wanna use other software

I'm still not sure I understood but it looks like VDX might help your case, turning an XInput pad into a virtual DS4.

I tried connecting the second controller in question to my PS3, and it's stopped connecting to my PC as well.

I'm updating just in case someone is ever in a similar situation: Update: it seems that my DS4 doesn't properly work. Does the same when trying to use it on my Playstation 4. Also tried two different DS4 and they DO work as intended. I think my broken DS4 somehow forgets the last connected MAC address. The memory that stores this address is now volatile, making it remember the last MAC address while it still has some residual electricity, but forgets it the moment it goes away. It's similar to when the battery in a PC is gone, so the bios resets to default when you unplug the computer for more than a couple of minutes. I could workaround the issue by having some background process in Win10 that automatically removes the disconnected devices AND stays in a searchable status and accepts automatically to whitelisted MACs, that way I could connect the DS4 by just setting it in pairing mode (share+PS buttons). Any ideas about how to do that?

@Saroni81 said in Proper Installation + Removal Guide?: How do I update Vigembus and Fireshock? Just download newer releases and re-sinall? Or should I uninstall the older versions before installing newer ones? Just install the latest versions once released, will update previous ones. @Saroni81 said in Proper Installation + Removal Guide?: Besides, I am also using x360ce to configure buttons differently somtimes. But I cant find the PS3 Home button in x360ce. By any chance, is there a good key remapper for vigembus other than x360ce? It would be wonderful if it could also remap keyboard and mousemovements to the controller. Well and in the best case its free and opensource. The reason I ask you this, is, because maybe you also made a remapper but I could not find it. I'm not writing any remapping software because I'd like to stay sane by default the PS button is mapped to the X360 Guide button, Windows and/or Steam can "swallow" that so try to disable the Windows Game Bar thingy and close Steam or switch Shibari to emulate a DS4, then x360ce should be able to detect it. Cheers

Follow the SCP removal guide of this forum, it covers everything. SCP does exactly what you tell it to do, it doesn't fool with random devices. Cheers

I unfortunately don't know what build/commit that was since it wasn't a branch of mine, sorry! Anything that's not a proper git branch or pull request will get eventually lost, those who contribute should follow that, or things like these happen

quick question, are you sure it a cold start, or resuming from hibernation? Windows 10's default is a not a cold shutdown. try powercfg.exe /hibernate off in an elevated command prompt and then see if shibari works on the next reboot

Just found this topic after creating mine. Guess I'll just use the same solution and get that batch script. Thank you

Hey there, @nefarius wanted to report that the build you posted solved this issue for me as well! I was really sad when my MLB 11 PS3 controller was exhibiting this issue, but glad to see there was a fix for it. Will there be a new stable build of Shibari at some point? Thanks for reading!

Uninstalling and installing managed to solve the issue! Hopefully this problem won't occur to other people. Thank you for your time and effort spent on this software!

Did no see this post, i faced the same issue as well, https://forums.vigem.org/topic/473/ds3-once-rumble-vibrations-occurs-does-not-stop

That's a known issue, I have it on my list. It's related to some fake controllers not being happy with the timing they receive output packets. Watch the commits and news for updates on that.

fireshock and shibari, and vigem, working together, I think is the best solution around for PS3 on pc

perhaps try disabling hibernation. "powercfg /h off" in an elevated command prompt

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