Innerspace Windowsnapper, Repeater, and a little extra sumptin sumptin

Quote:

---

Originally Posted by 'Lax',index.php?page=Thread&postID=165972#post1659 72

Quote:

---

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 :)

---

Hrm, I must be missing something with X-keys. It's new and I haven't assigned anything to most of my keys. I didn't think I needed to for IS, but that may be where I'm getting lost. I run the buttontest script fine, but when I hit the X-keys buttons it doesn't tell me any button name. All but five of my keys are blank and have no macros assigned to them. When I hit those buttons I get no output at all in IS, while running the buttontest script. When I hit one of my buttons with a macro assigned to it reports the output of the keys I assigned in the macro. For example, if I hit my X-key button that has {Shift+1} as its macro, the output in IS is:

Button=Shift position=TRUE
Button=Shift position=TRUE
Button=1 position=TRUE
Button=1 position=FALSE
Button=Shift position=FALSE
Button=Shift position=FALSE

I don't see where it's ID'ing that X-key button. When I hit a G1 key I get:

Button=G1 position=TRUE
Button=F1 position=TRUE
Button=F1 position=TRUE
Button=G1 position=FALSE
Button=F1 position=FALSE

That makes sense, I can see that it's the "G1" button. Not sure why it's set to F1, but that's another issue. :)

I find my Xkey buttons in the InputDevices.XML too, btw.

Am I missing something in setting up my X-keys, or is this an IS issue? Thanks for your help!

Thanks Balst3r for the setup, but now I have a few more questions (at work, so no chatting it up on the IRC), just going to go ahead and ask them here so I have a place to look back on if I screw something up...

OK, for the most part *IS* is working great, better than I had thought, but now its getting to the point where I need to make it work the way I want it to work (or at least hope that it will work). Right now, I am running multiple setups: 5 Warlocks, 5 Shamans, 4 huntards and 4 mages, then mixing the groups (4 huntards and a shaman) (4 mages and a shamana) (4 shamans and a DK/Pally)... so for the most part, aside from the lock group, I have a shaman in there healing. The hardest part I have is that don't always run Dungeons, I mix it up with doing Quests, so then it goes back to being 4 hunters and or the 4 mages. The 5 Shamans have their setup with having person A as Master, and Person B, C, D, E as the slaves and thats how Jamba sees it. But the second I go to put the Shaman in the huntard group or any group that does not see (shaman A *master*) as lead, he does not acknowledge Master A as leader, so I have to make certain macro for him to assist party1, or how ever I do it. Aside from having to go into Jamba on the Shaman and tell him that A (Master) from the hunter or mage group is Master, then I don’t know of any other way around this.

Now, onto some other questions...

The repeater thing, I have Agorons *spelling, sorry* IS setup, and its beeng working for the most part but as far as I can tell the black list, which I got from Propagandalf which (blacklsits W,A,S,D and Enter). So, I would have thought with those being blacklistsed, it would not send it to anyone other than the A (Main/Master, toon on Main screen) but when I bound W,A,S,D to a slave to test it out, it sent it to both... Not sure what went wrong, or maybe it does not do what I thought it did.
As for what I thought it did, and how it would be used, is if my A (Main/Master) dies then I can go to B (slave) and his W,A,S,D would work.

Next, Question...

There was an Addon *open something, Lax told me the name* that I saw in Zanthor's movie where it healed upon click. It was framed just like grid or any other type of framed mod. From my understanding, he was using a different toon and it healed while he was tanking with a Paladin I believe. Now, yes, I could just press a button and have that person heal someone else, but what I would like to have is my tank, click a person's name and they get healed by me clicking the grid (also, have the said person(s) healing on Round-Robin). (THAT WOULD BE ASWSOMESAUCE)...

There are some other questions but as I am at work, I have other things on my mind.... so I forgot them. The above questions are my main concern for me getting IS to work the way I want it too...

Ok, I ran the buttontest script and my x keys usb is not spewing bits. My g15 and mouse are fine and the "bind -keylist" reports all the button 1 through button 99.

I can start the x keys macroworks and it recognizes the keypad, but IS is not showing keypresses with or without macroworks.
I deleted the set for xkeys in inputdevices.xml , closed IS then saved the file and let it recreate on next startup and there was no change.

Any ideas?

