2010-02-06, 18:23
I've been playing with the latest nightly build r27482 and have setup the controller to do pretty much everything that the Xbox360EventClient.exe but within XBMC and without the need to launch the EventClient file. Correct me if I'm wrong, but I believe that the patch that bobdevis has written to fix the controllerdeadzone problem is included in the latest nightly builds. When i use the volume stick (right stick) I no longer have the sound level wandering down or up. The main reason I prefer this method is that when I would launch games from the Launcher plugin, Xbox360EventClient.exe would still send the 360 button presses through to XBMC while I was playing the game.
[PROBLEM]I do have a problem though with losing the ability to use the D-PAD. I haven't pin pointed what the cause is, but after some time, the dpad won't function in the menu's or the video. I can't remember exactly, but sometimes pulling the left trigger brings the DPAD back to life. I will investigate this further when I am able to replicate the problem.
Now on to some info for the 360 controller. I've been setting up the keymaping file for the 360 Wireless Controller and thought I'd share what I know about the controller's Button ID's so far.
Sample of the XML file for global settings
Here's a link to my prepared XML keymap file ready to go for the latest nightly builds of XBMC. Just put it in your "c:/Program Files/XBMC/System/Keymaps" folder and make sure your wireless controller is on before you launch XBMC.
http://rapidshare.com/files/346793973/jo...roller.xml
I still need info on the Right & Left triggers. At this stage it seems to be axis limit="0" id="3" makes the left trigger go super fast whilst axis limit="0" id="6" makes the right trigger go slow in the menus. Right and left triggers both go to the left or up instead of left and right respectively.
Hopefully this will shed some more light on getting full support for Xbox 360 Wireless Controllers in XBMC for Windows. I'm hoping by the next stable release we can all use 360 controllers straight after install without configuration.
On a side note, if you are after an Xbox 360 Wireless Receiver for Windows, you can get one from Deal Extreme
[PROBLEM]I do have a problem though with losing the ability to use the D-PAD. I haven't pin pointed what the cause is, but after some time, the dpad won't function in the menu's or the video. I can't remember exactly, but sometimes pulling the left trigger brings the DPAD back to life. I will investigate this further when I am able to replicate the problem.
Now on to some info for the 360 controller. I've been setting up the keymaping file for the 360 Wireless Controller and thought I'd share what I know about the controller's Button ID's so far.
Code:
button id 1 = A
button id 2 = B
button id 3 = X
button id 4 = Y
button id 5 = Left Button
button id 6 = Right Button
button id 7 = back
button id 8 = start
button id 9 = left stick button
button id 10 = right stick button
axis limit="-1" id="2" Up on left stick
axis limit="+1" id="2" Down on left stick
axis limit="-1" id="3" Left on left stick
axis limit="+1" id="3" Right on left stick
axis limit="-1" id="4" Up on right stick
axis limit="+1" id="4" Down on right stick
axis limit="-1" id="5" Left on right stick
axis limit="+1" id="5" Right on right stick
hat id="1" position="up" Up on DPAD
hat id="1" position="right" Right on DPAD
hat id="1" position="down" Down on DPAD
hat id="1" position="left" Left on DPAD
Sample of the XML file for global settings
Code:
<global>
<joystick name="Controller (Xbox 360 Wireless Receiver for Windows)">
<button id="1">Select</button>
<button id="2">ParentDir</button>
<button id="3">FullScreen</button>
<button id="4">Queue</button>
<button id="5">ContextMenu</button>
<button id="6">PreviousMenu</button>
<button id="8">XBMC.ActivateWindow(PlayerControls)</button>
<button id="9">Screenshot</button>
<button id="10">XBMC.ActivateWindow(ShutdownMenu)</button>
<hat id="1" position="up">Up</hat>
<hat id="1" position="down">Down</hat>
<hat id="1" position="left">Left</hat>
<hat id="1" position="right">Right</hat>
<axis limit="-1" id="4">VolumeUp</axis>
<axis limit="+1" id="4">VolumeDown</axis>
<axis limit="-1" id="5">AnalogSeekBack</axis>
<axis limit="+1" id="5">AnalogSeekForward</axis>
<axis limit="0" id="3">ScrollUp</axis>
<axis limit="0" id="6">ScrollDown</axis>
</joystick>
</global>
Here's a link to my prepared XML keymap file ready to go for the latest nightly builds of XBMC. Just put it in your "c:/Program Files/XBMC/System/Keymaps" folder and make sure your wireless controller is on before you launch XBMC.
http://rapidshare.com/files/346793973/jo...roller.xml
I still need info on the Right & Left triggers. At this stage it seems to be axis limit="0" id="3" makes the left trigger go super fast whilst axis limit="0" id="6" makes the right trigger go slow in the menus. Right and left triggers both go to the left or up instead of left and right respectively.
Hopefully this will shed some more light on getting full support for Xbox 360 Wireless Controllers in XBMC for Windows. I'm hoping by the next stable release we can all use 360 controllers straight after install without configuration.
On a side note, if you are after an Xbox 360 Wireless Receiver for Windows, you can get one from Deal Extreme