search

Ryochan7 / DS4Windows

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

DS4Windows Is Buggy After Latest Release #2740

Open FOSSilizedDaemon opened 1 year ago

FOSSilizedDaemon commented 1 year ago

Describe the bug Since the last update for this program every single game that I play, emulated or not, completely brakes input. Whenever I press a button I will have ten to twenty seconds before anything is registered and often it will just throw the in-game character around as if I hit every single button my controller. I have tried every single recommendation to no avail. I have installed to %APPDATA%, I have installed to \Program Files\, I have tried removing DS4Windows completely, rebooting, and then reinstalling, I have tried using HidHide, I have tried using exclusive mode, I have tried using several different Sony Playstation 4 controllers, I have tried updating everything on my computer, I have tried clearing all cache, I have tried uninstalling all of my video games and then reinstalling them to see if that would fix it. Sadly, none of these worked. From playing around with different games it could be buggy emulated games screwing up my latency and it not creating when I swap to different games but I have had these issues when I play a session with only well tested and stable games.

To Reproduce Steps to reproduce the behavior:

  1. Get the latest install of DS4Windows.
  2. Install it.
  3. Connect your controller (I tried both wired and wireless, neither worked).
  4. Open any video game (I have tried playing emulated games for PS, PS2, PS3, Wii, NES, SNES and I have also tried playing games for PC neither worked).

Expected behavior I expect the game to register my controller and play normally.

Screenshots and Logs

12/21/2022 11:02:56: DS4Windows version 3.1.11
12/21/2022 11:02:56: DS4Windows Assembly Architecture: x64
12/21/2022 11:02:56: OS Version: Microsoft Windows NT 10.0.18363.0
12/21/2022 11:02:56: OS Product Name: Windows 10 Home
12/21/2022 11:02:56: OS Release ID: 1909
12/21/2022 11:02:56: System Architecture: x64
12/21/2022 11:02:57: Running as User
12/21/2022 11:02:57: Some applications may block controller inputs. (Windows UAC Conflictions). Please go to https://docs.ds4windows.app/troubleshooting/kb-mouse-issues/#windows-not-responding-to-ds4ws-kb-m-commands-in-some-situations for more information and workarounds.
12/21/2022 11:02:57: HidHide control device found
12/21/2022 11:02:58: Starting...
12/21/2022 11:02:58: Using output KB+M handler: SendInput
12/21/2022 11:02:58: Connection to ViGEmBus 1.17.333.0 established
12/21/2022 11:02:58: Searching for controllers...
12/21/2022 11:02:58: Using Shared Mode
12/21/2022 11:02:59: Found Controller: F4:93:9F:68:59:9E (BT) (DS4 v.2).
12/21/2022 11:02:59: Plugging in virtual X360 controller (XInput slot #2) in output slot #1
12/21/2022 11:02:59: Associated input controller #1 (DS4 v.2) to virtual X360 Controller in output slot #1
12/21/2022 11:02:59: Controller 1 is using Profile "Default". Battery level is 100%
12/21/2022 11:05:57: Controller 1's latency over 10ms (503.85 ms)
12/21/2022 11:06:01: Controller 1's latency now under 10ms

I took some time to try and only play stable games. Here is a log from that session (NOTE: I turned off my controller instead of killing DS4Windows so I could get the log).

12/21/2022 13:40:11: DS4Windows version 3.1.11
12/21/2022 13:40:11: DS4Windows Assembly Architecture: x64
12/21/2022 13:40:11: OS Version: Microsoft Windows NT 10.0.18363.0
12/21/2022 13:40:11: OS Product Name: Windows 10 Home
12/21/2022 13:40:11: OS Release ID: 1909
12/21/2022 13:40:11: System Architecture: x64
12/21/2022 13:40:11: Running as User
12/21/2022 13:40:11: Some applications may block controller inputs. (Windows UAC Conflictions). Please go to https://docs.ds4windows.app/troubleshooting/kb-mouse-issues/#windows-not-responding-to-ds4ws-kb-m-commands-in-some-situations for more information and workarounds.
12/21/2022 13:40:11: HidHide control device found
12/21/2022 13:40:13: Starting...
12/21/2022 13:40:13: Using output KB+M handler: SendInput
12/21/2022 13:40:13: Connection to ViGEmBus 1.17.333.0 established
12/21/2022 13:40:13: Searching for controllers...
12/21/2022 13:40:13: Using Shared Mode
12/21/2022 13:40:15: Found Controller: F4:93:9F:68:59:9E (BT) (DS4 v.2).
12/21/2022 13:40:15: Plugging in virtual X360 controller (XInput slot #1) in output slot #1
12/21/2022 13:40:15: Associated input controller #1 (DS4 v.2) to virtual X360 Controller in output slot #1
12/21/2022 13:40:15: Controller 1 is using Profile "Default". Battery level is 100%
12/21/2022 13:50:03: Gamepad data write connection is lost. Disconnecting the gamepad. LastErrorCode=995
12/21/2022 13:50:03: F4:93:9F:68:59:9E disconnected due to read failure: 0
12/21/2022 13:50:03: Gamepad data write connection is lost. Disconnecting the gamepad. LastErrorCode=0
12/21/2022 13:50:03: Disassociated virtual X360 Controller in output slot #1 from input controller #1 (DS4 v.2)
12/21/2022 13:50:03: Unplugging virtual X360 Controller from output slot #1
12/21/2022 13:50:03: Controller 1 was removed or lost connection

I ran into the issues before quitting my game and disconnecting. Desktop (please complete the following information):

Additional context I tried extensively to solve this myself, but I cannot. Therefore I am ready to farm this out to someone with more experience.

Ryusennin commented 1 year ago

That version of the ViGEm driver you're using is one year old.

The driver is supposed to auto-update, but in doubt you could try the most recent build: https://github.com/ViGEm/ViGEmBus/releases

FOSSilizedDaemon commented 1 year ago

That version of the ViGEm driver you're using is one year old.

The driver is supposed to auto-update, but in doubt you could try the most recent build: https://github.com/ViGEm/ViGEmBus/releases

I updated and will try it out. Thank you, will report back if it is fixed.

FOSSilizedDaemon commented 1 year ago

That version of the ViGEm driver you're using is one year old.

The driver is supposed to auto-update, but in doubt you could try the most recent build: https://github.com/ViGEm/ViGEmBus/releases

I believe that fixed it, thank you. Any recommendations on how to have these check for updates automatically?

Ryusennin commented 1 year ago

Normally you should be all set. Since version 1.18, the ViGEm driver auto checks again for updates (it was disabled in 1.17).