Can confirm. As an aside: when I launch the on-screen keyboard, I do get controller input and I can focus the main window and still use the controller.
This happens in the latest beta for me with at least a couple controllers I tested (Steam Controller (wireless) and Hyperkin Trooper 2). Button presses properly recognized in game and in the controller button test, but the BPM controls are not functioning as expected with a game controller
+1 here with a PS5 controller. PS button also does not launch Big Picture Mode anymore.
+1 here with 8bitdo Lite 2 and 8bitdor Ultimate C Bluetooth
+1 here with a standard XBox One controller. Additionally, when opening Settings -> Controller -> Calibration & Advanced Settings:
Reverting to the stable client resolves the issue.
I am unfortunately suffering from the same issue, annoyingly the stable client has an issue with hardware decoding for remote play which seems to be fixed in the beta version.
Hopefully the team is aware and a fix is in the works, otherwise has anybody discovered a workaround?
With today's update the issue has softened a bit. Navigation via left stick is working now but dpad input is still being ignored.
I have also been experiencing this issue with a DS4 controller when using the beta. The only button that was picked up was the home button
I uninstalled the beta, and the problem disappeared
Manjaro linux, Gnome, Nvidia 3060Ti
PS4 controller on steam beta
Buttons does not do what are supposed to do. It's some mismatch. Only PS button working as espected. In games buttons are working with no problem, only in Big picture mode is problem on steam beta only.
With steam stable - no problem.
Also beta gives more performance to Big picture and run more smooth On Nvidia driver.
On Ubuntu, similar to other reports. I can't use my dualsense controller anymore. Steam Beta
@kisak-valve
Not sure whether this helps much, but for what it's worth, I've noticed my PS5 controller (connected by USB) works in a Gamescope session without any problems, while continuing to not work in regular non-Gamescope Big Picture mode.
The command I'm using for running Steam in Gamescope is
SDL_VIDEODRIVER=x11 gamescope --output-width 1280 --output-height 800 --nested-width 1280 --nested-height 800 --nested-refresh 120 --steam -- steam -gamepadui
This appears to be fixed in the latest beta.
Can confirm that my Elite 2 controller is again working in the latest Steam beta release
How do we know which beta version we are running and when a given beta is released on the "stable" channel?
How do we know which beta version we are running and when a given beta is released on the "stable" channel?
You should be able to see the build number and the build date under Settings / System. the build that fixed the issue was the one from yesterday 9pm.
As for what goes into the stable branch, I don't know. You probably have to read the release notes to see if this particular fix makes it into a future stable release.
Thanks.
Do you know where the release notes can be found?
https://store.steampowered.com/news/collection/steam/
Beta and stable release notes can be found here
Closing this since the last update fixed the issue for me. Thanks!
SDL_VIDEODRIVER=x11x1 2024-02
Your system information
Please describe your issue in as much detail as possible:
After latest beta my Microsoft Elite 2 Xbox controller (connected via bluetooth / xpadneo) does not work anymore in gamepad ui. Steam is not reacting to any button or stick input, the only thing that still works is the home button which opens the side menu. When going to Settings/Controller/Test Device Inputs I can see that Steam recognizes button presses or stick movement, but this does trigger menus or control movements in the UI. Tested in Dead Cells and the controller works in-game. Also tested successfully outside Steam (Kodi)
Steps for reproducing this issue: