Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Another way to hide a controller from Steam:
Connect the controller
Steam > Settings > Controller > General Controller Settings
Select the controller under Detected Controllers > press the Options button (this is the 'Hide Device' command but if you're on the Steam stable client it won't be displaying the button for it)
Disconnect / reconnect and it should no longer show up under Detected Controllers (if you're seeing the Hide Device button, then hide process is automatic and won't require a dis/reconnect to see it's effect). If over BT, power cycle the controller so it goes back to DirectInput mode.
To undo the hide, you'll see Unhide Devices at the bottom of that screen.
This can depend how you have things set up for Rocket League, but I presume the issue you see is the mode the controller is in. Over BT the controller can be in a mode that follows DirectInput or another mode where it follows it's own PlayStation protocol. There is a bug in Steam that always switches the DS5 to PlayStation mode. If you hadn't been using Steam for controller support with the game, then RL would have been supporting it via DirectInput. Hiding the controller from Steam would resolve this.
If you found you had to use DS4W for the DS4 to work with RL, then check if you have PlayStation Configuration Support enabled (you'd want it disabled and then power cycle the controller). Hiding the DS4 from Steam should also resolve this though.
Now I have 3 questions about your response. 1, when you say to press "Options" in controller settings, do you mean Options on the controller or is there supposed to be an options button in the steam controller settings? I have no options button, hide or un-hide controller in steam settings.
2. Is it necessary to have hidhide? And do you think it could fix this issue? I seem to recall I was using it at some point for some reason but can't remember the last time I used it, or why, nor does DS4W give me the option to use it anymore. I just click "Hide controller" under settings and it seems to do the trick.
3. There is also a good deal of evidence here to say this issue is being caused by Steam, both from what you've said and my own experience. It happened before a long time ago, where I had to go into controller settings and disable all controller support to get things working. However, I have the same issue whether steam is running or not, is it possible for steam to affect things while it's not running?
And also, now that the DS4 is working perfectly, it sort of narrows things down to the individual controller. Do you think it could be faulty? I just bought this one like a week ago so I mean, it could be possible. It worked until yesterday though.
Thanks again for your help!
1. Options was referring to the button on the controller
2. If PS+Options was giving you Alt-Tab when Steam was running, then HIDHide (or using Steam's method of hiding the controller) should stop that.
Hiding with HIDHide will also help if the game is trying to use the BT DualSense while it's connected to DS4W. It shouldn't be necessary if the hide option in DS4W is functioning though. You can check with joy.cpl (windows key + R, type joy.cpl, OK). Does it list one controller or two?
3. Steam shouldn't affect things when it's not running.
I doubt the controller is faulty. I think the issue is between settings (but saying that I don't see how it'd stop working if things weren't changed, so maybe OS?) and what Rocket League natively supports but we'll see. :D
UPDATE:
Just been testing out Rocket League with a DS5 over BT and it worked fine for me. No Steam or DS4W, so it means the game has native support for the controller. It supports the controller in DirectInput mode (over BT, when you see any change to the lightbar compared to first connection, its in PlayStation/enhanced report mode*. Quit Steam or DS4W if running, turn it off/on and it'll connect and remain in DirectInput mode). Another way to check the mode, is if the controller functions with joy.cpl. (run joy.cpl, select the controller and click Properties). If it functions on the test screen its in DirectInput mode.
This doesn't concern USB only BT - over USB when its in enhanced mode its still compliant with DirectInput, but over BT it supports only one or the other.
*Seeing no change doesn't necessarily mean its in DirectInput mode though, for instance Steam or DS4W could be configured to set/leave the lighhtbar the same colour/brightness etc as when its first connected. If they're closed they won't be affecting things.
If things aren't working natively for you then we go in a different trouble-shooting direction.
If you normally play it with vibration you'll want to stick to controller support from DS4W (or could use Steam). You may also want to stick with DS4W for the controller shortcuts like the power off command or the remapping stuff.
So as I said, after leaving the controller plugged in to the PC for some time, it confused the DS5 for a DS4, the light turned from blue to white and started working just fine, as long as it stayed plugged in, still no BT. After some time, I had to remove the cord to charge my vape and lo and behold, the controller just kept on working fine on BT. So... this is not exactly the solution I was hoping for but, I'm not gonna complain since I didn't have to do much. Thanks again for your help, I'm still marking your comment as the solution since if it hadn't fixed itself in this wacky accidental fashion, I'm sure I would have had to go through your troubleshooting steps to fix it. I probably still will, this probably won't last forever.
Thanks again!
My DualSense trackpad directional swipe suddenly stopped working, but I figured out a fix.
I had this issue playing Horizon Zero Dawn Complete Edition on PC with a DualSense.
Trackpad click would work, but not directional swipe. Everything else was fine.
I was running the Horizon .exe as Admin. That's what "made it stop working" (or at least was a catalyst). Perhaps this speaks to a larger issue, I don't know - but my solution was to NOT run the game as Admin. Went back to working immediately.