search

Ryochan7 / DS4Windows

Like those other ds4tools, but sexier
https://ryochan7.github.io/ds4windows-site/
GNU General Public License v3.0
6.96k stars 807 forks source link

DS4 connects to controller but any inputs immediately cause a disconnection #1148

Closed CacheTellsStories closed 4 years ago

CacheTellsStories commented 4 years ago

He, new user here. i just installed and was disappointed to find that anytime I did anything on my controller it would immediately disconnect. Even slight joystick movements cause immediate disconnection. Is there a fix?

CacheTellsStories commented 4 years ago

Also, not using bluetooth, the controller is wired.

mika-n commented 4 years ago

Do you have Sony DS4 gamepad or some compatible 3rd party gamepad? Please provide the logile (%APPDATA%\DS4Windows\log or Logs tabpage text file export in DS4Windows app).

To generate more detailed debug logfile you might wanna download DeviceDetect debug version of the app. The debug version generates loooots of messages from a gamepad connection.. https://github.com/Ryochan7/DS4Windows/wiki/Troubleshooting#detailed-debug-log-file-from-gamepad-connection-problems

CacheTellsStories commented 4 years ago

It’s a ps4 controller. After additional testing I found that the controller disconnected after being connected to anything. It would connect to steam, then disconnect seconds or minutes later.

I also found that the controller might just not connect to steam or DS4, seemingly at random. I think this is more an issue with my computer, though any help you can provide would be awesome.

Also, thanks for the swift response.

CacheTellsStories commented 4 years ago

This one is the most recent. For some reason it was recognized as an XBox controller and disconnected only after launching a game, Destiny 2 on Steam.

2020-03-13 12:45:49.4329|INFO|DS4Windows version 2.0.12 2020-03-13 12:45:49.4329|INFO|Logger created 2020-03-13 12:45:49.7531|INFO|LinkedProfiles.xml can't be found. 2020-03-13 12:46:06.5670|INFO|Starting... 2020-03-13 12:46:06.5670|INFO|Connection to ViGEmBus 1.16.112.0 established 2020-03-13 12:46:06.5670|INFO|Searching for controllers... 2020-03-13 12:46:06.5670|INFO|Using Shared Mode 2020-03-13 12:46:27.0772|INFO|Found Controller: 90:FB:A6:F2:FC:7C (USB) (DS4 v.1) 2020-03-13 12:46:27.4262|INFO|Plugging in X360 Controller for input #1 2020-03-13 12:46:27.4625|INFO|Controller 1 is using Profile "Default" 2020-03-13 12:46:46.2288|WARN|Controller 1's latency over 10ms 2020-03-13 12:46:46.3080|INFO|Controller 1's latency now under 10ms 2020-03-13 12:47:01.0038|INFO|Unplugging X360 Controller for input #1 2020-03-13 12:47:01.0038|INFO|Controller 1 was removed or lost connection

CacheTellsStories commented 4 years ago

This is the one that disconnected after inputs

2020-03-13 12:04:17.2060|INFO|DS4Windows version 2.0.12 2020-03-13 12:04:17.2060|INFO|Logger created 2020-03-13 12:04:17.2299|INFO|LinkedProfiles.xml can't be found. 2020-03-13 12:04:18.4006|INFO|Starting... 2020-03-13 12:04:18.4006|INFO|Connection to ViGEmBus 1.16.112.0 established 2020-03-13 12:04:18.4006|INFO|Searching for controllers... 2020-03-13 12:04:18.4006|INFO|Using Shared Mode 2020-03-13 12:06:04.8506|WARN|WARNING: Failed to read serial# from a gamepad (0x054C/0x09CC). Generating MAC address from a device path. From now on you should connect this gamepad always into the same USB port or BT pairing host to keep the same device path. 2020-03-13 12:06:04.9125|INFO|Found Controller: D9:06:D7:40:00:00 (USB) (DS4 v.2) 2020-03-13 12:06:05.0092|INFO|Plugging in X360 Controller for input #1 2020-03-13 12:06:05.0092|INFO|Controller 1 is using Profile "Default"

mika-n commented 4 years ago

The xbox360 entry in the logfile doesn't mean the type of the physical gamepad you have. It is just the type of output virtual controller created by DS4Windows app and ViGem driver. This is defined in a DS4Windows profiles (xbox360 or dualshock4 output controller type). https://github.com/Ryochan7/DS4Windows/wiki/Settings

Do you have two different gamepads? One as DS4 revision1 and other one as DS4 revision2?

Anyway. The latter logfile dump you provided clearly shows that your PC has problems while reading data from the gamepad. This is usually sign of problems with usb cable or usb port in the gamepad. Try different usb cables because not all cables work with DS4 gamepad. I have several mobile phone usb cables here which can only charge the DS4 gamepad but cannot send any data signals. The same cable may seem to work in PS4 console because PS4 handles the usb connection a bit differently than PC. PS4 console uses BT connection as a "data line" even when the gamepad is using usb cable. PS4 uses the usb cable only to pair and charge the gamepad, but not for data communication.

Another way to test this theory is to pair the gamepad in PC with BT. https://github.com/Ryochan7/DS4Windows/wiki/Troubleshooting#gamepad-connection-over-bluetooth-bt

The debug app version would generate more detailed logfile

CacheTellsStories commented 4 years ago

I don’t have Bluetooth, unfortunately. I did test two controllers, one old and one new. Sorry, probably should have said something. I’m pretty sure it’s the cable.