

New tools and techniques will have to be introduced to work around problems. More problems are also being created in an attempt to create a more integrated experience with certain software suites the Steam update that enabled Xbox Configuration Support will be a hurdle for all other mapping programs for the foreseen future. More software is being discovered that causes problems with the old way of doing things. This situation can be frustrating and hard to diagnose. I didn't read any hostility from your post. That method helped me find out that even something as mundane as the Windows Store app can cause exclusive mode to fail. Please check out his post and run the procedure in Process Explorer. Especially as more applications are being discovered that cause exclusive mode problems, it really makes the old "Hide DS4 Controller" option less useful and it makes HidGuardian more important.Īnother thing to mention is that mika-n found a way to determine which program currently has an open handle on a device and causing exclusive mode to fail. One big culprit that seems to be affecting people lately is ShadowPlay.

Just stopping and starting DS4Windows might not be enough if some program still has an open handle on the DirectInput controller. No matter the method used to get exclusive mode working, you will likely need to disconnect and re-connect the DS4 controller to make sure the changes take affect. The problem is still not directly caused by DS4Windows though so there is no reason to re-open this issue. I learned that Steam was not the culprit when I made my last post two weeks ago. This issue was initially closed when I thought the problem was caused by a Steam update made around that time.

The problem ended up being with the game as documented by other people. I had made a couple of changes affecting keyboard emulation so I was thinking that might have caused issues. It worked once and after I restarted horizon 4 it doesnt go exclusive mode even once, sadly. (Hide-DS4-Controller-config-option)-tips-and-issuesĪre done already, still fails to open in exclusive mode. I even disabled nvidia overlay, the rest of the steps from here It's pretty awkward as I haven't done anything else than starting Horizon 4 and Hide DS4 Controller won't work anymore. Given that I do tick Hide DS4 Controller.Īfter game restart (i had to switch graphics settings) the problem is back, can't Hide DS4 controller to work and it keeps quickswitching It's possible that it could've worked before with Hide DS4 Controller, but on previous versions of DS4Windows it was impossible for me to enable that, well it was, but the controller wouldn't connect, I just updated to 1.7.1 and it works flawless. Good news - it's not quickswitching at all and works perfect, just as on BT when Hide DS4 Controller is ticked!
