With copy-cats this may not be true because of different serialKey. Genuine DS4 has a real MAC address and it is the same both in USB and BT mode, so DS4Windows app is able to identify when the hot usb->bt plugged pad is still the same pad. If the gamepad doesn't have a real hardware MAC address then something like that could happen because the on-the-fly calculated serialKey is different in usb and bt mode. Debug version makes it possible to change that byte via file, so it is easy way to test this with the latest "official" DS4 version without re-compiling the app.Īnother thing about hot plugging BT while the same pad was connected over USB also. This may need a change in DS4Windows base code. DS4 pad doesn't seem to care if this byte is F3 or F7 (could be that only the first two bits of the first half byte are used, so the firmware in genuine DS4 handles F3 and F7 the same way, but copy-cat firmware is a bit different. Or could be that those web pages with DS4 output report specs have been updated since the original version, but DS4Windows app was never modified to follow those new reverse engineering results.Īnyway, maybe the DS4 copy-cat firmware expect to see 0xF3 value there and simply go wooooow if the byte is 0xF7. I just tested the output byte with 0xF3 value with a genuine DS4v2 gamepad and it did seem to work. That specific output report byte has been 0xF7 for ages (probably since the days of the original Jay2Kings version). If the message structure seem identical then copy-cat must have a buggy/different/problematic firmware. If those messages are compared with a known working Sony gamepad then it might tell something if the message structure is somehow different. There is "HidReportInspector" debug tool to inspect closer those incoming and outgoing messages. I'm sure in many cases it would be possible, but someone with such a hardware should debug it. I guess none of the developers have those copy-cat gamepad devices, so it is difficult to debug and see how to make those work better (to see how the communication protocol differs from an official Sony gamepad firmware). So, if you purchase those cheap Chinese copy-cats then there is high risk of getting a problematic BT connection. web site has a list of other PS4 compatible device VID/PID values and brand names.īut, there are no lists of BT chipsets or BT dongles because it is next to impossible to keep it up to date (too many variations and the same BT dongle brand and model may have several chipset variations and users often don't know anything about those details and they don't report it here or anywhere else. Seems that i have same problem with DS4 copy-cat not changing color and not vibrating, i tried to use debug mode and changing values one by obe and both at the same time, nothing changed for me, i'm open to help with anything else i can do to solve it You should close and restart DS4WindowsDebug app while modifying the config file. This should tell which one of these output report bit fields causes the issue or is it a combination of these two. Then try only one of these values at a time (set other one zero) and see how it goes. At first try both 17 and 132 values at the same time. I'm not quite sure which of these options breaks the rumble support in the copy-cat pad while connected over BT.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |