While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations:
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- The "video game preservation service" Myrient is shutting down in March
- SpaghettiKart the Mario Kart 64 fan-made PC port gets a big upgrade
- California law to require operating systems to check your age
- Run your own band in the pixel art management game Legends of Rock
- The OrangePi Neo gaming handheld with Manjaro Linux is now "on ice" due to component prices
- > See more over 30 days here
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
I'm trying to play with xbox one controller, it's connected via bluetooth and it seems to work properly through Steam big picture.
There is one problem, in game it's not working. I tested few game, native or proton with no difference.
Running games with xbox 360 controller is OK.
I'm running Debian Bullseye and disable ERTM (cf. https://wiki.debian.org/Gamepad#Troubleshooting)
How can I fix it ?
From [what I've read](https://steamcommunity.com/app/300380/discussions/0/1726450077644370194/), what happens in this case is that games are seeing Steam Input's "virtual" controller as a real one, and then picking up the physical controller as that of player two, which causes various problems. I gather that this is an old bug, so it seems odd that it consistently appears on at least some current Debian-based distros. Still, I'm glad that it was easy to fix! :smile:
Last edited by Pengling on 20 Jan 2023 at 2:55 pm UTC