G-Series Gaming Keyboards

[Trusselo]

it would be a "standard function" if repeat worked right!

[crayzihorse]

LCDMon has crashed a few times over the last week, since i have been using 3.03 Beta. after a crash i am told that there aren't any programs for it to run. when i look in the "Programs" section only the Logi* Key Proiler and Scripting Display are in the list.

kill/restart of associated processes doesn't re-populate the list and neither does a complete reboot of the machine. the applets missing are in the usual place.

what way do i go about fixing this? reinstall?, uninstall/reinstall?, execute individual applets?

[Trusselo]

what OS are you?  i havent had problems with crashing with 3.03..  but i do always have problems with the WMP sideshow app (microsoft).   I always turn it off right away. it will continue to play music after CLOSING wmp.  WMP will stay open in task manager no matter what untill you terminate pocess.  try turning off that app in the control panel> sideshow settings.

[crayzihorse]

i have come across a situation where the profiler isn't cleaning up properly. since this is Beta i thought i would post it here instead of just fixing the prob and moving on.

i created a new profile using "Copy from an existing profile". i then customised the new one replacing various keys. eventually i came to making a macro for CTRL. i replaced the singlekey CTRL with a multikey CTRL and hit an error with the message "a macro with the same name already exists..."

after a few fiddles in the profiler, disabling the G key where Ctrl was and double checking the macro manager for other instances i closed the profiler and searched the lgp file. i found one reference to Ctrl, a singlekey, and left it there.

i went back into the profiler and no matter what i did, this key would not get removed. since i was doing this profile anyway i went through the keys in every M set. no key was using that macro and there weren't any unused macros either.

even though i could just call the key CtrL or whatever, i really i don't want to leave any junk in the profiles, so i'll have to delete this entry. does anyone know how far off is the next release candidate is?

EDIT: i just had a better look at the lgp in question and it is full of same-name keys and macros that no longer exist in this profile. are these hangovers from importing from another profile or maybe from quick macros?

Message Edited by crayzihorse on 09-18-2009 06:52 AM

[windycityblues]

Okay so hopefully you guys can help me out. I got a G13 to use the analog stick to move with WOW. I've downloaded the beta and enabled joystick. I can go into game controller manager in vista (64) and it shows the g13 and calibrates beautifully. When I try to test profile the joystick movement doesn't register anything. Should it? I still have no movement in game as well. I have admin and profile lock on. Any help is greatly appreciated.

[Trusselo]

nothing should show in the Test window for joystick

WOW doesnt support analog control.  Use "Assign keypress" and do W A S D.  the 4 direction is actually 8. the diagonals will do  WA  AS SD DW.

[windycityblues]

Didn't seem like there was analog support after reading about the guys wanting to use their x360 controlers. Thanks I'll mess with it more tomorrow. Now if I assign the wasd to the stick can I take the wasd recognition off of g4, g10, g11, and g12? The game recognizes those g keys as the wasd keys as well as the stick. Any ways around it?

[Trusselo]

yup, here is where you get to customize and create the feel you want. you can take WASD off ALL the keys if you want. you can use your keyboard for that still if you wanted and have only special stuff and macros.

[MadGizmo]

I was excited about the software at first, but the analog joystick didn't work properly.

I wasn't able to calibrate the joystick and the crosshair in the "Test" tab of the "Properties" of the "Logitech G13 Joystick" didn't move at all, no matter what direction I pushed the thumb stick to.

But... I was able to get it working after all.

This is how I did it:

1. Open the "Logitech G-series Key Profiler".
2. Create a new profile and name it "Calibrate".
3. Click the "Select using the GamePanel display" radio button.
4. Click the "Lock profile while game is running" check box (make sure it is tagged).
5. Click the "OK" button.
6. From the "Edit" menu select "All G-keys" and click "Disable".
7. Click on one of the 5 thumb stick parts in the profiler. A popup menu appears. Click the last option, called "Assign Joystick".
8. Open the "Game Controllers" applet in the Windows "Control Panel".
9. Select "Logitech G13 Joystick" in the list box.
10. Click the "Properties" button and a new dialog window appears.
11. Click the "Settings" tab.
12. Click the "Calibrate" button and the"Game Device Calibration" wizard appears.
13. This is important: Watch the G13 display. It should read "Select OK when this game is running: Calibration". There will be a "tag mark" and a "X" on the display. Press the button below the "tag mark" on the G13. You should do this only after the "Game Device Calibration" wizard appeared.
14. Follow the instructions of the wizard. Note that the wizard asks you to "press a button on the controller" from time to time. You need to press the joystick like a button (and not move it left, right, up or down) whenever the wizard prompts you with that. You'll notice that the wizard moves to the next step when you do that.
15. At the end of the wizard's steps press the "Finish" button and the wizard will close.
16. You can now test the thumb stick in the "Logitech G13 Joystick properties" dialog by pressing the "Test" tab. You'll notice that the thumb stick is working fine now. If you press the thumb stick like a button then the red "1" in the"Buttons" section lights up now too.
17. Press "OK" to close the "Logitech G13 Joystick properties" dialog.
18. Press "OK" to close the "Game Controllers" applet.

That's it. Everything should work fine now.

BTW: I've tested this on Vista x64.

[MadGizmo]

BTW: My previous workaround to calibrate the thumb stick is required because there seems to be a bug in the driver software. When testing or calibrating the device it will still use the current profile. It shouldn't do that all. Example: Saitek devices don't do that. They are able to run the control panel applet without a similar workaround and the applet even works if all keys and axis have been mapped to keys. So, that must be doable for the Logitech magicians as well.

Message Edited by MadGizmo on 09-20-2009 04:11 AM