keep connect and disconnect repeatedly via bluetooth and not detecting it at all via usb
ronnyc7th opened this issue · comments
Describe the bug
when connect with bluetooth it connect and disconnect immediately and asking to charge it and back to connect and disconnect and repeat
when connect to usb, ds4windows not detecting it even though I can use the controller without ds4windows
but I wanna use feature from ds4windows
the controller is 3rd party ds4
To Reproduce
Steps to reproduce the behavior:
- just connect with bluetooth like usual
- it said connected and disconnected and ask to charge the battery and back to connected and repeat the process
- the battery is charged so its not the battery
- it seems like it try to see the battery status but it cannot, so disconnect and back to connect it again (only my assumption)
- is there a way to bypass the battery check
Expected behavior
it should work just like normal cause my actual ds4 and my others 3rd party ds4 is working fine
Screenshots and Logs
I copy the text from the log
2023-11-18 17:10:48.9072|INFO|Found Controller: 20:22:11:25:02:8A (BT) (DS4 v.1).
2023-11-18 17:10:49.3172|INFO|Plugging in virtual X360 controller (XInput slot #1) in output slot #1
2023-11-18 17:10:49.3172|INFO|Associated input controller #1 (DS4 v.1) to virtual X360 Controller in output slot #1
2023-11-18 17:10:49.3323|INFO|20:22:11:25:02:8A failed CRC-32 checks 10 times. Disconnecting
2023-11-18 17:10:49.3323|INFO|Disassociated virtual X360 Controller in output slot #1 from input controller #1 (DS4 v.1)
2023-11-18 17:10:49.3364|INFO|Unplugging virtual X360 Controller from output slot #1
2023-11-18 17:10:49.3364|INFO|Controller 1 was removed or lost connection. Charge the battery
2023-11-18 17:10:51.3299|INFO|Found Controller: 20:22:11:25:02:8A (BT) (DS4 v.1).
2023-11-18 17:10:51.6725|INFO|Plugging in virtual X360 controller (XInput slot #1) in output slot #1
2023-11-18 17:10:51.6725|INFO|Associated input controller #1 (DS4 v.1) to virtual X360 Controller in output slot #1
2023-11-18 17:10:51.6725|INFO|20:22:11:25:02:8A failed CRC-32 checks 10 times. Disconnecting
2023-11-18 17:10:51.6725|INFO|Disassociated virtual X360 Controller in output slot #1 from input controller #1 (DS4 v.1)
2023-11-18 17:10:51.6725|INFO|Unplugging virtual X360 Controller from output slot #1
2023-11-18 17:10:51.6725|INFO|Controller 1 was removed or lost connection. Charge the battery
2023-11-18 17:10:53.6803|INFO|Found Controller: 20:22:11:25:02:8A (BT) (DS4 v.1).
2023-11-18 17:10:54.0205|INFO|Plugging in virtual X360 controller (XInput slot #1) in output slot #1
2023-11-18 17:10:54.0205|INFO|Associated input controller #1 (DS4 v.1) to virtual X360 Controller in output slot #1
2023-11-18 17:10:54.0205|INFO|20:22:11:25:02:8A failed CRC-32 checks 10 times. Disconnecting
2023-11-18 17:10:54.0205|INFO|Disassociated virtual X360 Controller in output slot #1 from input controller #1 (DS4 v.1)
2023-11-18 17:10:54.0205|INFO|Unplugging virtual X360 Controller from output slot #1
2023-11-18 17:10:54.0205|INFO|Controller 1 was removed or lost connection. Charge the battery
2023-11-18 17:10:56.0272|INFO|Found Controller: 20:22:11:25:02:8A (BT) (DS4 v.1).
2023-11-18 17:10:56.3659|INFO|Plugging in virtual X360 controller (XInput slot #1) in output slot #1
2023-11-18 17:10:56.3659|INFO|Associated input controller #1 (DS4 v.1) to virtual X360 Controller in output slot #1
2023-11-18 17:10:56.3659|INFO|20:22:11:25:02:8A failed CRC-32 checks 10 times. Disconnecting
2023-11-18 17:10:56.3659|INFO|Disassociated virtual X360 Controller in output slot #1 from input controller #1 (DS4 v.1)
2023-11-18 17:10:56.3659|INFO|Unplugging virtual X360 Controller from output slot #1
2023-11-18 17:10:56.3659|INFO|Controller 1 was removed or lost connection. Charge the battery
2023-11-18 17:10:58.3741|INFO|Found Controller: 20:22:11:25:02:8A (BT) (DS4 v.1).
2023-11-18 17:10:58.7114|INFO|Plugging in virtual X360 controller (XInput slot #1) in output slot #1
2023-11-18 17:10:58.7114|INFO|Associated input controller #1 (DS4 v.1) to virtual X360 Controller in output slot #1
2023-11-18 17:10:58.7114|INFO|20:22:11:25:02:8A failed CRC-32 checks 10 times. Disconnecting
2023-11-18 17:10:58.7114|INFO|Disassociated virtual X360 Controller in output slot #1 from input controller #1 (DS4 v.1)
2023-11-18 17:10:58.7114|INFO|Unplugging virtual X360 Controller from output slot #1
2023-11-18 17:10:58.7114|INFO|Controller 1 was removed or lost connection. Charge the battery
above is the log text for this particular 3rd party ds4
in the log file below can be seen that it work with my others 3rd party ds4 and my actual ds4 controller
ds4windows_log_20231119.0.txt
Desktop (please complete the following information):
- Controller 3rd party DS4 v.1
- OS: Windows 10 home 22h2
- DS4Windows Version 3.2.19]
Additional context
I think ds4windows cannot detect the battery so it disconnecting it and back to connect it again (only my assumption)
is there a way to bypass the battery check
2023-11-18 17:10:56.3659|INFO|20:22:11:25:02:8A failed CRC-32 checks 10 times. Disconnecting
This usually means either the controller isnt respecting the bluetooth protocol and sending packets correctly or that your bluetooth hardware in your computer is not good enough to keep up with the connection/you are too far away/there is interference of some kind.
Packets are getting corrupted and DS4Windows is ejecting the controller.
2023-11-18 17:10:56.3659|INFO|20:22:11:25:02:8A failed CRC-32 checks 10 times. Disconnecting
This usually means either the controller isnt respecting the bluetooth protocol and sending packets correctly or that your bluetooth hardware in your computer is not good enough to keep up with the connection/you are too far away/there is interference of some kind. Packets are getting corrupted and DS4Windows is ejecting the controller.
but it works fine via bluetooth without ds4windows
and ds4windows works fine with my other controllers
so the bluetooth in this particular controller is not compatible with ds4windows?
can it be make compatible?
above is the log text for this particular 3rd party ds4
Filing this as invalid then. I can only support hardware I own.
Log also shows the error lies with the CRC-32 detection failing. Would not be surprised if the controller does not even fill those bytes for the input report. But we will never know so no exception could be made.