Garbear I'll give you as much info as I can in the hope you will find the issue.
(2016-01-30, 02:51)garbear Wrote: [ -> ]My guess is that Xbox_360_Wireless_Receiver_15b_6a.xml uses buttons for dpads because it has 6 axes, and Xbox_360_Wireless_Receiver_15b_8a.xml uses axes for d-pads because it has 8 axes.
So yes, several buttons will break. But the majority will work. The point is to use the data we have to give the user the most functionality possible out of the box.
hmmm, so looking at my submitted (working) keymap for the 8a (
the one on github) these are the axis:
Code:
leftstick right axis="+0"
leftstick left axis="-0"
leftstick up axis="-1"
leftstick down axis="+1"
lefttrigger" axis="+2"
rightstick left axis="-3"
rightstick right axis="+3"
rightstick down axis="+4"
rightstick up axis="-4"
righttrigger" axis="+5"
I count that as 6 axes, but my log says:
Code:
AddOnLog: Joystick Support: Initialized joystick 0: "Xbox 360 Wireless Receiver", axes: 8, hats: 0, buttons: 15
Note all 15 buttons are accounted for (0-14) using my keymap, with the d-pad using 4
buttons.
After running the controller config window which skips the down and right selections (
full log here) snippet:
Code:
20:25:28 T:139999357400960 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 13 pressed
20:25:28 T:139999357400960 DEBUG: Removing "up" from button map due to conflict
20:25:28 T:139999357400960 DEBUG: Joystick button event handled
20:25:28 T:139999357400960 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 13 released
20:25:29 T:139999357400960 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 12 pressed
20:25:29 T:139999357400960 DEBUG: Removing "right" from button map due to conflict
20:25:29 T:139999357400960 DEBUG: Joystick button event handled
20:25:29 T:139999357400960 DEBUG: Joystick Xbox 360 Wireless Receiver: Button 12 released
doesn't give me anything to help, as up was 13, and right was 12, skipped down and left
but this is the resulting keymap:
http://sprunge.us/SVBN snippet:
Code:
<feature name="up" button="13" />
<feature name="down" axis="-7" />
<feature name="right" button="12" />
<feature name="left" axis="+6" />
2 new axes here! are these the missing 7th and 8th axes? or does your code just populate the skipped entrys with some random figures?
What I don't get is how is Up triggering a button 13 press and also a movement on the 7 axis. Are you able to add a commit which could provide more logging info??