Yeah I unfortunately had to turn on post moderation thanks to spamming scum. I won't give them the satisfaction of abusing this platform for their fraudulent causes. Comes at the cost of regular users but what can I do. There's no staff of moderators so this solution has to do.

The blinking LEDs have literally zero expressiveness in Bluetooth functionality, it just means the controller doesn't get the or understand the packets sent to it to set the proper LED pattern, that's a Shibari issue I can not solve.

I have little knowledge and no hardware platform running ARM64 myself to test and verify so until someone can help me with that I'm afraid not.

I get the same error when trying to install the drivers on Windows 10 insider preview build 21286 (ARM64) VM running using Parallels 16 on a Macbook pro M1. Any ideas on how to get the drivers to install? I really want to use DS4windows and i'm stuck because I cant install the drivers. Is there an ARM64 version? Many thanks for your help, truly appreciate all the hard work you've put into this project!!

Capture.PNG image url)

@nefarius thank you dawg, i'm a complete noob so all this is new to me but I want to keep learning.

Bad news, doesn't seems to be a mini-USB connector problem, I tried 3 different cables and the problem persists.

I tried jiggling the cable but the DS3 doesn't disconnect.

I tried to replicate the problem on the desktop (by pressing buttons and shaking the controller), but it only disconected when playing games, a short time in the session.

if you install shibari as a service, then it'll start with the computer, and not show any UI, just output to the log file.

so it should just work on boot without any intervention.

@nefarius Thank you very much friend happy year, I hope and I know about the project I have that hope since the ps3 controller has a lot of potential, I know that anything can be achieved, you write to me privately, I am willing to support you, I also plan to advertise with a tutorial to the bthps3 so that more people know your work and appreciate it a lot (as I do right now)

Looking forward to this project reaching completion. I am attempting something a bit involved where I combine my arcade cabinet's DInput controls with optional wireless DInput controllers to get a top-level controllers. The process right now is multilayered and multifaceted since I have to use a combination of tools (Joystick Gremlin and XOutput) to get hide the physical hardware and get the virtual unified controller to show up on top. At any rate, I was forced to purchase DInput controllers in lieu of using my on-hand Xbox One ones because I cannot hide them from the XInput enumerated ones in the system. I am certain this will allow me more flexibility for my arcade configuration in going forward thanks to this.

@nefarius

I belive you completely and I understand the difference now, thanks for the links! 😊

Yes, Shibari handles vibration poorly. Since I'm cooking up a successor - again - I won't invest in fixing it 😉

Cheers

Get some sleep, mate 😘

TraceView Plus is what I use to read the trace files.

It's impossible to "destroy" hardware with just a driver swap (except in really really rare edge-cases that will not apply here) so heads up 😁

Start by sharing some more info and most importantly: screenshots of what your dongle is called, its hardware ID, what state it is in etc. you can gather all that info in Device Manager.

Cheers

EDIT: provide Windows version etc. Info, Info, Info!

Tough nut then I'm afraid. There aren't really tools I am aware of to troubleshoot this kind of issue.

@cornysz there will be soon-ish 😉

@notarobot hello!

I recently created a new site (that is still under construction) that is now hosted by GitHub: vigem.github.io and added the domain vigem.org as an alias that points over there now. The old Home repository became obsolete with that move so I deleted it (it only had one README anyway).

So maybe for you the old redirect is still cached by your browser or DNS?

Cheers