Originally Posted by
'propagandalf',index.php?page=Thread&postID=165885 #post165885
I'm trying to keybind some X-keys but I'm totally lost. I have the 58 key professional model. Could someone give me some examples on how to set X-keys up, preferably using keymapper. Wen I use the "bind -keylist" command I see a bunch of "Button 0, Button 1, Button 2, etc., (all the way up to like 142, which I don't get.. shouldn't it be 114 as that's the most the 58 X-kyes can program including the second layer.) I can't seem to get them to work in keymapper, however.
Also, I'm not able to get my G15 keys to work either.
I read that you need to clear the keys, so I set my profilier to the default profile and unbound all the keys, however, they don't seem to work in the keymapper, either. Argh.
Any help is appreciated!
X-Keys apparently uses the same driver for different models, so your device may appear to Inner Space to have more buttons than it actually has. The Button 1, Button 2 and so on are very likely from your X-Keys device. The following script can help you determine which button on your device corresponds to which button in Inner Space:
Code:
atom AxisMoved(string Axis, float Position)
{
echo Axis=${Axis} position=${Position}
}
atom ButtonMoved(string Button, bool Position)
{
echo Button=${Button} position=${Position}
}
atom DPadMoved(string DPad, float Position)
{
echo dpad=${DPad} Position=${Position}
}
function main()
{
Event[OnAxisMove]:AttachAtom[AxisMoved]
Event[OnDPadMove]:AttachAtom[DPadMoved]
Event[OnButtonMove]:AttachAtom[ButtonMoved]
while 1
{
waitframe
}
}
Save as (e.g.) buttontest.iss in the Scripts folder of your IS install, and run it in the console in the main program (the one that opens when you select Console from the menu) via "run buttontest". When you are done, "endscript buttontest". While the script is running, any button you press, any D-Pad that moves and any Axis that moves will spit out some output in the console (while your X-Keys doesn't have a D-Pad or Axis, other sorts of controllers like gamepads, joysticks, etc can fire those events). You will want to (or should, at least) rename your X-Keys buttons so that they don't say Button 1, Button 2 and so on, if for no other reason than they're probably not in the order you'd expect. Open up InputDevices.XML in the IS folder (use notepad or another text editor) and find the Set for your X-Keys. If there are multiple sets, it might take some trial and error to figure out which one is the right one, but have it open while you press buttons for the buttontest script and label them in the XML as you go. Zanthor for example names his X1, X2, and so on, and that's probably a good convention to follow for X-keys devices. When you're done, close IS first (it may overwrite InputDevices.XML on exit), then save InputDevices.XML. When you launch IS again, it will begin using the new names, which you can again test with the buttontest script.
The G-keys do in fact work with KeyMapper, and I know this because I have a G15 and I use KeyMapper
If you are concerned that they may not work, you can test this again with the buttontest script. When you press G1, it should say something about the G1 button. Someone else had some trouble yesterday with it, but it turned out they correctly set the G-key as the HotKey, but they also put the G-key to send to "all other" in the mapping -- which is going to do nothing in the other windows because WoW doesn't recognize the G-keys. So make sure you're not doing something like that
RE: RE: Assigning X-keys
Reply With Quote
Connect With Us