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?
@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
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.
Hi,
@nefarius You're joking!
I just finished to do what I wanted to ^^'
I followed this 2 methods:
To allow everyone to restart the service : link text (Security Template method because I'm not familiar with command prompts)
To create a desktop shortcut: link text (to a PowerShell .PS1 script with only this command: Restart-Service Shibari.Dom.Server )
Now I know it was useless, but it was interesting to search how to do it... And maybe someday it will help someone...
Thank you for your answers and work again.
Sorry for my bad english (I'm french so everyone should understand why ).
Cheers!
@cnrez glad it's of use, especially when you're on a tight budget. I'm really interested in feedback of working aftermarket devices. I'll also provide a "how to debug the driver" guide document so anybody will be able to see what's happening under the hood (in 2020)
Cheers
You mean the DualShock 4? Are you running BthPS3 version 1.2.1? This contains a small fix. Shibari itself currently has no DS4 support.
I misread that initially, pardon me.
Check in Device Manager if the necessity devices are there, expand Bluetooth node and provide a Screenshot. You can directly paste images into your post btw. No need for slow loading tracking riddled trash like imgur
Ah you provided that already, damn, I need to wake up more it seems and this imgur garbage loads like in good old 56k times on mobile...
Cheers
@dissectionalone said in can the BthPS3 be used without fireshock and shibari?:
Edit: Sorted it out. Turns out the place from where I ran the exe didn't please it (The root of a flash drive) Once moved to the desktop it worked.
Addressed and fixed!
I had a few spare minutes (and Internet, yay) today and updated the setup to version 1.2.1 (link in original post) which sets the registry value correctly. No automatic updates yet, you'd need to grab and install by yourself, cheers!
