Steam client is stealing dualsense controller inputs /forcing blank playstation support.

[XDeadzX]

ISSUE

While the steam client is running, the playstation 5 controller will not be read as a valid input device in steam games (and a few non-steam games) wired or wireless.

OS
Windows 10 22h1

STEPS

Open the steam menu
Head to options
Under controller settings, disable playstation support.
Load games with dinput support but not dualsense support
(tested games include Monster Sanctuary, Totally Reliable delivery service(TRDS), Katamari Damacy REROLL, and Outer Wilds for broken games on steam. Non-steam games include Totally Reliable delivery Service, and Outer Wilds on microsoft store)
Exhibit the games not responding to controller inputs 1-2 seconds after the game starts.

If running a game not on steam that is only dinput and not dualsense enabled (TRDS), the game will not read the controller as long as steam is running.


Another tell is with playstation support disabled, the dualsense controller will read as player 1 instead of blank player numbers. Without the steam client running, the player numbers will remain blank and the controller will operate as expected.

RESULTS

Controller is non-functional for majority of games while running the steam client.

EXPECTED

Controller works like it did prior to the june 17th(?) build. Enables dinput in games, recognized as a playstation controller, etc.
____

I noticed this at the beginning of july, having last played at the end of may. I've fiddled around a bit to figure out what the cause was, but the ultimate fix was to turn off steam. This is obviously a no-go for the games I own on steam... Enabling playstation support solves it but limits me to using steam's desktop profiles, xbox button prompts, and xbox limitations in the games (eg. no native touchpad.)

[Cortex]

Exact same issue, occurred after seeing the firmware update prompt, downloading and updating controllers.

This is occurring in any game which previously worked fine, have also tested the EGS versions of Rocket League, GTA V, Hitman 3, and Dead Cells, and they all work correctly on EGS, as they did on Steam prior to this issue appearing.

The controller will function if I enable "Playstation configuration support" under controller settings, but this is sub-optimal as it resets bindings, and introduces input lag.

[codemonkey]

Same problem. DualSense doesn't work at all when Steam is on. Something seems wrong around the time of the firmware update.

[tintingaroo]

I had encountered the issue during the beta but for me it was OK if wired, problem was when over BT.
https://steamcommunity.com/app/353370/discussions/1/4932019356830138029/

I think over USB the controller is compliant to both PlayStation protocol and DirectInput (concurrently?? or can easily switch??), but over BT has to be one or the other.

I didn't upgrade the firmware - don't know if that makes any difference in the wired experience.

[Falbaling]

Can confirm the issue (Using PS5 DualSense with Bluetooth).
Started on my end with the 27 July Steam client update.
Still worked outside of Steam while Steam was started before that.

[TehSpoopyKitteh]

To get around this, I typically turn off Steam Input via the controller tab in the affected game’s properties window. I’ve done this for Untitled Goose Game, and RetroArch.

Same problem appears to happen with Xbox and XInput controllers as well that natively use XInput in the first place.

[tintingaroo]

Just saw the Reddit post regarding the issue and realised I never posted a workaround in the actual bug report... So for the Steam peeps, how to manually add the controller to Steam's blacklist: https://steamcommunity.com/discussions/forum/1/3464975249570878405/#c3464975249571183239


