Inner Space Support of Logitech G-line of input devices

JamieW · Post by **JamieW** » Mon Feb 02, 2009 3:17 pm

I currently have an old G15 keyboard w/ 18 G-keys.

I'm contemplating on purchasing a G13 keypad to augment my input capabilities. Right now, I know that Inner Space provides native support for the G1 through G18 keys in scripting / binding by binding them to each key by name.

If I were to add the G13 to my system, would Inner Space support both devices' G-keys? Does anyone have any experiences to share, etc.?

I was hoping to get some input before going out and spending the $75 on the new gamepad.

Thanks!

Post by **Lax** » Mon Feb 02, 2009 5:09 pm

Assuming the G13 follows similar technical details as the G11 and G15, the G13 is not yet natively supported by Inner Space.

However, it would probably take me an hour to add support for the G13's buttons with your help.

I do want to pick up a G13 myself for testing and development purposes, but I don't know when exactly that will be.

trevyn · Post by **trevyn** » Mon Feb 16, 2009 11:15 am

Hi!

I am also using a G13 - so if you tell me what information you need - I am in

madman · Post by **madman** » Wed May 06, 2009 7:11 pm

I recently purchased a G13 and tried to set it up with WOW today, just to find out that no bound key ever reaches WOW, is this due to lack of G13 support or am I doing something wrong?

I previously had a N52te which worked great with IS, using mostly keymap features to multibox. I installed the G13, assigned my old "keyboard" keys to the G1-G22 buttons on the G13, and none of them do anything in WOW when running with IS. Pushing them in the ISBoxer config input windows doesn't do anything either. Pushing them in a regular windows input control (like Notepad for example) registers keypresses okay.

When I run WOW without IS, the keys work as well.

Am I missing something? Or is this due to G13 being unsupported? Which kinda confuses me because I thought I don't need native support for the Gxx keys if I map them to regular keyboard keys.

I'm running Windows7 x64 and using the x64 version of the Logitech software.

Post by **Lax** » Wed May 06, 2009 8:11 pm

I believe the issue would be due to running Inner Space (and therefore WoW) as Administrator, and not running the Logitech software as Administrator. The elevated user permission probably prevents the Logitech software from sending input to the game. I'll have to see about lowering the game priveleges to normal (and solving the Vista/Win7 compatibility conundrum that requires Administrator if UAC is enabled).

So I think you've got 2 choices at the moment:
1. Disable UAC
2. Run the Logitech software as Administrator

And no, the lack of G13 support only means that IS itself is not interacting directly with your G13, it should still work as long as the software has permission from Windows.

madman · Post by **madman** » Thu May 07, 2009 1:49 am

Thanks for the quick reply Lax! You were right. I disabled UAC for a test drive and then it all works. I'm going to try and see how I can run the Logitech drivers as administrator, because running only the profiler and the LCD app as admin doesn't seem to be enough. I'm trying for something less radical than disabling UAC

I'll update my findings here if I manage to get it working.

madman · Post by **madman** » Thu May 07, 2009 5:37 pm

Got it working with UAC enabled now as well, makes me feel a lot better about the security. I had to make a task scheduler entry to run lgdcore.exe with elevated privileges at startup, because simply ending the profiler via task manager and re-starting it manually with admin privileges didn't seem to work. Lgdcore.exe is the only one of the 3 logitech entries from start-up that needs to be elevated, the others (basically the panel stuff) can be left at regular privileges.

Suggestions were spot on, Lax, thanks! I'm now eagerly awaiting native support of those many G-keys

cali · Post by **cali** » Thu May 14, 2009 12:41 am

I have the same problem, G13 doesn't work with IS, what is UAC ?

madman · Post by **madman** » Thu May 14, 2009 6:27 am

User Account Control, a security layer in Vista and Windows 7. Basically it prevents software that requires administrative privileges from running unless you specifically allow it to.

The "easy fix" for the problem was to turn UAC off. To do that, go to Control Panel -> User Accounts and select "Change User Account Settings", then you''ll get a window with a slider that you can turn all the way down to disable UAC. This is really easily done, I personally didn't like it because it had me disabling something I actually consider a useful Windows mechanic.

The "complicated fix" consists of starting the G13 software with administrative privileges. To do that, I had to use the task scheduler. Basically you just create a regular task to be run at windows startup, and you have it pointing at LgdCore.exe with the parameter /SHOWHIDE to run minimized. Try Google for howtos on the task scheduler, there are a quite few available and explaining it all here would be too complicated (if you ever had to use the task scheduler run stuff like rivatuner/RTSS/EVGA precision, it's the same procedure, just a different executable).

cali · Post by **cali** » Thu May 14, 2009 4:18 pm

Ok thx
It work

Vdera · Post by **Vdera** » Wed May 20, 2009 12:05 pm

Whilst on the G series topic, would it be possible to provide native support for the G19?

I'm happy to help out in any way I can in order to get it up and running.
It's inclusion in Innerspace would be a huge help for me and it would be greatly appreciated.

Post by **Lax** » Wed May 20, 2009 12:09 pm

For any currently unsupported Logitech device, I have to actually have one in my hands to add support; Logitech does not provide technical documentation for natively supporting their devices.

I don't currently have money to spare to do this (I'm behind on a few bills, I recently moved back to my old house to save $$ every month) -- if anyone wanted to donate for the purpose of adding support, you can send a paypal donation to lax@lavishsoft.com and put a note on it about device support. Or if someone lives in MI and wants to let me borrow their device (I live in Grandville, MI) I can do it that way as well.

Vdera · Post by **Vdera** » Wed May 20, 2009 12:43 pm

So, there would be no way for me to press keys and tell you the values they return? That's a shame

Vdera · Post by **Vdera** » Wed May 20, 2009 4:45 pm

Not sure if it's worth anything, but there is a listing in my InputDevices.XML for the G19, but it only lists the media keys, as below.

<Set Name="046D-C228 G19 Gaming Keyboard (7-input)">
<Set Name="Buttons">
<Setting Name="0">Volume Decrement</Setting>
<Setting Name="1">Volume Increment</Setting>
<Setting Name="2">Mute</Setting>
<Setting Name="3">Play/Pause</Setting>
<Setting Name="4">Stop</Setting>
<Setting Name="5">Scan Previous Track</Setting>
<Setting Name="6">Scan Next Track</Setting>
</Set>
</Set>

Post by **Lax** » Wed May 20, 2009 5:16 pm

Yeah that's just for the media buttons on the device