![]() Definitely try the debug version of DS4Windows that has mentioned to see what HID devices are being enumerated and make sure the Strikepack FPS dominator DS4 is being seen. In your case, it looks like your computer is recognizing the controller already as an HID device. In my environment, it did not work right away because I was using other software/drivers to get it to work (specifically ScpToolkit) and it prevented DS4Win from picking up the controller as an HID device. ![]() Yep, in #882 I also requested support for the Strikepack FPS dominator, but it turns out it's already supported through the CronusMax device handle. Just chiming in here to add to what already mentioned. cose the debug DS4Win app and re-launch it when changing a gamepad connection). Do separate debug generation while connecting the gamepad with USB and BT (ie. ![]() Run the deviceDetect debug version as instructed in the Troubleshooing documentation page and please provide the logfile (content of Logs tabpage in DS4Windows). The debug version will generate loooots of detailed messages about detected gamepads and HID devices and how it goes when DS4Windows tries to negotiate a connection to a gamepad device. If the gamepad really doesn't work in your PC then maybe you should try to run a special debug version of DS4Windows app. See this post about CronusMax tests: #702 However, in this case it worked only if CronusMax was set to use the gamepad in PS4 mode in Cronus settings. In your case "HID\VID_054C
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |