You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 24, 2021. It is now read-only.
Tried to connect via BT and USB, win10 see ds4 as wireless and successfully recognize it, but controller doesn't appears in steam big picture controller configuration window or in Devices and Printers > RMB > Game controller settings > Advanced > Preferred device pop-list
Also I tried enable verbose log in ds4windows settings > Device Options Enable verbose log, stop and start server and controller's VID and PID is 0x0000
Tried connect controller to another pc and it works fine in both steam and ds4windows
Any suggestions or help? Tutorials from google and yt also no help me.
The text was updated successfully, but these errors were encountered:
It's a little bit tricky paring DS4 with Windows. What am I did was first connect DS4 via USB and Windows installed the OEM driver for DS4 controller (it works perfectly and I see them in devices) . Then I use this tutorial for pair DS4 with my laptop via BT https://www.youtube.com/watch?v=N7DUV4T8744 . Then controller is stable and not auto disconnected :) .
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Tried to connect via BT and USB, win10 see ds4 as wireless and successfully recognize it, but controller doesn't appears in steam big picture controller configuration window or in Devices and Printers > RMB > Game controller settings > Advanced > Preferred device pop-list
Also I tried enable verbose log in ds4windows settings > Device Options Enable verbose log, stop and start server and controller's VID and PID is 0x0000
Tried connect controller to another pc and it works fine in both steam and ds4windows
Any suggestions or help? Tutorials from google and yt also no help me.
The text was updated successfully, but these errors were encountered: