Inner Space Support of Logitech G-line of input devices
Moderators: Lavish Software Team, Moderators
No. Logitech does not use standard behavior for their custom buttons. The media buttons do, which is why they appear in inputdevices.xml.Vdera wrote:So, there's no way to just manually add the G buttons, using the same code layout as media buttons?
Nope. I need the information on communicating directly with the hardware, and that would just be emulating keystrokes.Also, the latest Logitech SDK contains software to emulate the G19 keyboard, not sure if that could be used as a replacement to allow you to get the data you need to add support for it.
Hey Vdera,
I have a G15 and a G13 hooked up right now. Even though I can't map keys directly with InnerSpace to the G13 I can still use the Logitech profiler and point those keys to ingame keybinds, etc. So I have my G22 key is my assist button so I don't have to reach to the G15 to press a G-key.
I would sure like to see support for the G13 as well and may donate to the cause.
I have a G15 and a G13 hooked up right now. Even though I can't map keys directly with InnerSpace to the G13 I can still use the Logitech profiler and point those keys to ingame keybinds, etc. So I have my G22 key is my assist button so I don't have to reach to the G15 to press a G-key.
I would sure like to see support for the G13 as well and may donate to the cause.
Okay, anyone with a G13 or G19 (or any other currently unsupported device) I have a new program that can collect the data required to support these and other devices.
http://www.lavishsoft.com/downloads/Lav ... Tester.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. 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:
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 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.
http://www.lavishsoft.com/downloads/Lav ... Tester.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. 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:
Code: Select all
050D-0815 v210 (Unnamed Device): Button 1 at bit 72
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 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.
Does that mean that we might be able to see native support for the N52 buttons soon (without having to use their software to emulate keypresses)?Lax wrote:That's about it. As far as device configuration and not producing output, here's an example. The output example I gave 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.
No, it does not mean that: n52 has been supported for years. To configure your n52 to work with Inner Space, switch all of the buttons to "DI Button" mode. Then you need to do some voodoo in IS's InputDevices.XML file -- see http://www.dual-boxing.com/forums/index ... post200804 for instructionsDoes that mean that we might be able to see native support for the N52 buttons soon (without having to use their software to emulate keypresses)?
Oh, okay, something I didn't know! Good deal.Lax wrote:No, it does not mean that: n52 has been supported for years. To configure your n52 to work with Inner Space, switch all of the buttons to "DI Button" mode. Then you need to do some voodoo in IS's InputDevices.XML file -- see http://www.dual-boxing.com/forums/index ... post200804 for instructionsDoes that mean that we might be able to see native support for the N52 buttons soon (without having to use their software to emulate keypresses)?
I posted a response on dual-boxing.com about the output from your program for the G13.
http://www.dual-boxing.com/forums/index ... post211184
Signed up for a year, and pretty impressed so far.
http://www.dual-boxing.com/forums/index ... post211184
Signed up for a year, and pretty impressed so far.
Experimental G13 support is now in the IS development build, now I need someone who can test it. See me in chat -- http://www.lavishsoft.com/chat/isboxer.php -- if you can test the G13 or have another unsupported input device (G19, etc)
G13 support is now tested and functional in Inner Space build 5011 (buttons only -- including joystick press, but not joystick movement, which can still be configured via the logitech profiler). Still need someone with a G19.
X-keys device support should be functional for any new X-keys USB devices as of build 5011, but I don't have confirmation on that. Older X-keys USB devices were already supported.
X-keys device support should be functional for any new X-keys USB devices as of build 5011, but I don't have confirmation on that. Older X-keys USB devices were already supported.