xbox one s 9th axis? #334
Comments
This may cause some wrong button mappings, usually if you also have RGB control software installed. This is due to Steam Input internally using SDL to query the controller, and SDL uses wrong assumptions about the HID driver. It will also affect software not running through Steam while Steam is running.
The X button is aliased "north" internally in the Linux kernel but actually, it is not north on Xbox controllers. Games use the symbolic names instead of the cardinal names, so mapping ends up correctly.
Xbox controllers do not need calibration, the evdev driver already returns the correct value range and dead zones to the jsdev driver. Also, that old jsdev interface is usually not used by any modern game which makes calibration useless anyways.
The RT issue may be linked to the 9th axis.
Nintendo has X and Y swapped. I'd expect emulators to have a switch for swapping that as the user prefers. If it doesn't, there's a quirk option in xpadneo to pretend Nintendo mapping (swaps X and Y, and actually makes X the north button).
The 9th axis was requested by simulator users who wanted to use the triggers for rudder but needed that as a combined axis. Software supporting gamepads should usually ignore that as they expect only 8 well defined axes.
This may be a problem with your Bluetooth dongle. We actually can do nothing about it from xpadneo, xpadneo doesn't talk to Bluetooth, xpadneo talks to a HID device presented to us by Bluetooth.
From the perspective of xpadneo, this makes no difference. But I'm not able to guess the same for other software that you may be using.
The connection problems are usually in bluez itself (due to neighboring devices, or software like kdeconnect which interferes with Bluetooth in a bad way), sometimes within Bluetooth drivers in the kernel. While we still try to provide support for Bluetooth issues, there's nothing that xpadneo as a driver itself could do about it because it doesn't talk to Bluetooth. Usually, CSR with original chipsets dongles work best (Cambridge Silicon Radio, used by vendors like TP-LINK). |
|
Steam wasn’t open, I guess it has something to with having it installed.
I do have openRGB installed and running.
What steps should I take to stop steam or other from messing with the
mapping?
…On Thu, Jan 13, 2022 at 1:28 AM Kai Krakow ***@***.***> wrote:
Steam Input (enabled by default via Steam Desktop client)
This may cause some wrong button mappings, usually if you also have RGB
control software installed. This is due to Steam Input internally using SDL
to query the controller, and SDL uses wrong assumptions about the HID
driver. It will also affect software not running through Steam while Steam
is running.
Questionable, some buttons are mapped incorrectly as well X shouldn't be
north?
The X button is aliased "north" internally in the Linux kernel but
actually, it is not north on Xbox controllers. Games use the symbolic names
instead of the cardinal names, so mapping ends up correctly.
When calibrating with Gamepad in plasma I am asked to calibrate a 9th
axis, LT and RT seem to activate this axis, xpadneo not installed it asks
for 8, but some buttons do not work.
Xbox controllers do not need calibration, the evdev driver already returns
the correct value range and dead zones to the jsdev driver. Also, that old
jsdev interface is usually not used by any modern game which makes
calibration useless anyways.
With xpadneo puNES doesn't recognize the select button, SNES9x does, ePSXe
recognizes them all, but RT is recognized as 456 when lightly pressed and
453 when fully pressed. So those are likely app related issues.
The RT issue may be linked to the 9th axis.
X and Y mapping appears to be swapped
Nintendo has X and Y swapped. I'd expect emulators to have a switch for
swapping that as the user prefers. If it doesn't, there's a quirk option in
xpadneo to pretend Nintendo mapping (swaps X and Y, and actually makes X
the north button).
and the 9th axis that doesn't exist (does it?) is activating RT and LT
[...]
LT does negative for 9th axis RT does positive for 9th axis
The 9th axis was requested by simulator users who wanted to use the
triggers for rudder but needed that as a combined axis. Software supporting
gamepads should usually ignore that as they expect only 8 well defined axes.
connection also drops occasionally.
This may be a problem with your Bluetooth dongle. We actually can do
nothing about it from xpadneo, xpadneo doesn't talk to Bluetooth, xpadneo
talks to a HID device presented to us by Bluetooth.
I do have a HTC vive box connected to my pc, the Vive wireless system as
well. Not sure if it is conflicting, but can unplug the vive box or disable
if someone teaches me how on arch.
From the perspective of xpadneo, this makes no difference. But I'm not
able to guess the same for other software that you may be using.
I've been trying to work this out for a few days after taking a week off
out of frustration, finally got it to connect when the kernel was updated
to 5.15.13(5.16.0 according to arch) and I am actually running EndeavourOS,
but that probably doesn't really matter.
The connection problems are usually in bluez itself (due to neighboring
devices, or software like kdeconnect which interferes with Bluetooth in a
bad way), sometimes within Bluetooth drivers in the kernel. While we still
try to provide support for Bluetooth issues, there's nothing that xpadneo
as a driver itself could do about it because it doesn't talk to Bluetooth.
Usually, CSR with original chipsets dongles work best (Cambridge Silicon
Radio, used by vendors like TP-LINK).
—
Reply to this email directly, view it on GitHub
<#334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPNONUNOUUB7DNSPV6EQKLUV2LNHANCNFSM5L2VLYCQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Please uninstall openRGB to see if that resolves your issue... OpenRGB interferes with access permissions to raw HID devices and tries to make the controller a RGB device controlled by openRGB. If that fixes your issue, a work-around would be to override the ACLs provided by openRGB to the controller HID device until the issue is resolved in openRGB. This problem usually only affects software using SDL2 for input. |
|
Found a different solution, installed retroarch and switched to that and playing wired since my controller won't connect again. I do have the BCM20702A0 (I believe) which I used for hackintosh, saw it on the list and I could try it instead. Update: |
Version of xpadneo
0.9.1 git repo and aur
Controller Model
Xbox One S controller
Connection mode
Bluetooth connection
Installed Software
Steam Input (enabled by default via Steam Desktop client)
Severity / Impact
Questionable, some buttons are mapped incorrectly as well X shouldn't be north?
I've read the docs and the bug reporting instructions
I've applied the latest firmware update to the controller
I probably didn't figure it all out but it's too early to give up
Describe the Bug
When calibrating with Gamepad in plasma I am asked to calibrate a 9th axis, LT and RT seem to activate this axis, xpadneo not installed it asks for 8, but some buttons do not work.
With xpadneo puNES doesn't recognize the select button, SNES9x does, ePSXe recognizes them all, but RT is recognized as 456 when lightly pressed and 453 when fully pressed.
So those are likely app related issues.
X and Y mapping appears to be swapped and the 9th axis that doesn't exist (does it?) is activating RT and LT
LT does negative for 9th axis
RT does positive for 9th axis
connection also drops occasionally.
Steps to Reproduce
install 0.9.1 and go to calibrate
Expected Behavior
8 axis
Screenshots / GIFs / Videos
https://imgur.com/a/DKqtWKn
System Information
Controller and Bluetooth Information
Bus 007 Device 003: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio
xpadneo-btmon.txt
xpadneo-dmesg.txt
xpadneo-lsusb.txt
Additional Context
I do have a HTC vive box connected to my pc, the Vive wireless system as well.
Not sure if it is conflicting, but can unplug the vive box or disable if someone teaches me how on arch.
I've been trying to work this out for a few days after taking a week off out of frustration, finally got it to connect when the kernel was updated to 5.15.13(5.16.0 according to arch) and I am actually running EndeavourOS, but that probably doesn't really matter.
The text was updated successfully, but these errors were encountered: