Logitech G15 Key Binds not Working for me
Moderators: Lavish Software Team, Moderators
Logitech G15 Key Binds not Working for me
Has anyone who has a G15 Keyboard noticed if they can bind any of the following keys and get a response?
G3
G17
M2
M3
Play/Pause
I wrote a test app to test these binds and those are the only keys that don't seem to respond. Can anyone else verify that these are working correctly? Or is this a bug?
Thanks!
Tyric
G3
G17
M2
M3
Play/Pause
I wrote a test app to test these binds and those are the only keys that don't seem to respond. Can anyone else verify that these are working correctly? Or is this a bug?
Thanks!
Tyric
Code: Select all
[g3] [g3] Command (Release): echo "test"
test
test
test
test
test
Bind 'g3' removed
[g17] [g17] Command (Release): echo "test"
test
test
test
test
test
test
test
Bind 'g17' removed
[m2] [m2] Command (Release): echo "test"
test
test
test
test
test
Bind 'm2' removed
[m3] [m3] Command (Release): echo "test"
test
test
test
test
test
Bind 'm3' removed
[play/pause] [play/pause] Command (Release): echo "test"
test
test
test
test
Ok, I have tried rebooting and it seems to be starting something up or something is programmed in, where even though I don't have my profiler running, I'm still having the same problem. When I hit the G Keys while in the console, the key I programmed are still popping up in the console.
I am making sure that LGDCore.exe is not running... closing it down completely. LCDClock.exe and LCDMon.exe are running, but those are LCD apps and shouldn't be interfering.
The thing that confuses me is that the rest of the keys except those work fine with my profiler running. My profile isn't setup with macro's... just duplicating a specified keypress. There is one noticable coincidence with all the keys that don't work.. They all return an extra character with the same wierd behavior.
here are my mappings:
G1: 1
G2: 2
G3: 3
G4: 4
G5: 5
G6: 6
G7: Q
G8: W
G9: E
G10: A
G11: S
G12: D
G13: Z
G14: X
G15: C
G16: V
G17: B
G18: N
if I press them in the console I would expect the following text:
123456qweasdzxcvbn
This is what I actually get cut and pasted after doing that and hitting enter:
wn command '123456qweasdzxcvb'
It's really wierd. The play/pause button gives the same wierd
Unknown command '' character.
Is this a bug with the profiler and those keys maybe?
I am making sure that LGDCore.exe is not running... closing it down completely. LCDClock.exe and LCDMon.exe are running, but those are LCD apps and shouldn't be interfering.
The thing that confuses me is that the rest of the keys except those work fine with my profiler running. My profile isn't setup with macro's... just duplicating a specified keypress. There is one noticable coincidence with all the keys that don't work.. They all return an extra character with the same wierd behavior.
here are my mappings:
G1: 1
G2: 2
G3: 3
G4: 4
G5: 5
G6: 6
G7: Q
G8: W
G9: E
G10: A
G11: S
G12: D
G13: Z
G14: X
G15: C
G16: V
G17: B
G18: N
if I press them in the console I would expect the following text:
123456qweasdzxcvbn
This is what I actually get cut and pasted after doing that and hitting enter:
wn command '123456qweasdzxcvb'
It's really wierd. The play/pause button gives the same wierd
Unknown command '' character.
Is this a bug with the profiler and those keys maybe?
wierd... the forums are filtering out the wacky characters...
Lemme try this:
Lemme try this:
Code: Select all
g3: Unknown command '
3'
g17: Unknown command 'b'
M2: Unknown command ''
M3: Unknown command ' '
Play/Pause: Unknown command ''
Just to follow up on my own resurrection of this topic, I have a workaround for this problem. I'm posting with the hopes that it helps someone else.
I was not running the profiler, which seems to work for me on and off. Whenever it's not working, simply running the profiler then exiting it solves the problem for me. Before exiting the profiler, I usually have it set to a profile where all the keys are undefined, but I'm not sure if this has any real effect on solving the problem or not.
I was not running the profiler, which seems to work for me on and off. Whenever it's not working, simply running the profiler then exiting it solves the problem for me. Before exiting the profiler, I usually have it set to a profile where all the keys are undefined, but I'm not sure if this has any real effect on solving the problem or not.