Barnack

Windows 10. Yeah i guess i will.

It all started with the volume wheel getting stuck (not phisically) sending an infinite loop of volume input not allowing any other kind of input to reach the computer. As suggested i checked if it was an icue issue using the keyboard without icue running for a while. Today i started icue again, and the volume wheel issue occurred again (didn't happen for the whole time i used the keyboard without icue). I unplugged and re-plugged the keyboard which solved the input being stuck issue. It still works like normal keyboards, but now almost everything cue related doesn't work. Macros, remaps, rgb. I found out writing code on Visual Studio (i have my italian layout ò key remapped to altgr + à (which prints #)) but the # doesnt appear, and neither does ò, as if the original key has actually been overridden but the macro i set is being ignored. I tried updating icue, there was an update, and i installed it (3.18.77). Checked for keyboard firmware updates, and nothing was available (3.21.7168). Tried to force firmware update in case something in the keyboard was corrupted, but the process made icue crash upon reaching 2%. Is this an hardware issue with the keyboard, a software issue with keyboard's current firmware, a software issue with icue? Can i do something for it? Should i ask for a replacement?

Hi, where do i find my K95 platinum's part number for an RMA request?

I'll try running the pc without iCue on for a while, the problem is a time it happened two consecutive days, now it didn't happen for 1 month until today...

Greetings, sometimes when i use the volume wheel (happens in both directions), the computer will keep receiving the volume up/down input as an infinite cycle; animations won't work, any other form of input won't work. Restarting icue won't solve anything, the keyboard will just be stuck there until i physically detach and reattach the cable. Keyboard's firmware is already the lastest version (v 3.21.7168). Any way to solve? The keyboard was purchased last year right before Christmas.

That would still require an additional software running in the background that interfaces with icue and which for obvious reasons cannot be ported in K95's onboard profiles; Using the SDK to work on key mapping and macros doesn't make more sense than just using AutoHotKey imo. The SDK has its uses of course (integration with a specific software), but i wouldn't take it as an efficient device customization option. If it was possible to directly interact with cue-compatible hardware without using icue as a middle layer it'd be different, and one could just write a stright icue replacement that supports anything without having 2 background programs running for it. Still no onboard profile but you avoid multiple programs. Having icue support some kind of scripting and onboard profiles to a smaller extent on the other hand would be the best solution. Supporting a script is so easy that corsair can hire me to come up with a script grammar, c++ parser, ast and interpreter for icue (although but i lack experience with the hardware for onboard support :D:), and i'm not even a professional developer (yet)

It would be nice to allow for a lightweight autohotkey-like scripts interpreter on both iCUE and onboard profiles for devices with onboard memory. There's many really trivial things which can't be done right now that would be crazy easy with a script if(some key held down) { remap(a, b) remap(windows, ctrl_left) macro q [shift down, h, shift up, e, l, l, o, space, w, o, r, l, d] } And no switching an entire profile having to reload all the mapping and lighting effects to access a layer while you hold a button is not a solution, it's a workaround. Why isn't this a thing? It would make sense to be able to do that with an "advanced" software like iCue instead of having to install yet another application that takes more resources on the background.