This happens to me as well, however for me, Steam Big Picture automatically selects my mouse, a Roccat Tyon Black, as its controller (yes, my mouse also registers /dev/input/js0 as well as a pointer device).
For me the only way to get steam to recognise the correct controller is to unplug my mouse, restart xboxdrv (the gamepad driver), and re-plug my mouse.
Same problem here, for me I have Thrustmaster T-16000 Joystick , Big picture detects the joystick's throttle as me scrolling through pages.
I have to unplug the joystick.
Would be quite easy to select a controller simply by it's name and ignore whatever /dev/js it is on. Would be a cool feature.
What actually would be quite good to do at the same time would be to have per controller configurations and then just select the config to be used as primary,secondary etc.
Oh and if someone says "just create a udev rule to set your gamepad as js0", that doesn't work any more because udev scrapped renaming of kernel device nodes. It only allows symlinking now
Is this still an issue?
I don't have said mouse any more, but I can test this again with two different controllers if needed.
@kisak-valve This likely can be closed
Nothing extracted yet.
I have a HOTAS plugged in, as well as a sixaxis controller connected by Bluetooth (Bluez 5.28).
The HOTAS is registered as /dev/input/js0, and /dev/input/js1, while the sixaxis is registered as /dev/input/js2.
Steam Big Picture automatically picks the first controller, which is the HOTAS throttle. This is of course not the right one. Please add an option to select the controller used in Big Picture or automatically detect a gamepad instead of some kind of different controller.