Comet 1626864951

Without iCUE installed, your profile functionality is greatly reduced, but your stored profiles will still work.

The Corsair keyboards are programmable, so you can unplug the keyboard from your home computer and plug it in at a gaming competition machine. In order for this to work, the USB keyboards must follow the USB specification, specifically, Chapter 10 on Keyboard (page 253). There are 231 defined keys, and a total of 65535, if you include the reserved ones. iCUE lets you rebind different physical keys to act like different defined keyboard keys. Note that Unicode comprises 1.1 million code points -- there simply is no way to even specify that a keyboard key should be like a key labelled with an arbitrary glyph in Unicode. There are, however, workarounds. You can use iCUE to define each key in a profile to send a particular string, and that string can be copy/pasted from Character Map or BabelMap or any other source, and pasted into the TEXT definition for the key, which you would use in iCue in lieu of macro recording.

I'd like to be able to DISABLE a button, so iCUE doesn't have it doing anything, but have the input still register. If a button is disabled, it shouldn't register input on the computer. If you want a button to register input on the computer, use iCUE to indicate what input to register.

You do not need to open and set CUE; it should remember your last profile settings. CUE does support accented characters.

:faceslap: Hold onto your sanity! It's not that it "can't be implemented"--it will come... eventually.

See Tutorial: Switching Modes by Modifier Keys and Modifier Key Combos. For CUE 2, use profiles instead of modes. You can define a profile switch on the first key, and in the switched-to profile define lighting to light your other keys. I have demoed this technique in other posts, where pressing the WinLock key toggles a red color on my Windows keys while they are disabled.

Take a look at Tutorial: Switching Modes by Modifier Keys and Modifier Key Combos. (For CUE 2, one would use profiles instead of modes.) The idea is that while pressing your CTRL key, you switch to a profile that illuminates the keys for which CTRL is part of a valid combo (e.g. a, x), and you can also assign actions to the second key from within the CTRL profile -- just remember to retain original output of the keys, if you still wish the CTRL sequence to act as originally intended.

The feature you request has existed within CUE even in version 1, using modes. In CUE 2, one would use profiles. See: Tutorial: Switching Modes by Modifier Keys and Modifier Key Combos

Until such time as Linux is officially supported, you should see the (Unofficial) Linux Driver.

:thinking: My favorite game that I play using my Corsair keyboard and mouse is certainly Correspondence chess. :hihi: Feel free to sign up for a free account and challenge me to a game. :wall: I also play backgammon, but that is not on the computer, but with my local backgammon league.

To see if software reprogramming via CUE can be effective for setting a desired color, I recommend trying to set the LED to a few settings, and observing the result: 100% RED, 100% GREEN, 100% BLUE. If any of these colors is not showing anything, then you may need to RMA. If all the colors are simply switched around, then you can use CUE to figure out how to program to rogue light. Also, once you have achieved the desired HUE, if your intensity is too low, then you need to RMA, otherwise, you can most likely reduce the settings using CUE to make the LED match the others.

The ability to set the advanced option for a macro to execute uninterrupted is present in CUE 2.15.83.

If you are not using every key that FFXIV allows you to use, then just define these extra mouse buttons to act like any of those keys.

You can use the CUE SDK, and define the lighting based on the window title of the active window, for example.

You are describing the behavior when the keyswitch may have gotten dirt, dust, or grit in it; the "switch hitter" helps determine if physical contact is being made--people usually use compressed air to blow out any grime to help the keyboard switches make more consistent contact.

The MegaRainbow thread has my favorite example of this genre. You should not have troubles getting the profiles working fine on K70, as CUE 2 has cross-platform support. Not only are there model-specific profiles, it is usually simple to edit any profile as needed.

Most basic things are doable in basic mode. Advanced model allows for advanced manual control, where one could assign solid lighting with timing on specific keys to perform animations--I hope you try RGB Share in advanced mode to see exactly what CUE 2 is capable of, and examine the profiles and read the forums to learn more on how this is done. Note that Advanced and Basic mode are distinct; CUE is in one or the other, not both, which is why changing the slider shows only the settings relevant to the current mode. Opacity is useful when overlapping multiple simultaneous colors on a single key. Set a red wave going from left to right and a green wave going from right to left. At 100% opacity, the first wave on the list will completely go over the second wave. At 50% opacity, you will see red+green=yellow where the waves overlap. This is understandable with a background in additive color theory.

It depends on your device. For example, Scimitar Pro RGB allows one to save a rainbow lighting effect to the onboard memory.

If my Actions/Macros could be grouped somehow For now, I simply use a prefix in the naming of my Actions/Macros, such as: BIZ001-description of first BIZ macro BIZ002-description of second BIZ macro BIZ003-description of third BIZ macro GRP001-description of first GRP macro If you adopt this standard nomenclature, you may find it reduces the tedium. We shall await a future CUE version that caters to those few that have so many actions/macros that having grouping inline is more important for Corsair's developers than fixing other bugs/implementing other features.

Try using the profile I supplied in this thread.

Are you using REMAP KEY? See if you can reproduce the success I mentioned earlier; I have attached a CUE profile for you to import that implements the mapping. Let me know if it works for you using my provided information, and then together we can figure out why your own attempts are not working. mouse.cueprofile

If you toggle a macro on, then other keys will not stop the macro from running. Also note that best practice for keystrokes is to enter them as a single macro action, instead of separate keypress and keyrelease events.

The keyboard works the same as what you expect, so touch-typing for productivity should not have any negative effect. The vertical switch of the key labels is to help with the lighting up of the keys, as the upper part is more strongly lit, so that people who do not touch-type can see the emphasized symbol is what will be entered when unshifted. The K95 platinum keyboard has the ANSI layout. Now the ANSI standard labels the bottom row of keys as follows: [Control][super][Alt][space][Alt][super][Meta][Control] Corsair chose not to follow the example of ANSI in labelling the keys, so the bottom row is more friendly to Windows users: [Ctrl][windows logo][Alt][space][Alt][windows logo][menu icon][Ctrl] I understand that you may find the inverted labelling of the numeric keycaps confusing. There are third-parties selling replacement keycaps, but forum rules are that these forums are for discussing Corsair hardware/software and prohibit discussion of competitor's products.

A web search shows that if you don't want to get your replacement keycaps from Corsair that there are other suppliers. I may not say if they are of higher (or lower) quality, so you will need to judge this for yourself. [url="http://forum.corsair.com/forums/showthread.php?t=77167"]Forum Rule[/url] #9 [b]NO DISCUSSION OF COMPETITORS.[/b] [i]This forum is here for the express purpose of supporting current and future users of Corsair products. Please do not discuss competing products or their suppliers by name on this forum, either in a positive light or a negative one. Such posts or threads will be edited or deleted at our discretion. Please contact the makers of that product for help. As stated above, their names are filtered out from public view.[/i]

I think establishing support for the workaround is sufficient for all advanced usage; you could create a support article documenting the workaround and give the necessary warnings about why it is not advised to completely lose the left click functionality and should ensure that the user binds this to some other area. I believe that it is very important to support the left mouse button's rebinding, not least of which is that it is a major use case to swap the left and right mouse button functionality!