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
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.
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.
Started on my end with the 27 July Steam client update.
Still worked outside of Steam while Steam was started before that.
Same problem appears to happen with Xbox and XInput controllers as well that natively use XInput in the first place.
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.
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.
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.
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
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
and the save controller type option
Seems like it doesnt work for me :( Wired and BlueTooth no success :/
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