I unplugged my microphone and this is the log I get now when I launch DS4Windows: As you can see in the following log, HID#17, referred to as HID-compliant headset, is actually my Blue Yeti. I also just found what was causing the UNKNOWN ID to appear in DS4Windows' Debug version. I wasn't even playing a game when it happened. However, my controller got disconnected again while it was just resting on my desk (it wasn't idle disconnect). At first I thought for sure that the solution had been found because I played for a long time without any disconnection. I also had some traces of SCPToolkit on my PC. Got really busy all of a sudden and since this bug happens randomly, it requires a bit of time to test each time. Thanks for the help, hopefully someone with a similar issue will be able to solve it in the future with the information in this thread. They might not even be caused by DS4Windows, could be my Bluetooth adapter or even Windows itself. Repeating the steps on the guide as he suggests proved ineffective to me, so I gave DevManView a shot at removing them and it seems to have worked.Īfter a few days of occasionally playing I haven't had disconnects again, only very rare latency spikes (once every few hours or so, lasting on average 2 seconds), but I'm fine with those. Though the steps suggested at first didn't yield any results, DevManView (which is suggested at the end of the guide to be used as a means of verification) not only detected the leftover registries, but also seems to have been able to get rid of them, even though nefarius doesn't suggest using it for that purpose. Turns out there was still residue from the installation, even though it didn't show up anywhere on my system. I had already done the steps you suggested before I installed Jays2Kings DS4Windows version, but decided to do it again just in case. Sorry for the late reply, had some things to take care of irl and it slipped my mind to update this thread. Then I tried closing the emulator and playing the same game I was playing before updating to see if it helped, but ended up getting the same result shortly afterwards. I turned it on once more and it reconnected, but the same thing happened again after another couple of minutes. I proceeded to configure everything and it all worked as intended, but after a few minutes playing my controller disconnected mid-play. I'd be still using the original fork of DS4Windows, but when I proceeded to configure profiles for some of my emulators I noticed motion controls for Dolphin weren't supported, so I looked for an updated version and found this fork, which supports it. I played over 1 hour with no issues whatsoever. Whatever is causing this issue could be related to it, because at first I was using the outdated version of DS4Windows by Jays2Kings and my controller didn't disconnect once. It just so happens that ViGEmBus which is used by Ryochan7's fork of DS4Windows is also partially made by nefarius. To get what I think is the most important bit of info out of the way, I've had this exact same problem with my old DS3 controller when using the updated SCPToolkit by nefarius (not the original ScarletCrush version). I've been getting the same error, but I'm pretty sure my DS4 is rev2, so it might not be related.Ī couple of things I can say that might help on pinpointing the issue: There might be way to make those fake copies work better, but someone with such a device should debug it. This same issue has been discussed several times in other issue posts and there is not much developers can do without actually having one of those fake copies on hand while debugging the issue. What ever it is then the debug version may tell a bit more why the connection is unreliable. These gamepads often have issues over BT connection (works just fine over USB, but BT is unreliable because of poor "BT radio"). Is this new gamepad or 5-6 years old DS4 gamepad? The thing is that Sony haven't manufactured those DS4 rev1 gamepads in several years after they released "fixed" DS4 revision2 gamepad.ĭo you have genuine Sony gamepad? During the last couple years there has been many fake Chinese wanna-be DS4 gamepad copies using the official Sony DS4 revision1 hardware ID. Based on the logfile you posted already tells that you have DS4 revision1 gamepad. Maybe the debug version tells more info in a generated debug logfile?Īnyway.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |