Odd issue with xinput (affecting microsoft controllers and random controllers)
Just writing this here so i can keep track of it while testing as i might not get full time to dive into it until Wednesday.
Currently it seems like Xbox controllers and random Xinput controllers (RetroFighter BattlerGC) get mapped up as an xbox 360 controller wirelessly according to steam input and then refuse to provide input, wired they show up as either 360 or xbone controllers but still provide no input.
However controllers like the 8Bitdo Ultimate Bluetooth controller (in xinput mode) will work fine and shows up as an xbox one controller and generates input while the KingKong 2 Pro shows up as an xbox 360 controller but will generate input.
According to @EyeCantCU this seems to not happen on his Gnome system with his Xbox Elite Series 2 controller while i have verified it is broken on 2 separate systems (both running deck KDE image) on my end.
I will be firing up a VM with passthrough to it myself on clean installs as this seems super weird.
NOTE: image shows me moving the left stick all the way to the top left and the left joystick position in steam is still reported as 0,0
this also happens with other applications too so it is not steam input causing the issue.
21 Replies
update:
ujust use-stock-gamepads fixes the elite controller, testing others
does not fix:
* retrofighters battlergc
fixes
* xbox one elite series 2 (wired)
* xbox one elite series 2 (bluetooth)
* xbone S controller (bluetooth although it reconnected 2 times going from detected as xbox one with no input, to xbox one with input to xbox 360 with input)
* xbone S controller (wired)
anomally: seems like the first connection on a bluetooth connection (regardless of controller and input mode) will provide no input on both my systems, reconnecting the controller will make everything work againI wonder if xpadneo/noone are busted...
it is weird and idk if i tried to use controller other than 8bitdo ultimate bluetooth controller and the kingkong 2 pro controller
both which have been unaffected and i think i have been using them since before xpad-noone was made for bazzite
last time i used an xbox controller for bazzite was when i first set it up on my htpc over a month and so ago
so might be
Do you encounter this in GNOME?
oh right, kinda got distracted when it worked with stock-gamepads
will fire the VM up again and rebase to gnome
will just check the xbox elite controller for now as i need to head to sleep very soon
Sounds good 🙂
just a question, do you use the stock gamepads option? do you have the xone.conf, xpadneo.conf and xpad-noone-blacklist.conf in /etc/modprobe.d?
since the stock option worked for me
controllers still not responding on gnome so must be xone, xpad, xpad-noone and xpadneo related
Hmm... Possibly. I'm on the latest image and haven't encountered any issues. I'll try a fresh one
just check if you have the files i listed in /etc/modprobe.d
if the conf files exist then youre using stock-gamepads not ublue-gamepads
The default (Ublue gamepads). I don't touch the config file so I'm not entirely sure but I can look when I'm home
i dont touch the config either which makes it odd that we have 2 different results, hence why i want to check if you have the config files before digging deeper 🙂
im heading to bed, have a nice remainder of your day
I've got it in /usr/lib/modprobe.d
ok then you had stock-gamepads enabled, hence the different results
I definitely don't because lsmod shows xpadneo
xpadneo still loads
it loads in both ublue-gamepads and stock-gamepads
That's counter to what they're supposed to do
Adding my experience with Bazzite GNOME: 8bitdo Ultimate BT works in both xinput and BT modes, but xinput mode has a timeout with the way it expects a game connection. This isn’t easily achieved using the distrobox container version of Steam because your controller has to be connected prior to launching Steam, but the controller only stays connected if it’s turned on while Steam is running.
I get around this by running the flatpak version of Steam.
I have a fightstick running off a GP2040-CE that identifies as a 360 controller. It works without an issue. I have not made any changes to controller drivers.
(And apparently this doesn’t matter anymore now that I see that Steam is layered in. I have not been paying attention for a few days)
Yep, fully consistent now
We lose some benefits but gain others
Such as HDR on KDE in the very near future
never had that issue (KDE) with my 8bitdo Ultimate BT controller in neither xinput, switch input and BT mode 🤔
but i also discovered that gnome doesnt use the same bluetooth backend as KDE yesterday since when i went from KDE to GNOME my BT5 dongle i use for testing in VMs didnt show up in gnome 😂 i had forgotten that they use different backends
well its what happens when you have the files and connect a controller
but at least the controllers work which is all i care about 😛
So it looks like the behavior for the just recipes is the opposite of what I had thought they were (unsure if this was intentional or not). Stock gamepads loads xpadneo among others, Ublue gamepads unloads them all
I might open a PR for that as it feels backwards
Can also use modprobe to load right then versus rebooting