Logitech G series and ISBoxer

I've been getting my head around ISBoxer and Multiboxing in EQ2 for a week or so now. It's been quite a learning experience. I've got lots of questions, but I was hoping to begin with a question I've seen asked elsewhere (and can no longer track down), but not here.

Exactly which products in the Logitech Gaming series peripherals ARE supported, and which are planned?

I'm currently using a G9x mouse, which I've used the Logitech software to map macros to the forward and back buttons that allow me to switch windows.

I also use a G13 game pad (which is supported but I can't get any of the M1-MR light toggles to work) and a G110 keyboard (G19 without the LCD) which it doesn't recognize.

I'm working on a single PC 6 box solution and having a stockpile of keys seemed like a good idea. I've been able to make use of most things through a combination of ISBoxer and the Logitech macro software, but it'd be nice if everything was recognized (I know, a lot to ask).

Also, just a general note I stumbled on to and stumbled on to the fix. When I first set ISBoxer up with the logitech peripherals I was having issues with ISBoxer/Inner Space stopping in the middle of loading my EQ sessions. This would go away if I shut off the Macro Profiler for the G13 (Whatever the specialized version of SetPoint they install with the hardware).

In any case it turns out that while they use the name SetPoint for the software it is not the same as the older SetPoint software used in other logitech products (like the one I replaced when I got the new keyboard). It doesn't uninstall the old SetPoint but leaves it in and sets them both running. This led to the weird conflicts I was having in ISBoxer.

Thanks for a great product. You've made Everquest 2 fun again.

[lax]

I also use a G13 game pad (which is supported but I can't get any of the M1-MR light toggles to work

The M1-MR lighting features in ISBoxer are labelled as G11/G15 features, and that is accurate. IS does not yet support the M-lights on the G13. I didn't have one to test with at the time I added support for the buttons, so making lights work was out of the question. I do have one to test with now, but I have more critical issues to deal with at the moment (e.g. some games not working correctly) so I can't promise you an ETA on that.

As far as natively supported Logitech devices, the list is currently: G11, G13, G15, G19. The lighting features work on the G11 and G15.

The G110 is new and I haven't had anyone ask about it yet. To get it supported, here's a copy/paste...

I have a program that can collect the data required to support these and other devices.
http://www.lavishsoft.com/downloads/Lavish.ButtonTester.exe

To use it:
1. Make sure the device is plugged in and operational
2. Run Lavish.ButtonTester.exe. It will open a DOS window to show its output.
3. When it says "Waiting for input..." it is ready for you to start hitting buttons on the device
4. Press each button in an order that makes some sort of sense -- the program is going to tell you some numbers, in the order your buttons are pressed. Make sure to know the order you press the buttons, so they can be matched up to the output for supporting the device. If you hit a button and do not see anything happen, the device may be emulating a keyboard at the hardware level, which means it either needs to be reconfigured, or it will not work. Otherwise, you should see output like this:

050D-0815 v210 (Unnamed Device): Button 1 at bit 72

5. Get me the complete list
6. Wait for me to add support for the device

That's about it. As far as device configuration and not producing output, here's an example. The output example I gave (above) is with a Nostromo Speedpad n52 (not n52te). The n52 by default emulates the keyboard, and to show up as buttons on the device instead of keyboard buttons, each button had to be configured as a "DI Button" (Direct Input Button). With a Logitech G15 keyboard, each button must be "Unassigned" (via the Logitech Keyboard Profiler), so I would expect the same from a G13 or G19.

As far as planned, it doesn't really matter. I can support most input devices. It's nice when the input devices conform to standards so I don't need to make people run a program like the one above to support them (absent actually having the device myself). It seems most of the device manufacturers don't really care about standard support, they'd rather build custom macro software.

Lax, I appreciate the work you're doing and that you're even willing to investigate such requests. I'll try to get you data for the G110 this weekend. I do programming as well (all though of a far less interesting type), and get my priorities shifted around enough on the holidays that I wouldn't try to pull that on anyone else.

Ok, if I got this right here are the keys for the G110:

G1 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 1 at bit 8
G2 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 2 at bit 9
G3 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 3 at bit 10
G4 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 4 at bit 11
G5 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 5 at bit 12
G6 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 6 at bit 13
G7 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 7 at bit 14
G8 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 8 at bit 15
G9 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 9 at bit 16
G10- 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 10 at bit 17
G11- 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 11 at bit 18
G12- 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 12 at bit 19
M1 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 13 at bit 20
M2 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 14 at bit 21
M3 - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 15 at bit 22
MR - 046D-C22B v100 (65280,0,4)(G110 G-keys): Button 16 at bit 23

Let me know if you need more info or if I did anything wrong.

Thanks.

[lax]

(Slight apology here to RogueFury who got me the data a night or two ago and was also waiting on this)

The development build of IS (build 5071) now has Logitech G110 button support (no lighting features). To switch to it, right click IS and select Patcher, then check "Download development (test) patches", and restart IS to allow it to patch. If you're already on the development build just restart IS. To switch back later if you have problems do the same thing. If the G110 is plugged in when you relaunch IS, it will be detected. Shut down IS again in order to save the detected device, then launch ISBoxer. The G110 buttons should then appear as G110-G1, etc. in the drop-down box in any Hotkey Picker window.

Let me know if it works or not, it should but I can't test it myself.

Cool. Was able to remap keys. Will be testing today. If you don't see a reply, they work.

Thanks for the fast update.

Works like a charm.

Hey.

I am using the Logitech G19 keyboard and its apparently not supported for assigning the G buttons yet.
I have downloaded the Lavish Button Tester program and here is the keys:

M1: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 1 at bit 20
M2: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 2 at bit 21
M3: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 3 at bit 22
G1: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 4 at bit 8
G2: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 5 at bit 9
G3: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 6 at bit 10
G4: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 7 at bit 11
G5: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 8 at bit 12
G6: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 9 at bit 13
G7: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 10 at bit 14
G8: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 11 at bit 15
G9: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 12 at bit 16
G10: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 13 at bit 17
G11: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 14 at bit 18
G12: 046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 15 at bit 19

Thanks in advance.
Team Howster

[lax]

G19 is indeed currently supported. If you got a new device and are hooking it up for the first time, do the following:

1. Plug it in and then launch Inner Space. Inner Space will detect the device
2. Exit Inner Space. This will cause it to save the detected device info
3. Launch ISBoxer. ISBoxer reads the device info from the saved Inner Space settings
4. G19 keys should now be in the drop-down box in any Hotkey Picker window (but will not be detected by the "press key here" box)

G19 is indeed currently supported. If you got a new device and are hooking it up for the first time, do the following:

1. Plug it in and then launch Inner Space. Inner Space will detect the device
2. Exit Inner Space. This will cause it to save the detected device info
3. Launch ISBoxer. ISBoxer reads the device info from the saved Inner Space settings
4. G19 keys should now be in the drop-down box in any Hotkey Picker window (but will not be detected by the "press key here" box)

Ok. I tried this but still cant find the G Keys from the drop down box in any hotkey window. This worked very well with my prevous G11 keyboard before some keys broke and had to replace that G11 Keyboard. I've had this keyboard for about 2 months now but without any detection of my device. (thats the reason i thought it might wasnt supported yet). Using a key remapping feature to be able to use the G buttons atm (G1 = Ctrl + Num1 etc...). Maybe its because of me upgrading the keyboard and Innerspace cant overwrite the config? (Just having a few guesses here ).