If you come with expectations that you’ll just be fully catered no matter what your setup is and expect things to just work without ever trying to understand problems, you sure can be disappointed. Believe or not, most of the time those issues are out of control for Linux or the distros, as your hardware vendor made it to work on Windows and Windows only. Community is here to help you, but with your attitude it gets difficult no matter how much others try to help.
Pretty much because for some reason it’s broken mess in native games with SDL, and works nicely when using Proton, I noticed that too.
Hi there, having two dualsense and one ps4 controller, using them for ages on Linux and they mostly run great, but your issues doesn’t sound completely new either.
It’s very important on how you installed Steam and whether it’s native package or Flatpak. For Flatpak you might need special udev rules to allow the controller inside sandbox, usually can be installed using steam-devices package.
As others said, enable Playstation Controller support in Steam’s controller settings page.
Check if Steam overlay is functioning. In-game, press Shift+Tab and you should see the overlay and then you should be able to get to controller settings. Try out both with Steam Input enabled and disabled - by default I guess it depends on the game, but mostly enabling it will make it work for games that have issues picking up ds natively.
Test your controllers using something like jstest-gtk. Perhaps there is something else connected that acts as player 1 controller.
Don’t forget that at this point X11 doesn’t have feature parity with Wayland more than the other way around. Mixed DPIs, refresh rates, multi-display VRR, virtual screen resolutions, nested compositing, direct scan-out, GPU hot plugging, DRM leasing, HDR are all exclusive or at least better on Wayland.
Plot twist: he grabs you out of the bush and kiss