There are other workarounds with their own pros / cons. Could use just HIdHide and get a similar result as adding to the blacklist, or combo DS4Windows & HidHide and still be able to use the controller with the Steam client (would lose rumble since it's not supported when DS4W is emulating a DS4).

[Cortex]

Originally posted by tintingaroo:

Just saw the Reddit post regarding the issue and realised I never posted a workaround in the actual bug report... So for the Steam peeps, how to manually add the controller to Steam's blacklist: https://steamcommunity.com/discussions/forum/1/3464975249570878405/#c3464975249571183239


There are other workarounds with their own pros / cons. Could use just HIdHide and get a similar result as adding to the blacklist, or combo DS4Windows & HidHide and still be able to use the controller with the Steam client (would lose rumble since it's not supported when DS4W is emulating a DS4).

Thanks a bunch! Working perfectly after applying this fix, wireless or wired.

[XDeadzX]

Originally posted by tintingaroo:

I didn't upgrade the firmware - don't know if that makes any difference in the wired experience.

It may be apart of the problem, however I updated as soon as the windows utility released, and it had worked for at least a little while following the release of the 297 firmware. Wired and wireless both broke at the same time for me.

The blacklist feature does help as a workaround, but sadly it's still less than ideal and doesn't return to previous state of being able to use chords while not enabling in-game support/steam input.
Volume chords, play/next track chords, and the ability to turn off the dualsense controller with a button press are just such nice comfort features. Xbox still functions this way, with support not required to operate chords.



But to contribute more/new information, the same controller works perfectly fine on steam deck in game mode. Including standard playstation icons in games the two deck games I tried them on. So it doesn't appear to be the controller/firmware at fault. And as previously stated, closing steam causes the controller to return to normal function for non-steam games on windows still.

[tintingaroo]

Aye, a workaround and not a fix - gotta wait for Valve to address / advise.

A workaround that gets things closer to the correctly working experience is to hide the DualSense and present to Steam an emulated DS4 via DS4Windows or DualSenseX etc. There are pros and cons between those two remappers and their emulated DS4.

[tintingaroo]

I've been looking at the code in SDL2. It's well commented so it's easy to get a grasp of what its doing and I see where I want to play about with. Problem is I don't know how to modify the dll Steam uses / make it compatible with Steam. :(

https://github.com/libsdl-org/SDL/blob/main/src/joystick/hidapi/SDL_hidapi_ps5.c
lines 704 - 722
We want to end up in the ELSE but we're meeting the condition in the ELSE IF??? First test I'd do is set enhanced_mode to false in the ELSE IF then see if the controller stays in simple mode... If it doesn't, set enhanced_mode in the ELSE to false and see what happens... Then try to figure out how to use DEBUG_PS5_PROTOCOL, maybe check out line 696...

[Rev]

Originally posted by tintingaroo:

I've been looking at the code in SDL2. It's well commented so it's easy to get a grasp of what its doing and I see where I want to play about with. Problem is I don't know how to modify the dll Steam uses / make it compatible with Steam. :(

https://github.com/libsdl-org/SDL/blob/main/src/joystick/hidapi/SDL_hidapi_ps5.c
lines 704 - 722
We want to end up in the ELSE but we're meeting the condition in the ELSE IF??? First test I'd do is set enhanced_mode to false in the ELSE IF then see if the controller stays in simple mode... If it doesn't, set enhanced_mode in the ELSE to false and see what happens... Then try to figure out how to use DEBUG_PS5_PROTOCOL, maybe check out line 696...

from my coding knowledge, if you're trying to end up in a certain condition, try fronting that condition to the top of your loop so it has precedence

[Balderick]

Steam Input used to have GUI to map buttons and gave option to save any layout as any controller type. i.e. a PS5 controller layout could be saved as a PS4 type controller. I used to get blank layout with Thrustmaster T500 RS wheel and pedals but could save buttons on wheel and wheel base as PS3 to get Steam/desktop navigation using buttons on wheel outwith game running.

Am sure this could have helped in this and other scenarios. My cloud gaming vm uses virtual gamepad driver which Steam refuses to change saved controller type and cannot change controller type as Valve completely removed the GUI to do so.

The GUI used to look like
https://steamcommunity.com/sharedfiles/filedetails/?id=2546024083
and the save controller type option
https://steamcommunity.com/sharedfiles/filedetails/?id=2546035537

[stili]

Originally posted by tintingaroo:

Just saw the Reddit post regarding the issue and realised I never posted a workaround in the actual bug report... So for the Steam peeps, how to manually add the controller to Steam's blacklist: https://steamcommunity.com/discussions/forum/1/3464975249570878405/#c3464975249571183239


There are other workarounds with their own pros / cons. Could use just HIdHide and get a similar result as adding to the blacklist, or combo DS4Windows & HidHide and still be able to use the controller with the Steam client (would lose rumble since it's not supported when DS4W is emulating a DS4).

Seems like it doesnt work for me :( Wired and BlueTooth no success :/

[tintingaroo]

What is happening for you @stili? Steam is still detecting and displaying the DS5 on the Controller Settings screen?

[Balderick]

According to this Steam user using Steam for windows the layout ui in controller settings should be available for PS type controllers when in dinput mode, i can not reproduce with my Thrustmaster T500 RS wheel and pedals when in dinput mode but it older PS3 licensed device
https://steamcommunity.com/groups/SteamClientBeta/discussions/1/3482994087425070630/?tscn=1664051851#c3373782431189831601

This highlights how broken Steam Input is just now. I used to see steering wheel as detected controller in controller settings but when opening layout mapping ui there were no buttons mapped. Mapping layout and save as PS3 type controller meant i could use wheel buttons and wheel base buttons to navigate Big Picture without launching a game.

In recent Steam client builds Steam Input never detects wheel and pedals but works just fine when in xinput mode in games that support them. Just cant navigate big picture out with game any more because of the missing controller layout ui and Steam not listing them as detected controller.

It weird how Steam is treating the dul sense and other devices like wiimote just now. Glad i do not have that issue!.

Am sure what i am describiung is related to how Steam Input is handling PS type controllers and other input devices.
Hopefully Valve fix soon.

Thanks for helping out tintingaroo you very knowledgeable guy and appreciate your help. Just realised it was you who was helping me out over on Steam for windows beta discussions