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 was archived by the owner on Mar 5, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 5, 2026. It is now read-only.
[Enhacement] Disable HidHide hiding for devices using native profiles #68
Many newer games have built-in support for the Dualsense controller, and sometimes it’s desirable to use a “Native” profile to fully utilize the Dualsense capabilities. "Native profiles" refer to those that do not spawn a virtual controller.
However, when such profiles are loaded while HidHide is used for hiding, the real controller remains hidden unless it is manually removed from HidHide's hide list. Similarly, if DS4Windows loads a profile that spawns a virtual controller, the real controller is not hidden, leading to potential double-input issues. Again, this requires manual intervention in HidHide.
Since the HidHide CLI supports adding/removing specific devices from the filter, it would be convenient if DS4Windows could automate these processes. Specifically:
Unhide the real controller when loading profiles that don’t have an associated virtual controller.
Hide the real controller when loading profiles that have an associated virtual controller.
@floysh - I can relate to this situation and just want to describe a current "workaround" that works reasonably well for me (with one annoying downside described below.)
TLDR; This is sort of not an issue if you disable HidHide alltogether and create a Default "passthrough" profile in DS4Win which doesn't emulate a controller. Then use Auto profiles to load a profile that emulates XBOX / PS4 and set it to load only for games that don't natively support the Dual Sense.
I use a Dual Sense Edge for reference but the following should apply for the regular Dual Sense as well.
1 - I completely disabled device hiding of in Hid Hide (untick checkbox "Enable Device Hiding"
2- In DS4Win I created a "Default" load profile which does not spawn a virtual controller (tick "Disable Virtual Controller)
-- I use this profile for mapping KB macros and Virtual mouse etc. I also use it for special actions.
-- I unbound all normal controller buttons from this profile (I don't think this is really needed)
-- Using this profile for all Games that natively support the Dual Sense (Edge) allows you to use all (if wired) or most (if wireless) functionalities of the dual sense controller, without any double input of a virtually spawned controller.
-- The only downside here is that whenever I trigger macro or special action the game will read the normal controller action in addition to whatever the macro sends. With the DSE controller this isn't as much a problem, since there are many buttons which can be uses exclusively for macros without triggering game input. Example: I play a game where the map opens by pressing "options". I configured a macro which when pressing FN Left plus "options" is supposed to Alt Tab the game. Now the macro correctly fires but the game will also read the options from the game input and open up the map in game.
3- I then created a separate Profile in DS4Win which spawns an XBOX controller.
-- I use the Auto Profiles feature to automatically load this profile whenever a game that does not support the DSE controller natively is in the foreground
-- In 99 percent of all cases this avoids double input, since even though the real controller is not hidden, the game that you are playing is not supporting the DSE natively and would therefore not read any input from it. For example when playing Starfield, even though both controllers are now visible in control panel, Starfield will only read the virtual Xbox controller
-- Steam Input could mess with this logic but that's why I disable that (see next steps)
-- Finally in pretty much all other cases where let's say both controllers are recognized and you would rather play with the XBOX controller rather than DS, these games / emulators typically would allow you to select which controller to pick (eg. FFXIV).
4- I also completely disable Steam Controller Input for most cases. This could be skipped or you could decide to use Steam Controller input instead of step -3- but I would never recommend that.
The alternative to the above that also sort of worked for me was to invert the hide list for Hid hide and add games that read your virtual controller to the now "black list". But that was much more hassle than it was worth.
hey @zeanogit i always did the same and yeah its all awesome but it actually isnt the moment you try to multitask (like game and music apps) with alt tab binded to the controller, with a program like joyxoff (because its literally the only good software with a keyboard for gamepad), when ds4windows has to turn on and off the gamepad emulation during game (native dualsense) and music app (x360c emulation) it always bugs out and crashes and that really sucks.
DS4Windows never did the task of disabling HidHide for specific devices because IIRC that is what Nefarius wanted. That task was supposed to be done through the HidHide Configuration Client manually to make diagnosing HidHide problems easier for him. That does not matter now though.
Activity
kareem007g commentedon Mar 1, 2025
there is a problem with hid hide , not active. when enable hid ds4 controller option .
#66
zeanogit commentedon Mar 2, 2025
@floysh - I can relate to this situation and just want to describe a current "workaround" that works reasonably well for me (with one annoying downside described below.)
TLDR; This is sort of not an issue if you disable HidHide alltogether and create a Default "passthrough" profile in DS4Win which doesn't emulate a controller. Then use Auto profiles to load a profile that emulates XBOX / PS4 and set it to load only for games that don't natively support the Dual Sense.
I use a Dual Sense Edge for reference but the following should apply for the regular Dual Sense as well.
1 - I completely disabled device hiding of in Hid Hide (untick checkbox "Enable Device Hiding"
2- In DS4Win I created a "Default" load profile which does not spawn a virtual controller (tick "Disable Virtual Controller)
-- I use this profile for mapping KB macros and Virtual mouse etc. I also use it for special actions.
-- I unbound all normal controller buttons from this profile (I don't think this is really needed)
-- Using this profile for all Games that natively support the Dual Sense (Edge) allows you to use all (if wired) or most (if wireless) functionalities of the dual sense controller, without any double input of a virtually spawned controller.
-- The only downside here is that whenever I trigger macro or special action the game will read the normal controller action in addition to whatever the macro sends. With the DSE controller this isn't as much a problem, since there are many buttons which can be uses exclusively for macros without triggering game input. Example: I play a game where the map opens by pressing "options". I configured a macro which when pressing FN Left plus "options" is supposed to Alt Tab the game. Now the macro correctly fires but the game will also read the options from the game input and open up the map in game.
3- I then created a separate Profile in DS4Win which spawns an XBOX controller.
-- I use the Auto Profiles feature to automatically load this profile whenever a game that does not support the DSE controller natively is in the foreground
-- In 99 percent of all cases this avoids double input, since even though the real controller is not hidden, the game that you are playing is not supporting the DSE natively and would therefore not read any input from it. For example when playing Starfield, even though both controllers are now visible in control panel, Starfield will only read the virtual Xbox controller
-- Steam Input could mess with this logic but that's why I disable that (see next steps)
-- Finally in pretty much all other cases where let's say both controllers are recognized and you would rather play with the XBOX controller rather than DS, these games / emulators typically would allow you to select which controller to pick (eg. FFXIV).
4- I also completely disable Steam Controller Input for most cases. This could be skipped or you could decide to use Steam Controller input instead of step -3- but I would never recommend that.
The alternative to the above that also sort of worked for me was to invert the hide list for Hid hide and add games that read your virtual controller to the now "black list". But that was much more hassle than it was worth.
foss-lover34 commentedon Apr 7, 2025
hey @zeanogit i always did the same and yeah its all awesome but it actually isnt the moment you try to multitask (like game and music apps) with alt tab binded to the controller, with a program like joyxoff (because its literally the only good software with a keyboard for gamepad), when ds4windows has to turn on and off the gamepad emulation during game (native dualsense) and music app (x360c emulation) it always bugs out and crashes and that really sucks.
Ryochan7 commentedon Apr 9, 2025
DS4Windows never did the task of disabling HidHide for specific devices because IIRC that is what Nefarius wanted. That task was supposed to be done through the HidHide Configuration Client manually to make diagnosing HidHide problems easier for him. That does not matter now though.