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
Discussions Rules and Guidelines
Report this post
Here's a post from someone else who's running into the same issue, trying to use it with DS4Windows:
https://www.reddit.com/r/DS4Windows/comments/saw0u8/help_with_nacon_asymmetric_wireless_controller/
What about the button layout. Before the update steam did not recognize it as an XBOX but as a PS4 controller.
I can use the controller but the layouts are wrong both in games and in steam big picture menu. This was not the case for the past 2 years before the beta update of steam.
Do we know if steam will resolve this?
I just tested it using the Controller -> "Test Device Inputs" functionality in the new Big Picture and it showed up as an Xbox controller and all the controls worked as expected, except for the PS button which brought up the Xbox game bar on my computer (which is what happens when the Xbox guide button is pressed)
This is how i used to map Thrustmaster T500 RS wheel buttons and wheel base buttons (no axis) but steam does not even show that device as detected nowadays - which is not expected behaviour as steam users should be able to decide what controllers get shown in controller settings not steam. It is afully licenced ps3 device and used to get detected as generic gamepad.
Bug Report for that found at - https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3763356923841756034/
What i am describing and what OP is describing is a duplicate of https://steamcommunity.com/app/1675200/discussions/1/3498761686675442671/
Many more threads do mention and describe same issue.
PS button prompts are broken, both in steam ui and in game.
This post claims SDL 3 has full backward compatibility in the Takeaway.
https://schedule.gdconf.com/session/open-source-game-development-summit-simple-directmedia-layer-past-present-and-future/892854
And yet Steam SDL is so broken it is nothing like its former self in the days before Steam Deck and nbpm existed.
Steam Support refuse to acknowledge this as an issue going by what is described in the Steam Deck thread linked to above reporting same issue made several months ago.
@slouken Can you plaese acknowledge this is now a known issue and we can expect ps button prompts to be fixed in the near future?
Knowing something is broken is first step in fixing it, right?
Am really looking forward to listening/watching your SDL talk at GDC as Steam SDL has changed so much i no longer know what are bugs and what is new expected behaviours. I see more bugs and less functionality and configurability compared to what Steam SDL used to work like. Steam SDL seems to have been massively gimped and it feels like Valve just want to hardcode everything. But nothing is working like expecetd with all the recent changes. So much feels deliberately broken just for nbpm and Deck. like the Define Layout ui that had been completely removed until two or three months ago
Is that because of WGI changes?
How do you know if generic gamepads that loaded as xinput compatible device is using raw or other service/api or not?
xinput supports both xinput and dinput so steam sdl not being configurable to manage this is actually a sdl bug
https://learn.microsoft.com/en-us/windows/win32/xinput/xinput-and-directinput
Something changed in windows os which Valve devs cant reproduce on linux and since linux is now primary targeted platform Valve just blacklist controllers or set them as generic gamepad loked to xinput so breaks ps button prompt support in steam ui and in steam games.
The thread slouken links to describes controller working as ps controller in games that support it - steam sdl always forces xinput.
slouken has only shared info to make us think we cant expect that controller to work in steam because it is not detected by ds4windows though i pretty sure it does get detected but simply can not connect. Enabling verbose logs in ds4windows proves that.
What is described for nacom controller in op here and in that reddit thread is actually describing exact same issue i see with Thrustmaster T500 RS steering wheel (ps4 licenced device) in both steam sdl and ds4 windows.
ds4windows also treats my THrustmaster eSwap X Pro controller like nacom - it gets detected but cant connect
ds4windows vigem driver forces a bt controller when emulating ps4 controller - that is how it fixed 8BitDo Pro 2 controller in Steam sdl in A (macos) and D (android) modes which are both dinput as raw capabilities are shown in device properties. It also fixed BT
Here is link to a thread on libsdl-org where slouken simply can not reproduce what many folks are saying bad layout is a issue but A and D modes are working like expected for them. So cant fix
The problem is far wider than just nacom controller.
imo steamxbox.sys driver is being assigned to wrong device because of the weird WGI thing so steam cant see the raw capabilities
Have Sony or Microsoft complained to Valve about the button prompt thing? From Valves perspective all controllers that steam input detects is a steam controller. Maybe Ms feel the same about controllers connected to a windows pc it is a xinput device.
i tried to explain there is much more that slouken can do to help us better understand why xbox type controllers, ps type controllers and other supported controller types have stopped working like expected in steam sdl.
slouken could fix it by removing sdl3.dll and nbpm from steam until they are ready for consumer devices in the wild.
Recompiling sdl source code to generate new sdl3.dll to swapo out the one that gets installed by Steam is a known workaround for fixing ps5 controller support in Steam, it may help with nacom controller issue too..
We can also use sdl2-gamepad-mapper to check sdl config for controller outwith steam runtime and compare that to what is in steam config.vdf after steam detects same controller. The problem is steam sdl, it simply does not work anywhere near as well as it used to..
https://gitlab.com/ryochan7/sdl2-gamepad-mapper/-/releases
But apparently, we need to just accept our controller may or may not work like we expect in steam because of nbpm and all the poopooo it has caused..
For me my xbox controllers (first and third party licenced devices), Thrustmaster T500 RS, 8BitDo Pro 2 controller all do not work like expecetd. From smaller issue like guide button being broken (using nbpm undoes my workarounds to get everything working in steam large mode) to simply not being detected in steamui and is not usuable in steam games that support it even after disabling steam input for game with T500 RS
Everything i loved about steam was mostly related to how Steam INput used to be massively configurable for all my controllers and input devices. Now Steam Input is why my scorn for steam grows by the day because it sucks so bad it hurts. I hate being reminded how broken steam is every time i plug in a controller.