[quote='moosejaw',index.php?page=Thread&postID=1663 78#post166378]Ok, I ran the buttontest script and my x keys usb is not spewing bits. My g15 and mouse are fine and the "bind -keylist" reports all the button 1 through button 99.

I can start the x keys macroworks and it recognizes the keypad, but IS is not showing keypresses with or without macroworks.
I deleted the set for xkeys in inputdevices.xml , closed IS then saved the file and let it recreate on next startup and there was no change.

Any ideas?[/quote]

Yeah, I'm having the same issue. Sucks, as I really want it to work with Innerspace. According to the people in IS IRC their Xkeys just worked out of the box with IS and didn't need to do any set-up. So, something must be different with ours. Is your Xkeys new? Which model is it?

I tried installing an older version of macworks v. 1.0, as v. 1.01.2 (or some such) came with my keyboard, thinking maybe an older driver would install. No luck.

I d/l'ed the [url='http://www.xkeys.com/software/memresident.php']Macro Recorder[/url] but I couldn't get it to work with my XKeys (58 key professional, btw). It may not be compatible and the documentation isn't clear on which models are.. or atleast they contradict each other in various help files. Anyways, it has an option to "unprotect" your keyboard and to clear your keyboard, etc., but again it won't work my mine. I get an error saying it can't find my keybaord, or some such. A troubleshooting help file mentions an executable on the disc called SPLAT to try, but that didn't work either.

That's as far as I got before I got too busy with RL and too fustrated to mess with it any more.

If you find any solution please keep me posted! :)

It's really too bad that they (apparently) changed something with X-Keys and the newer ones don't work the same. There's a lot of people that do have the older ones (Zanthor is one) and they work great. You might want to shoot them an e-mail and ask them why the newer devices apparently don't work with DirectInput -- maybe they can change something back to the way it was before.

Otherwise, if nothing shows up from buttontest.iss, you may be forced to have the X-Keys buttons translate to key combinations :( What I would probably do is have them translate to something like CTRL+ALT+SHIFT+<key> via the X-Keys software, and then you can create IS binds or key maps using those key combinations instead of mapping directly to the X-Keys buttons.

I sent an email to X-keys support, I'll let you know if I hear anything.

I purchased my x keys usb this year. Serial # 824883 Model # PIE002-15D.
I also have a PS/2 model which I have been using with premapped hotkeys but I think the USB model and IS would be much, much more flexible.

edit: By this year I mean 2008. :rolleyes:

I got a response from someone at PI Engineering:

Quote:

---

Hello Scott,

We had to update our firmware to provide Vista (and 7) support and the
Product ID and report structure changed as a result. The new firmware
is called "MWII" and the previous generation is called "SE"

If you could put us in contact with the Innerspace developer, we would
be happy to assist him in recognizing our new generation of X-keys.

Macro Recorder is not compatible with the MWII firmware, but
alternatively, we have a Beta version of a new X-keys Hardware Mode
Programming Utility which I could send to you. This would allow you to
program keyboard macros and mouse functions into the X-keys.

I hope this information is helpful. Feel free to contact me with any
questions.

Dan Slider
Director of Sales and Customer Service

---

I hope you don't mind Lax, but I mentioned your program and how you thought that something had changed, specifically having to do with "DirectInput". I'm going to PM you his email with the hope that you could email him (when you get a chance) and find a fix. ...please :) It'd be greatly appreciated! :D

So this appears to be Directx/Direct input not recognizing the new firmware? So it would be a Msft issue with base drivers?

I have a fresh install of Vista 64 and the only way the usb xkeys works is with MWII. I do not think Lax can correct this although the folks at PI have been very responsive to our market and may have a quick fix. Here is to hoping a solution is right around the corner.

Quote:

---

Originally Posted by 'moosejaw',index.php?page=Thread&postID=167215#pos t167215

So this appears to be Directx/Direct input not recognizing the new firmware? So it would be a Msft issue with base drivers?

I have a fresh install of Vista 64 and the only way the usb xkeys works is with MWII. I do not think Lax can correct this although the folks at PI have been very responsive to our market and may have a quick fix. Here is to hoping a solution is right around the corner.

---

Not a problem with DirectInput. The issue as I understand it is that the driver isn't fully compatible with DirectInput. I should be able to implement support for the alternate method, but it's going to be a few days before I can get to it. If you can get the X-keys guys to restore DirectInput support that'd be great, but the e-mail sounds like they would rather I work on using a different API.