Valve released another set of Beta updates for the SteamOS Client and Steam Desktop to bring in bug fixes and expanded support.
For SteamOS / Steam Deck the latest update in Preview / Beta brings in:
Steam Input
- Fixed input in: Ratchet and Clank for Legion Go S.
- Improved support for: 8BitDo gyro on controllers with updated firmware.
And then for the Steam Desktop Beta changes:
General
- Fixed layout regressions in post-game summary UI and in achievement unlocked friends feed rows.
In-Game Overlay
- Added per-core CPU utility bar graph as an option for performance monitor.
- Made FPS graph and new per-core CPU utilization graph options independent from detail levels so you may now have full detail but no graphs, or just FPS+CPU/GPU Utilization but including graphs.
- Fixed wrong value sometimes shown as Max CPU core utilization in performance monitor.
- Fixed a regression breaking join game from the friends list in the overlay in some cases.
- Fixed small slow memory leak in gameoverlayui process.
Steam Input
- Improved support for 8BitDo gyro on controllers with updated firmware.
There's no specific Linux improvements yet for the newer In-Game Overlay, I will let you know here on GamingOnLinux as soon as I spot any of the newly added features making their way to Linux.
Some you may have missed, popular articles from the last month:
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
hopefully they add a temp gauge to the overlay then that will be complete
0 Likes
Love seeing even a little bit of progress. I only use 8bitdo controllers now and have zero regrets.
0 Likes
Anyone getting the gyro to show up on an 8bitdo? I can't seem to access it from the beta on my wireless ultimate 2. The windows profile setup isn't useful
0 Likes
I finally got gyro, the paddles and analog triggers to work at the same time on an 8BitDo Pro 2!
Seems that gyro support has made its way into the Steam stable branch, so no Steam beta needed.
The controller had to be updated to firmware version 3.06 (using 8BitDo's update tool that only works on Windows (I did that using VirtualBox)).
To get all those features, I had to connect the controller in DInput mode over Bluetooth (mode switch on the bottom set to "D").
To allow Steam to read the gyro data, I had to add a udev rule:
File: "/etc/udev/rules.d/42-8bitdo-pro2.rules"
reload udev rules with `sudo udevadm control --reload` and reconnect.
Et voilà, all features of the Pro 2 exposed to Steam :)
Note that everything worked out of the box on my Steam Deck. Looks like Valve is shipping the respective udev rules already.
The device name in the udev rule may differ if you've got another controller; I found mine by watching the kernel output with `sudo dmesg -w` and connecting to the controller in DInput mode. (The last part after the "." seems to count upwards with every new connection, thus the asterisk.)
Credit goes to the author of this GitHub gist (which was for another controller, the "8BitDo Ultimate 2 Wireless"): https://gist.github.com/barraIhsan/783a82bcf32bed896c85d27dbb8018a5
Maybe that'll help you get things set up @cwinnbari
Seems that gyro support has made its way into the Steam stable branch, so no Steam beta needed.
The controller had to be updated to firmware version 3.06 (using 8BitDo's update tool that only works on Windows (I did that using VirtualBox)).
To get all those features, I had to connect the controller in DInput mode over Bluetooth (mode switch on the bottom set to "D").
To allow Steam to read the gyro data, I had to add a udev rule:
File: "/etc/udev/rules.d/42-8bitdo-pro2.rules"
# 8BitDo Pro 2: Gyro in DInput mode over Bluetooth
KERNEL=="hidraw*", KERNELS=="0005:2DC8:6006.*", MODE="0660", TAG+="uaccess"
reload udev rules with `sudo udevadm control --reload` and reconnect.
Et voilà, all features of the Pro 2 exposed to Steam :)
Note that everything worked out of the box on my Steam Deck. Looks like Valve is shipping the respective udev rules already.
The device name in the udev rule may differ if you've got another controller; I found mine by watching the kernel output with `sudo dmesg -w` and connecting to the controller in DInput mode. (The last part after the "." seems to count upwards with every new connection, thus the asterisk.)
Credit goes to the author of this GitHub gist (which was for another controller, the "8BitDo Ultimate 2 Wireless"): https://gist.github.com/barraIhsan/783a82bcf32bed896c85d27dbb8018a5
Maybe that'll help you get things set up @cwinnbari
0 Likes