G-Series Gaming Keyboards

[Sir Saber]

Hello dear Logitech friends, I have recently having a little problem with my G13. When I start up my PC ( win7 64bit ) everything seems to work fine with my G13 ( I can change the LCD screen, change profiles etc ) but if I try to play with it nothing happens. So I open up a blank Txt file just to see if it's the game who's bugging and indeed my G13 doesn't perform what I configured it for. WASD doesn't appear neither all the ALT, CTL, NUM buttons I've configured. So I try to unplug it and replug onto another USB slot, nothing. I restart my PC -> Nothing I restart my PC again -> It's working again ... I really don't know what could be causing this, I've tryed all my usb slots and it does it with every single one of them. Could it be that my 4 years old G13 is having alzheimer ? Thanks in advance for your support !

[bystander]

Is the profile you want to use active?  If you use Steam, you also have a harder time to get the profiles to automatically open when the game opens.  You have to set the profile go to the steam game at the folder C:\Program Files (x86)\Steam\steamapps\common.

You can also use the profile selector on the LCD display to select the profile you want active and lock it.  The last method that I'm aware of is to make it the default profile within the Program Manager.

[Sir Saber]

Thanks for the answer but that's not really it. I do not use Steam and I don't have any problems changing my profiles. My problem is that when I hit the buttons nothing happens, all my Gbuttons are keybinds and they don't work at start up. So if I have 1234567890 as my Gbuttons and I want to type it in a .txt (just to test the buttons out) file it won't work, also it doesn't work in games or anywhere else. I have to restart my PC as often as needed until the keybinds work again. I hope I've explained my problem somewhat better this time ^^'

[Asfodelo]

Exactly the same problem.

Any solution?

[kgober Logi Guru III]

the number one cause of keybinds not firing is that the profile you think is running isn't actually running at all.  all keybinds are associated with a specific profile, and if that profile isn't active nothing will happen.  usually profiles activate themselves automatically based on the programs you run, but sometimes this can break down and you may have to tweak things manually using features like 'persistent' profiles and 'locked' profiles.

also, the G13 functionality is dependent on the Logitech software.  if the software isn't installed, or it's not running, or it's damaged in some way, things won't work.  installing the latest version of the software isn't always a good solution when you're having problems.  I have found the most reliable version of the software to be the "legacy" version, v3.06, but if you downgrade from v7 or v8 drivers to v3.x you may have to recreate your profiles.

make sure when installing the software that you run the installer as admin.

-ken

[Asfodelo]

Thank you for your reply.

I'll try that but it sounds strange that the profile "sometimes" loads and "sometimes" doesn't.

Windows "is a kind of magic" anyway 

[kgober Logi Guru III]

typical causes of profile problems:

having two or more profiles for the same game or program.  in that case, the Logitech software might run a different profile than you think it should.  this is especially troublesome when you weren't aware that more than one profile even existed, for example because you backed up profiles to your G13 on-board memory.

rapid changes in foreground applications might cause the Logitech software to lose track of which application has focus, and therefore affects which profile is active.  applications that have popups that grab focus for a very short time will often cause this.  common apps include software update notifications, security software popups and media player notifications.

running with insufficient rights might prevent the Logitech software from being able to identify the foreground window.  if this happens, make sure the software is running as administrator.  note that this issue only applies to certain older versions of the software.

-ken