A path with spaces on the command line must be surrounded by double quotes, that's no Shibari issue. Just fire up the application without installing it as a service and share what it outputs so people could actually see why it doesn't work instead of guessing. Troubleshooting one-o-one.

@MoltresRider welcome to the internet. Stop trolling or victimizing yourself, nobody falls for that around here. It's insanely disrespectful towards the volunteers floating around here to demand immediate attention and response times like you have some sort of enterprise SLA - which you don't. With free products comes the liberty of us to invest as much or as little time in free support as we please so stop acting entitled. This isn't Instagram. The nerve of some people these days... Cheers

From the looks of it, those are Bluetooth only drivers. Do you have anything that allows me to play using a cable plugged into the USB port? I have no Bluetooth card or anything Umm... FireShock? It is required to use BthPS3 anyway, since PS3 controllers pair via USB connection. Uses the same ViGEmBus/Shibari suite BthPS3 uses.

Yes, it's similar. I don't use glosc. I'm trying to reproduce it now. And there's a issue here. https://community.osr.com/discussion/291843/wdfchildlistupdatechilddescriptionasmissing-not-working-sometimes! When the problem occurs, mmc operating will hung, this is the dmp.

I've never heard of that error and I doubt that's all that's logged.

This error could literally mean anything... Just run the executable directly or at least have the courtesy to share some logs...

Where did you even get it and why did you tinker with it? I mean, I'm used to people ignoring every little bit of documentation I provide but what do I have to do next, a flashing, screaming banner? Or switch the repositories to private?

Once again: BthPS3 has nothing to do with the input and output of the controller, it handles the connection to Windows, nothing more, nothing less. Those issues are Shibari business and possibly there's some overlooked hack or trick that MIJ accounts for but I don't know of that and don't have the capacity to go after that so I can't really recommend any solution at this point in time. TL;DR: It is what it is Cheers

@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.

Has nothing to do with the functionality, try a complete reinstall. Shibari creates a log with information on what's happening, look at that and/or share it here, otherwise it's poke in the dark. Cheers

Hey hey! Odd, you can try to look in Task Scheduler, look for an entry named ViGEmBusUpdater and manually delete that. Then try running the setup again. Cheers

Ahoy! It's fixed for good now Cheers

@felagund cool! Glad to see my genius contributes to getting rid of SCP

Shibari is the culprit then Thanks for reporting, no ETA of any attempt to look into this though.

That's because the value is altered by the setup, not the INF since I didn't have the time nor interest to re-submit the driver for signing just for this change. I'll consider it in the future though, thanks for noticing.

@ComFreek not really, DI will come back into the game once additional features like pressure sensitivity arise since XInput is a static API, you can't present more axes and buttons than the specification provides, DI although allows that - with pitfalls but I've successfully implemented pressure sensitivity via DI in the lab.