GunnerCO

Just to close this thread, the keyboard faulted in another way (lost all red backlighting) and has been returned for a replacement on both counts. If the replacement has any different G-key behavior under hardware mode I will comment further here.

I've experienced exactly the same thing. My keyboard (mostly red lighting) suddenly went dark Two hours of tinkering later, after clearing all stored profiles, force-reloading firmware, soft (Esc) reset... the red LEDs in the main keyboard area simply will not light. The top bar LEDs will light red, but not those in any of the key areas. Since no further fixes are noted here, returning to Amazon for replacement. (This is the same new keyboard that will not give hardware-mode G key action, another issue for which much effort and all remedies failed.)

(Ah, no edit option.) No. I did all the original setup with a direct connection, then moved the connections to the KVM. With a bit of tinkering (sensitive to plug-in order etc.) all keyboard and iCue functions are working perfectly... except hardware key assignments, which have not worked under any hardware setup or connections.

No.

I don't think I can get any more complete or specific. I am assigning some short text strings to each key that are useful to me across all my apps, even when not running iCue. I am assigning the strings using Hardware Key Assignments, then 'overwriting' the profile to the keyboard memory. Absolutely everything seems to be working (I can even extract the settings to a new or blank profile), but the keys simply do not work — with these simple strings or any other hardware key assignment — when the keyboard is in hardware mode (with hardware lighting). I can't see anything I'm not doing right, or any sign that the programming is not being properly downloaded/retained.

Okay, how about this: G-keys broke in hardware. Help fix. 🙂

Searched, didn't see anything that addressed this issue. Opening editorial comment: The user stuff really, really needs to make a clearer distinction between hardware and software assignments. Even after you learn, one way or the other, hardly anything actually confirms the difference. I see a lot of first-timer confusion about it, too. But enough of that. Win11, K95 XT, Stream Deck MkII. All software and firmware current. Replacing a long time Logi installation; scrubbed the keyboard software, reinstalled Setpoint for trackball control. Software key setup done via Stream Deck (for now... we all know such things are never really finished). Software lighting, ditto. And even hardware lighting, ditto. But I've been trying across two days for the keyboard to hold hardware G-key assignments. Have tried everything obvious, thought of and found in various online help discussions. Bupkis. Absolutely no hardware G-key programming sticks when iCue is shut down. Have rebooted system, deleted profiles from memory, cleared memory and done the plug-in hard reset. Have turned off Stream Deck. Have tried programming all six keys with several different control options (although all I want is six simple text strings). Yes, 'overwrite' profile after every change. And... nothing. Hardware G-key assignments do nothing. This is frustrating because I KVM between my main console and an employer laptop setup, and I neither want the hassle of installing iCue on the latter nor want to do without six very useful macro keystrings. (And yes, the KVM works fine, although it turned out to want a very tricky order of plugging and powering up. I also did all of the above programming attempts with the K95 plugged in directly.) So what is wrong/am I doing wrong/am I missing, here? And secondary question, which I suppose is probably already addressed somewhere... why ITF does Corsair use two USB plugs? I know a fair amount about USB tech (have written system design docs to the chipset level)... and I can't think of a reason to separate the connections. Thx on all...