K95 problem with pressing two G key concurently

[ChrisR]

Hello

 

I'm encountering a problem when trying to program G keys to do continuous playback.

What I'd like to do is to have G keyboard keys (linked to in-game commands) continuously send a specific keycode when pressed and kept pressed.

(user case: in WoW, press an action key while user commands are in global cooldown, so that the command fire the instant the GCD is over)

 

Setup:

 

I use the K95 keyborad configuration software. I set it up for "hardware playback" ("software playback" is not suited for what I want to do, but that's beyond the point I want to outline).

 

I create two macros (with numbers 1 and 2) like the one below:

(1) down

0.050 seconds delay

(1) up

 

I assign each macro to a different G key (say G1 and G2).

For each key, I select the continuous playback option (ie it should repeat the macro over and over again) with a delay of 0.050 seconds.

 

When I use press both key independantly, things works as expected: I get either a long strings of 1 or a long strings of 2.

 

Problem:

 

The problem arises when I press both G keys either simultaneuosly or one after the other in rapid succession.

 

Specific case: I press G1, while G1 is pressed I press G2, wait a little and then depress G1 while keeping G2 pressed.

I would expect a long string of 1 followed by a long string of 2 that keeps going even after I depress G1. (like 1111111111111111222222222222222222)

 

The result I get is that everything stops the moment I depress G1. Even though G2 is still pressed no "2" is registered. (11111111122 it stops when I depress G1 but with G2 still pressed).

 

It work as if the action "keydepress" is generic (the same for all G keys) and stop whatever macros are running (even if it is not attached to the key being depressed).

 

Note: using autohotkey to do something similar on another keyboard (or directly on the K95 on the numeric pads) works as I expect (one key depress do not stop the macro of the remaining pressed key).

 

 

Questions:

 

Is this the expected behaviour or is it an "undocumented feature"?

 

Any suggestion of what I would be doing wrong? Or any work around?

 

 

TY in advance

[Toasted]

Unfortunately, the G-keys cannot be used simultaneously. The only way would be to depress one G key then press the other.

[ChrisR]

Thanks for the reply!

 

Too bad this can't work as I expected it. For the uneducated person, it would seem to be possible though since mechanically evey key are separate.

[Comet 1626864951]

Unfortunately, the G-keys cannot be used simultaneously. The only way would be to depress one G key then press the other.

 

http://www.corsair.com/en-us/blog/2013/september/common-corsair-keyboard-questions

Q: What is N-key rollover?

 

A: These terms are often used to describe keyboard features and both refer to how many keys can be simultaneously pressed to register input. Some keyboards may only have 6-Key Rollover which means that the keyboard may only be able to display 6 simultaneous keys at once. Corsair mechanical keybaords use N-key rollover which means that you can use any number of simultaneous keypresses and all will register properly at once. Here is a link to a good test to see what your keyboard is capable of, and to test your Corsair keyboard as well: http://www.microsoft.com/appliedsciences/content/projects/KeyboardGhostingDemo.aspx.

 

Corsair touts their n-key rollover, and I think there is a another cause for the observed behavior. Let's try an experiment, without using CUE or any assigned actions or lighting. 1) Open NotePad. 2) Mash down the "A" and "B" keys simultaneously, and observe the result.

 

In my experiments, I observe the following types of results:

1. AAAABBBBBBBBBBBBBBBB
   
2. BBBBAAAAAAAAAAAAAAAA
   
3. ABABABABABABABABABAB
   

 

Given that the keystrokes may be very so slightly desynchronized, that the scan line pulse check may occur just before/after a switch is closed, that there is special handling for key debouncing, and the typematic autorepeat is done by the OS, then you can tell from the third type of result that the n-key rollover certainly works for the A and B key. However, as most test results in a string first of one character and then the other, we must conclude that this is the standard way that the operating system handles the situation when both keys are pressed down simultaneously.

 

This explains why you observe what you do when you define two G keys to play the role of the A key and the B key. You are doing everything correctly; you just didn't correctly anticipate how the system would react.

Note that it is up to the application program to define what to do when multiple keys are pressed at once, so using special programs that indicate the keyboard state should tell you that both G keys are pressed.