Closed TiagodePAlves closed 1 year ago
The same thing happen for me.
The same thing happen for me.
The same thing happen for me.
This works as designed in the current versions. It's just cosmetic, the controller is still fully supported. We cannot currently change that. See also #286
Version of xpadneo
0.9.5 (from AUR xpadneo-dkms 0.9.5-2)
Controller Model
Connection mode
0a12:0001
dongle)Installed Software
Protocol Information
Please help us identify at which layer the problem can be found if you want to report mapping errors or if the controller fails to be detected:
evtest
is showing issues (describe the issues below)BTN_NORTH
andBTN_WEST
are intentionally swappedjstest
is showing issues (describe the issues below)gamepad-tool
is showing issues (post console output below)Please describe how it is failing below in the next sections.
Severity / Impact
Describe the Bug
When xpadneo is installed and loaded, my Xbox Series Controller is recognized in Steam as a Xbox 360 Controller, even named like that in General Controller Settings and Big Picture Configuration. This only happens in Bluetooth, the controller is recognized correctly with a wired connection. The odd part for me is that without xpadneo installed, the controller is labelled correctly in Steam (tested wired and Bluetooth connections).
Not sure if this expected or not.
Steps to Reproduce
Expected Behavior
Controller should show up as Xbox One Controller in Steam settings.
Screenshots / GIFs / Videos
System Information
Controller and Bluetooth Information
xpadneo-btmon.txt
xpadneo-dmesg.txt
xpadneo-lsusb.txt
Additional Context
Although the labeling is weird, the controller works perfectly.