Then it’s just about getting the two to talk as you would do with a Dualshock 4 and PS4 console. Not all PCs and Laptops will have a Bluetooth receiver built-in, but it’s relatively easy to find one that will plug into your set-up. You can do this using any USB-Micro USB cable or connect the gamepad wirelessly via Bluetooth.
It’s what we’ve all been waiting for: Connect your PS4 DualShock 4 controller to your PC or laptop. If you’re still running Windows 7, you’ll also need to click ‘Install 360 Driver’.
Following this, click the ‘Install the DS4 Driver’ option, and the software will get to work making any plugged-in PS4 controller compatible with Windows 8, Windows 8.1, and Windows 10. Click on it, and from here, it’ll begin the set-up process until a pop-up menu appears, asking you to choose where you want your settings and profiles to be saved – all standard stuff. The downloaded file should be labeled as ‘DS4Windows.exe’. To download it, head to the DS4Windows website. It works by tricking your PC into thinking that the Dualshock 4 connected is actually an Xbox 360 controller, which is already compatible with a Microsoft product. That software is called DS4Windows, and as the name suggests, it has been specifically developed for this exact purpose. To achieve PS4 controller functionality on a PC, you’ll need the help of a piece of online software. Navigate to your controller’s manufacturer’s website and download the latest available drivers.
Or Type in your controller’s model into Google and also add drivers at the end.
NOTE: This issue is with Windows Standalone player and Windows Editor but not with UWP, since it uses completely different code to read input. So, this is another "band-aid" fix that attempts to mitigate the problem. Attempts to work-around the problem only seem to cause other issues or regressions, as was the case with this bug. This causes problems when multiple Xbox controllers are connected on Windows, since we don't know which UserIndex goes with which HID hardware ID, causing failures to read input properly. However, XInput only operates by a 'UserIndex" value and doesn't expose any kind of hardware ID, and so there's no way to reliably map a UserIndex with a HID hardware ID. The 2 triggers are combined to a single axis making it impossible to read them independently using HID, and instead the only way to read trigger input is via XInput. The core problem is caused by the way Microsoft choose to implement Xbox gamepads (Xbox 360 and Xbox One) on Windows, in that the left and right triggers cannot be properly read by the HID interface.
This bug is part of a much larger issue with InputManager that's been around for a long time.