About the double input (controller) issue

DS4Windows does not magically transform your gamepad from one type to another. It creates a virtual gamepad that is associated to your real one. This means that if you have 1 real gamepad connected then windows will actually detect 2 gamepads. If 2 real then 4 and so on.

Bạn đang xem: Ds4windows

The image below shows how Windows behaves when a DS4v2 (Wireless Controller) is connected to the system while DS4Windows is emulating a Xbox gamepad:


If the game detects both the real and the virtual gamepad at the same time then it will receive commands from 2 different devices at every button press and stick movement, which can lead to the infamous double-input issue that can make games unplayable. Check the examples below:

GIF showcasing the double input issue (click to expand)


"Keep in mind that the "double input issue" encompass every problem related to 2 controllers responding to the same user" input, even if both controllers are not 100% mimicking each other


Problems caused by the double input issue (click to expand)

The game may:

Detect every command twice, making it unplayableStart 2 player mode randomlyIgnore the virtual controller because it picked the real controller firstRespond incorrectly to the controller"s inputsUsually happens because, even though the game is correctly reading the virtual controller, it is also incorrectly reading the real controller"s inputs at the same timeDo not respond to any controller commandUsually happens because the game detected the real controller first while being simultaneously unable to read its inputsOther non-obvious issues

To prevent or fix this issue it"s necessary to hide the real controller in order to make only DS4Windows" virtual controller visible to games. This can be done in two ways:

HidHide (recommended)DS4Windows" Hide DS4 Controllers option (legacy, non-recommended option)

Methods to prevent it

HidHide (recommended)

HidHide is a driver that acts as a barrier between Windows and game controllers connected to the system. It allows the user to selectively hide gamepads and only allow specific software to still detect them.

It is the recommended method because once it has been properly setup the double input issue is solved for good for the hidden controller.

Xem thêm: Lý Thuyết Trò Chơi Và Ứng Dụng Trong Kinh Doanh, Lý Thuyết Trò Chơi Và Ứng Dụng Trong Quản Trị

In DS4Windows case, the user needs to set HidHide to:

Hide the real controllers from the system once when connected via USB and once when via BluetoothAllow DS4Windows to see all hidden devices, otherwise it would think there are no supported gamepads connected
HidHide result


HidHide Configuration Client


Example: Hiding a DS4


This option exists on DS4Windows" Settings tab. When enabled, DS4Windows will kindly ask Windows for exclusive access to detected devices, meaning the later would only allow DS4Windows to detect the gamepads and preventing the double input issue.


The problem with this method is that Windows can deny the exclusive access request when another process already has a open connection to the gamepad. Common reasons for this request to fail are:

A game already is runningGoogle chrome/Opera is running (why does it have a connection to the gamepad you ask? A mystery)Nvidia Geforce experience process having a hold of the gamepadRandom non-obvious process having a hold of the gamepadetc

Even if it works initially, if your gamepad disconnects in the middle of a game chances are that you"ll lose exclusive access upon reconnection, requiring you to close the game to try again.

For the reasons explained above, the Hide DS4 Controllers option is NOT RECOMMENDED, though it remains available to users that need to use it for whatever reason. HidHide is the better option all around for those who can use it.

Xem thêm: Cách Chơi Cf Mobile Trên Pc, Hướng Dẫn Cách Cài Đặt Và Chơi Cf Mobile

Dedicated troubleshooting page

In case you really need to use this option, there is a dedicated troubleshooting page for the Hide DS4 controllers option that can be followed to verify why windows is failing to grant the exclusive access request.