xbox elite 2 controller swapped buttons #21
Replies: 1 comment 7 replies
-
|
These patches are outdated... I should update them. Regarding the paddles, I think there's a misconception of them being separate game input buttons - MS never intended that but SDL tries to handle it that way (but it breaks at the protocol level). You can only reliably separately detect the paddles in profile 0 mode (that is, no LED is showing). All the other three profiles map the paddles to existing buttons - there's no separate key code for paddles. That mapping defaults to A,B,X,Y. The problem with X, Y and RB you are seeing is probably due to Steam Input enabled. After (but not sure when) I upgraded this patchset to the latest v0.9 version, that may be fixed. Try installing the latest v0.9 xpadneo driver over this patchset as a module (it should work, I'm doing the same). If that fixes your problem, confirm here. If it doesn't, open an issue report there. |
Beta Was this translation helpful? Give feedback.
-
|
BTW: Switching between the patched-in module and the out-of-tree module is currently broken and needs a reboot. This is due to differences in handling the bus detach and attach which has been repaired in latest out-of-tree module. |
Beta Was this translation helpful? Give feedback.
-
|
I've updated the kernel patch, please re-download and apply again. It should fix most issues and is at current xpadneo master with additional Share-button-to-F12 patch (which I'm currently testing). |
Beta Was this translation helpful? Give feedback.
-
|
Ok, Thank for your support :) |
Beta Was this translation helpful? Give feedback.
-
|
Maybe we can solve the paddle mystery when I reverse-engineered the programming protocol. You may need to map the paddles to some specific inputs using the Xbox Acc app in Windows. And Steam for Windows probably needs an update to work with the latest firmware properly because MS seems to have changed how the paddles are exposed on the protocol. I think @medusalix from xone sees a similar problem with the paddles using the dongle protocol. It looks like some bits shifted by one byte between the 4.x and the 5.x protocol which can be detected by looking at the packet size, at least this is true for the Bluetooth HID protocol. Also, at least in HID, the paddles aren't really a button bitmap but rather a plain HID value, and I needed to parse that manually in the report handler. So, in Windows you may have better luck switching from Bluetooth to the GIP dongle, or vice-versa. With firmware 5.x, it's at least easy to switch the connection mode, no re-pairing needed:
|
Beta Was this translation helpful? Give feedback.
-
|
I don't remember having pairing issues with 4.x because I share the same key on both operative systems: Maybe I am wrong because I mainly use the PS4 dual shock controller on Linux and I don't play too much with my elite controller. I think I will update to 5.x hoping Valve will update the windows xbox elite support. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @kakra ,
I recently give it a try your xpadneo patches for 5.15 again
This time I could make it working perfectly.
But the problem is... X and Y are swapped and RB is not working and some more problems.
I tried to update the controller firmware to 5.13.3143.0 but I had the following problem and I had to revert back to 4.8.1908.0
https://steamcommunity.com/groups/SteamClientBeta/discussions/0/5144805327263762385/
as you see, with the new firmware steam stopped to have the feature of remapping the paddles and I wanted to have that feature so I reverted the firmware.
My question is:
To whom I have to report the issue about having the buttons wrong using 4.8.1908.0 firmware?
Thanks for your work
Beta Was this translation helpful? Give feedback.
All reactions