Petro

Yep. I'm 100% on the same page as you brother, and was only teasing. No more posts from me for another few years. Merry Christmas! Stay safe and virus free whether it be Covid 19 or ICUE!

lol. You resold to "friends". Keep your friends close, so you can sell them your crap that doesn't work right. Rebinds are easy and have always been easy across every major brand and minor brand? You can buy bling on that major brand that I didn't know was Swiss until a couple days ago (or that it was 5 times the size of Corsair and profitable), you just have the option of buying "not bling" and buying the function you want. For most macro questions in this forum, I could reply, as of 3 years ago, "This is how I'd do it on this brand, this is how I'd do it on this brand, and this is how I'd do it on that brand". There were 2 things I could do easily on CUE that I couldn't figure out how to do easily on other brands. Profile switching used to be universal across the brands, but I can't do it with easily with Corsair anymore with "improvements" to CUE. Last night my wife was like, "Maybe some techy kid has built some emulator software or something. They're always doing that." And I said, "No, there just doesn't seem to be an interest in macros", and then I saw Polyrythm's post and was curious. @Polyrythm, when you buy a piece of Corsair hardware, you download the necessary drivers and version of Corsair Utility Engine. If you still have those downloads, you could maybe clean your system, and load it again(?), if you were ever happy enough with Corsair that you bought more of their stuff? You would lose all your lighting and profiles. ...Then put a piece of tape over that "update" button on ICUE. My mouse is shaky and my keyboard is funny, and from what I gather from parcels in this forum that started with ICUE version 3.3. I did that with CUE 1, 3 years ago on my top of the line computer at that time, and it is still running fine. If your tech is over 3 years old, I might even suggest finding a copy of CUE 1, on the internet, for your purposes. I even went out and bought an older Scimitar mouse (non elite? 8000 or 12000 dpi? and it works) Not so great for lighting but good enough, can't make starting sounds with the action, funny timer settings, can't retain original action of The key, but better macro creation otherwise and fast profile switching.

...And if you try to google your problems you'll pull up a Youtube video of an unboxing of a K100, where the guy says, "The wheel feels a little gritty on my fingers..." and you're thinking, "What type of shill crap is this? What about the great glowing blob of sh-t that is ICUE underneath that you need to run the thing?"

Thanks. No problem. I realized my answer was manifesto-ish, which is why I highlighted the important recommendations in yellow, and commented that 1 and 2, while I believe them to be a proper recommendation or comment were somewhat facetious. (I don't think that) The raised key action requires a sacrificed key: If he added an action to his default profile, to his Escape Key for example of raising the "o" key, and retained the original action, the escape key would still work during typing, and you wouldn't notice an effect anywhere. Conversely, if he transferred his "toggle" to his default profile, that would sacrifice a key. I try to keep my default profile as clean as possible, so I would assign your panic button to an innocuous key (the print screen for example), but the key will still work on most occasions. If Rems19 decides he/she/they likes his/her/their toggle, and puts another one in, say to crouch for example, then one has to remember to shut that toggle off as well. - tinkering with the program is dangerous, even within the rules of the unofficial instruction manual. Maybe the raised key action causes lag, or will cause some weird effects with other programs. My experience with the retain original action, is that it seems to keep the original action as per instructions in the operating system (so same repeat rate, etc.) but I don't know for sure. - I am experiencing it 10 times a day currently where it would be more, but frustration causes me to leave the computer. I do have several macros assigned, and as I said my panic button is not working currently because ICUE is shutting down. (Again, when Corsair was pretending to take input on suggestions for CUE 2, I suggested a preprogrammed stop action or stop action on the interface immediately).

... and to think I have upgraded your reputation in the past or thought about it. "Rambling manifesto aside..." Sheesh. "Elaborate action": it's 1/2 of an action: Raise the "o" key. If he does forget to toggle the switch before he leaves the game the "o" key is in the pressed position. If he goes to a web page, it's typing o the whole time. While he's navigating in ICUE to the profile he wants, he's renaming it, "ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo" The last time I was in this forum circa 2 years ago before the current crash of my ICUE, I read a post from you about the Action Library, about keeping it clean, and it was causing a macro in the Library to be attached to my escape key. Have they fixed that yet? 2 years later? That's the only reason why I hit update, was because I presumed they would have fixed that. My suggestion to Rems19 was to make a "panic button". Why is it leaving the profile when he leaves the game? Because the profile is attached to the game. So depending on the number of profiles he has he could go to any profile. Copying actions creates a problem. Leaving actions in the Action library creates a problem. You solved his problem by telling him not to use the program as would come about by tinkering with the program or by using the "unofficial instruction manual", because they haven't posted an official instruction manual. Yes @Rems19, it is better to avoid using actions with ICUE, as per c-attack. Anything that can be accomplished with good old fashioned human brain is better. It is better to avoid using ICUE altogether as per my manifesto. @c-attack, I was going to DM you to get help with my current problem. I've reinstalled Corsair (deleting my appdata, program data, and registry keys). I've run the repair tool. Corsair would suggest that the problem is with my utilization of ICUE actions. I would suggest it is with the program. Any ideas?

No there is not an action event triggered by leaving the profile. Following steps and suggestions: 1. Do NOT continue to purchase Corsair products 2. Do NOT update your ICUE ever ever 3. You could make a button which raises all keys and place it in each profile: - a) Record a new macro and type every key on the keyboard or just "o" in your case if you want to be lazy. - b) Remove all the delays and delete all the key press actions. If you were just to do "o" in your case you would have a new macro "Raise key(s)" with "Release key O" as a macro step. - c) Assign it to any key that you don't regularly use in any or all of your profiles: Maybe the right window key, or print screen or an arrow button. I used to have one for all my keys, which included my modifier keys and mouse buttons. I assigned it to my Escape button. If you want the key to keep doing what it is supposed to do, consider using retain original key output under advanced settings of the macro (For example: I would not want pressing of my panic button to activate the windows key, so I would not retain original output if I assigned it to that key, but the only time I use print screen is with the control key so I might consider retaining the original key use if I assigned it to that one.) If you use macros ever in the future, and do it by recording the macro including the delays there will be many cases where you will have a key or mouse button left in the pressed position. (If there is a delay between the pressed and released action you will often interrupt the macro in the course of pressing keys or mouse clicking during the delay.) The button with the "Key raise" macro assigned can be your "panic button". You can also put a second action on the button or macro which switches your profile back to your default profile. You may think I'm being facetious with steps/suggestions 1 and 2, and I somewhat am, however, consider the following: 1. CUE 2 and ICUE has had a problem with copied macros since its inception. I reported it in CUE 2 and at the inception of ICUE. Currently, there are 2 or 3 posts that I have seen other than my own, where currently people are seeing it as deleting macros, unassigning them, and shutting down ICUE with macros left on but no further macros working (ie. ICUE shuts down, the profile lighting is on, macro sounds and the lighting profile are working, but macro actions do not work. So my "Panic button" does not work). Corsair believes these problems are with the macros: If reported through the support ticket system, Corsair gave my original report of the problem 3 years ago the following response: We cannot help you with macros. If you were to make this "panic button" and copy it through several profiles, you would experience this problem sometime in the future. If you create it for just the raise key "o" button, you should create it in each profile you intend to use it and not copy it. 2. Corsair became a public company in 2020 with currently $3B market capitalization. They post in this forum and in their public documents "continuous improvement" of ICUE, but the last 3 years of improvement have all been towards system monitoring, and they have done nothing to improve actions or action editing. I can now see on my dashboard that fan 3 is spinning at 830 rpm (It is not a fan made by Corsair. I don't care), but my profile switching has decreased to about 1 second per switch. Someone posted the symptoms of this problem with the current update V3.36.325 in June. Corsair has not acknowledged the problem or done anything to fix it. They have stated publicly that their profit margin and business plan is through the Elgato Stream Deck. I guarantee that "Improvements" to ICUE for 2021 will be for Elgato Stream Deck, and bug fixes will be to those portions of ICUE related to Elgato. They will not be for your MK55 keyboard and they will degrade performance. Hopefully the current presentation of the bug is extensive enough for even those who just play first person shooters will notice the degradation in their performance, such that Corsair will fix this.

Last night after watching Rachel Maddow, and before writing my post and going to bed, ICUE was going crazy. I was able to replicate symptoms expressed by superTRev and Zelendel. ICUE was shutting down and staying on the lighting associated with the profile. Any button or key assigned with a macro were playing the starting sound associated with the macro but not executing the macro. (I have macros associated with the left side of my keyboard and my right click mouse button in my current gaming profile, so that they will not interrupt running macros. I have a sound associated with my right click macro which would play but the macro did not execute (ie. the mouse would not right click)) When I hit the shortcut in the taskbar to reactivate ICUE, there would literally be 10 or 15 copies of some macros in the profile, and some were deleted (as per superTRev) when I moved these around, ICUE would close on me (as per Zelendel). I played 2 or 3 games, and this happened each game. This evening I reviewed this help article and ran the repair tool which requires a reboot at the end: https://help.corsair.com/hc/en-us/articles/360044638712-How-to-Fix-unresponsive-macros-and-remaps Before the reboot and repair, I had fixed the gaming profile. After the reboot, my macros were there and mapped correctly. I have played 2 successful games this evening (,and my mouse wheel works!). Though I tried reimporting some other older profiles and they were still mapped incorrectly. I don't know why they have not helped you since June and ignored your pleas for help superTRev. I don't know why my CUE needed repairing. I don't do deep dives into the program, and the only time I look at my registry or use regedit is when I'm troubleshooting ICUE. My mouse wheel failed in about June, so maybe that was the start of my disrepair as well with an update in June. Corsair reads the posts pretty quickly (they have moved two of my more critical but innocuous posts to jail within hours of posting), but as soon as they start going vitriolic, they don't seem to answer them in the public space. I completely understand your vitriol however. My reasoning for not going to the Support Ticket System are clear after two failed attempts with similar symptoms. If you've been fighting with this since June, I would recommend (if you haven't already) that you, - try running the repair tool as per the help article linked. - and contact Corsair Support Ticket System without referencing any post in here or any vitriol in here.

Pressing the Update Available dialogue icon in ICUE on Dec. 10, 2020 caused my ICUE to remap all my second actions to different ones as reported on Dec. 10 in this thread. To correct it, I spent several hours with difficulties as discussed remapping the macros to their appropriate second actions. Turning the computer off and on that night, caused all corrections to be misremembered or not saved and reverted to mis-mapped to the incorrect locations. On Dec. 11, I began remapping a second time with intent to write down or record identifiers and purpose of some actions knowing that this was happening again. My ICUE flashed white during operation on Dec.11 and the macros were mismapped again. Twice before, I have gone to the support ticket system when a Corsair Utility Engine update has caused damage to my profiles, and been advised that I would have to get to a clear system and rebuild my profiles. With limitations, the last year has seemed somewhat stable, and prior to hitting the update button I export my profiles, but I haven't been careful to copy my Appdata and program data recently. I last seem to have hit the Update button on 11-29-2020 as evidenced by my dated name of my exported profiles, (and date modified in Windows). ICUE was stable in that all my macros have seemed to work as I entered them through recent updates of ICUE. An interesting thing though is that my mouse wheel has been broken all this time, and I thought it was broken mechanically as I often use the middle click mouse button for an action. I tried to fix it through cleaning and windows etc. After installing this update, it works fine. How do you affect the mouse wheel in ICUE? It's weird to me, that an update to ICUE with everything else equal has fixed the mouse wheel which has been broken through several previous updates. To fix the macro corruption that occurred with V 3.36.125, I have tried to do what SuperTRev did in previous post using V 3.35.152, to my December 10 profile to the same result of it being from a "newer version". I performed a clean installation of V 3.35.152 using the instructions found on Corsair Help: https://help.corsair.com/hc/en-us/articles/360025166712-Perform-a-clean-reinstallation-of-the-Corsair-Utility-Engine-iCUE- I imported my exported profiles of Nov. 29, 2020 and they were remapped wrong. I copied each action from Nov. 29 into the Action Library and then into a new created profile and reassigned all the actions to keys and buttons and reassigned all the second actions to the appropriate macros. The results I'm getting now are crazy. I was able to recreate Zelendel's experience in this thread where moving actions on my list crashes ICUE. Reopening ICUE and many of the actions were renamed and remapped again. So, there you have it: prior to downloading the Corsair Update my keyboard and mouse worked, and afterwards, it has been a sh-tshow. Twice in the past after experiences similar to this one Corsair Tech support has advised me that all is lost: Sorry for the inconvenience and to reset my Corsair Utility Engine. Once in the past they advised me to do this, but the problem was in fact related to there being a macro in my Actions library that randomly assigned to the "Escape" key and would screw up my Windows Software when I pressed Escape. This action library random roulette that Xin0710 refers to is referring to that? bug of 2 years ago? Will ICUE screw up your peripheries? Apparently. What controls the Mouse wheel scroll in ICUE? Why did the update fix it? I haven't posted or or been very active in this forum for a couple years, because most of the posts seemed to revolve around fan speed and lighting, and trying to sift through it all, made me feel like SuperTRev seems to feel like in their post. Wife: "Why are you moping around watching Rachel Maddow?" Me: "I updated my Corsair. It broke again. I can't use my computer or play my game. It's so hard to fix..." Wife: "Again?!?!?!?" Me: "Yeah, I know right. Hit that damn update button and Trust Corsair."

That is cool and artistic in a computery way. Now quit procrastinating and get back to studying for your physics final! No seriously, your art is displaying in a room somewhere across the globe for the next month or so. Merry Christmas!

Hey, I don't want to hi-jack your thread, or kill it with negativity, but installing an ICUE update has crashed my ICUE again today. I see that nobody has replied to your post in a month. My advice is "Don't make the switch". Return it if you can. The amount of questions you have suggest that you could easily get up 30 to 50 actions. You will not be able to do some of the things you could do on other software ever. Bugs are pervasive and extensive, and are still introduced without warning with new updates, and they will wipe you out. Where would you start asking for support when this happens? The Actions Library has been busted for over a year I think? - busted with a previous update. Ya, if you leave actions in the library they will be randomly assigned to keys on your keyboard. I downloaded the latest update thinking Corsair would fix that. Did you know this? Is there any warning for you as a new purchaser of this equipment that this is the case? The Action Library is a big button on ICUE. What's that for? - The answer is don't use it, it's currently screwed. 9) I could answer number 9 for you with a "workaround" that I learned from this forum a couple years ago, that involved switching profiles. Switching profiles now takes a visible amount of time on my system however, where it might not on your "fresh" system, which makes this method useless. 1) I don't think so. It would be cool if I could learn an answer for this in the forum. Remember also that the Actions Library is either screwed or has been screwed in the past. If you want an action in 3 profiles, you have to copy it to the 3 profiles. If you change the action or improve it, you have to copy it back and delete the other copies and reassign them. 8) Does closing the program stop a running macro? Are you sure? How are you closing the program? Pressing the "X" button? Macros actually run pretty quickly. The actions they have executed are not stopped by closing the program. Buttons will be left in the pressed position. 6) "Hard to swap here and lose it". Ya it's lost. Corsair has not improved "Actions" or Actions editing since the introduction of ICUE. They have been focused on component lighting, cooling, and system monitoring. In the last year or so they have been introducing computer components and hardware. I imagine Corsair's ICUE programmers are in the basement, and the Actions programmers of ICUE are in the closet of the basement. You're appealing to the workers in the closet of the basement. They are not actively involved in this forum, except to police it. (You mentioned the "L--h" word. Prepare to be shot.) Indeed they have only introduced bugs. Could you imagine trying to get support on any of this when it goes to hell; it will, and unfortunately it may likely be because of nothing you did.

Updated today: All second actions to macros were mismapped after the update was installed. So if pressing Q.1 had a second action of Q.2, it was randomly remapped to W.1. This happened with EVERY ACTION. As I know each Corsair update seems to crash some part of ICUE I take precautions to "protect" my work before trying to get rid of that "Update available" dialog box on my ICUE. Having exported the profile prior to hitting the update button to a safe location. Re-importing the profile wasn't able to fix the problem. When I re-imported the safe profile the second actions were all remapped inappropriately. This latest crash reveals several difficulties with ICUE that simple user testing would have revealed since day 1 of ICUE. I have pointed out some of these before in this forum, but Corsair has not made notable changes to the "Actions" portion of ICUE. Here's a quick list of difficulties revealed by the latest bug (Second actions were remapped wrong) introduced by downloading the update of which some seem like they would be easy fixes but have been around since the introduction of ICUE: 1. The Second Action Window in the pull down of "Advanced Settings" for Macros is too small (mostly too narrow). Make it wider: seriously (Seems like an easy fix). The current pull down menu allows for 14 characters to be read of the title of the macro of the second action. The description of what the macro does is either limited to the title of the macro or a different list made by the user (A "Notes" box for the macro would be an ideal add by Corsair here). So if I have 10 macros with the title of "Shift Release ..." I am left guessing to a large extent which one I am selecting for the second action to be applied to the Macro. 2. Actions Library Fix - Second Action Application: After a previous Update issued by Corsair, the first action in the "Actions Library" would randomly be assigned to the "Escape" button, which was weird. The solution to that bug was posted on this forum, and if I remember correctly, I think acknowledged by Corsair as being aware of the problem: the solution was to delete all actions from your Actions Library. Has this been fixed? Actions lose their "Second Action" assignment when put in the library. 3. The profile actions are active in the ICUE editor when trying to edit that profile, making it difficult to edit the profile. Solution: Use the default keyboard or have a button in the ICUE interface to use the default keyboard when editing a profile. Assigning an action to a letter key is dangerous with ICUE, but I did it. If you interrupt a macro while it is executing with ICUE there is a high risk you will be left with with a key in the pressed position. For example, the Corsair tutorial for macros records pressing of the Windows key to switch applications. If you then interrupted that macro for any reason, by pressing a key on your keyboard for example, there is a danger you would have the Windows key in the pressed position. To eliminate that problem, I put some keys on my keyboard to macro actions: ie. Shift press tied to second action Shift release, so that there is no danger of pressing the shift key interrupting my macro which I've set to execute uninterrupted. With this bug introduced by the Corsair Update, and my second actions being reassigned, all of these buttons are in locked in the pressed position while I edit them, which is ,of course, very difficult. I have made a "Default" profile where there are no macros, and I've made an "Escape" button macro in the profiles that do have macros where I have the raise key action to all the keys on the keyboard. Because of the bug introduced by the latest Corsair update, I cannot edit my "Macro" profiles without first re-assigning the Second Actions which have been remapped incorrectly (to macros at the bottom of the Actions List incidentally, so I have to scroll up to the top of a long list to find the "None" for Second Action), and I cannot edit the titles of my Macros in the profile so that I can find them on the Second Action dialog box of the Macro Profile because pressing a key in that profile would put it in the "pressed" position. Actually the list of problems that could be solved or is frustrating to me as a user revealed by today's Corsair bug is extensive, and Corsair, is still probably focused on reading the temperature of some 3rd thermocouple or stream decking or something. Above are a few fixes that would help me correct a bug introduced by Corsair's latest update to the Actions portion of ICUE. If you ever do focus on the "Actions" portion of your program, I invite you to enlist me as a private "real world" user, to create a better user interface and program.

http://forum.corsair.com/forums/showthread.php?t=138328

Be able to select and copy a group of actions within a macro or assigned action, and be able to go to a different macro and the clipboard remain active so you can paste the group of actions in the other macro.

Block all Macros/Raise all Keys/Inhibit Profile Switching/Stop Recording Default Assignable Action - All Macros are Stopped (queued macros if any are removed from the queue) All Key registries are reset/set to the raised position Recording is Stopped without recording the break function Profile switching actions are inhibited, except possibly by hardcoded buttons (M1, M2, M3 on a K95 keyboard), and by clicking the profile in the Cue program. Make this STOP PROGRAM BUTTON a button that you can press in the Cue Program. (In Cue 2 for example, put a stop program button near the advanced toggle or settings toggle), since the program has to be left open to utilize it. It might restore my faith in Corsair a bit, if you acted on this in somewhat a timely manner: I could somewhat program this myself by putting a profile switch on the break key and making a macro to set all the keys to a raised position, copy my default profile to the break profile, but it would take me a while to do (20 hours), and I might screw it up, and you guys have a little more power on your end. I think you reacted to the "retain original key function" suggestion within 3 months, and haven't reacted to any of my suggestions (even though they must be somewhat good as many were programmed into your Cue 1 software). Seriously, when the Alt-tab thing happened to me with Alt-Tab locked even after a power down, I was panicking. The keyboard was inactive, and screen continually changing programs. Ctrl-Alt-Delete? Nope, the alt button macro was locked down and was the cause of the problem. I unplugged all my corsair peripherals, and the Cue program flashed a few times and then wasn't able to recognize any peripherals. Probably if I had powered down for longer it would have reset(?), but I don't know. The error I made to cause this seemed pretty innocuous.

Possibly make some default actions to recover your system. One idea I keep getting caught on and a possible idea to fix this is a, Block all Macros/Raise all Keys/Inhibit Profile Switching/Stop Recording Default Assignable Action - This would be an action that Ensures the following: All Macros are Stopped (queued macros if any are removed from the queue) All Key registries are reset/set to the raised position Recording is Stopped without recording the break function Profile switching actions are inhibited, except possibly by hardcoded buttons (M1, M2, M3 on a K95 keyboard), and by clicking the profile in the Cue program. Think about making this a default action that is in your default hardware profile, and make it assignable to a key for older hardware users. A default position for the action could be on the key combination for Ctrl-Break. Which is what us older "punch-card" programmers used to do to stop a program going haywire. If i had this feature I would assign it to that and the window lock key. Why? - Experimenting with repeatable actions - Using second actions The following examples: 1. Use a repeating action on toggle, and I may not have set the action to "Execute uninterrupted, and when interrupted a key is left in the down position. This has happened to me a lot with modifier keys in the macro, or when I have recorded the macro which records key press/key release. Many times I have no way to fix it except turning off my computer, and with Windows now remembering where you are, it's becoming more difficult. I have been locked in Alt tab, and shut my computer off and on, and had it come back on with the Alt tab still going, switching my programs repeatedly. I've had keystrokes locked down and tried to go to the Cue program to fix it, and wiped out several actions, because of the autosave feature. 2. Been using a work around suggested in this forum to create key combinations: So shift, alt, and control take me to different profiles in which the key combination actions are programmed to the combination key. But if I try to create a new action or modify an existing action within the profile with the switch, and have to type shift in the cue program it will take me to the other profile, and the program has a hard time with it. I have to disable the profile switch, make the modification, see if it works, (oops it autosaved on me....) find the profile switch in this messed up unorganized list of actions and backup actions, and reactivate it. 3. Recording Relative mouse movements within a macro, and finish. Then you have to move to the stop recording button and mouse click, which is all recorded. Then you are transported to the end of the macro. You have to scroll back find the part of the recording that you didn't want in there (the movement to the mouse recording button and final mouse click) and delete it (Which can be difficult to find in the hundreds of actions that end up being recorded by a mouse move/click recording) 4. Several other examples... If there is something like this in Windows already, or within Cue, if someone could tell me that would be great as well. (Several times I have been in a screwed situation, and I have to think really hard to get out of it.)