Sojourner1

Has anyone noticed unusual electromagnetic emissions from their corsair peripherals that stops when iCUE.exe is terminated?

Problem has resolved itself after the keyboard was replaced. Odd that the problem started with a software update, and resolved with a hardware replacement.

Finally had to replace my K55. Went and bought another K55. Remembering what I went though last time I had to replace a keyboard--reconstructing all of the profiles and macros for the new board--I went through and backed up every single macro into the software library, took screenshots of each profile for reference, yadda-yadda-yadda. So the new keyboard was sitting on the shelf, because I was just dreading all the work I'd need to do for the dozens, upon dozens, upon dozens of macros I have... Finally, just now, I unplugged the old one and swapped it out. Opened up iCUE to unleash the tedium... Wait... WHAT'S THIS?! iCUE AUTO-MIGRATED MY MACROS? EVERY. SINGLE. ONE. AMAZING. Thank you. Also, I didn't realize that there are, like 3 different versions of the K55, so I do actually need to remake all of the lighting. Old board was Pro XT, new one is just plain Pro. Oh well, the price was right,

Another thing to check is the mouse sensitivity settings (pointer speed). It is different from DPI and based in the Windows OS, though iCUE does allow you to change this setting from inside the program, under Device Settings > Pointer Speed. I was having weird cursor speed issues for months. Any time iCUE closed or crashed I noticed the speed would change, and then revert on restart of iCUE. Turns out iCUE stores separate settings for both software profiles and hardware profiles.

An electrical short could be the cause of your issue. I would try the keyboard on an entirely different system to check for that. Or open it up to look for any signs of physical damage to the circuitry.

That is strange. I recreated the profiles from scratch, and recreated that actions from scratch too, and both cases caused the lagginess. Edit: I should mention that I just got a Windows Update (KB5026372) and the profile switching is much less laggy after the restart.

I don't see anything in there about why my macros don't work properly anymore.

I'm honestly wondering if there was a mass layoff over the last few years that resulted in an almost complete change-over of their software engineering team, and they are basically trying to rebuild iCUE piece by piece with each update. I've used Logitech, Microsoft, Razer, and Roccat macro software over my lifetime and I've never seen a product break so often.

A few days ago I upgraded from iCUE 4.33 to 5.1. Immediately I noticed that one specific "ProfileSwitchingAction" is not working properly anymore, and is extremely slow. I spent some time recreating the profiles to pinpoint the cause of the delays. The profile in question has multiple "Launch App" functions mapped to various keys on the keyboard and mouse, and these are linked to .bat files that do many different things. Switching to this profile works correctly, instantaneously. Switching from this profile, however, takes an extremely long time, sometimes up to a few seconds. In recreating the profile, the delays started as soon as I added the first "Launch App" linked to a .bat file, and with every addition of another linked .bat file, the delays increased. There are no delays with other profiles that have no "Launch App" linked to .bat files. Changing the Launch App from .bat files to directly open folders does not get rid of the lag.

So I managed to fix this problem... luckily I know how to use the comparison tool in Visual Studio Code, and luckily I have over a dozen versioned backups of my iCUE profile folder going back almost a year. If anyone else is needing to map an action to that particular key, here is what I did. I opened the ...AppData\Roaming\Corsair\CUE5\profiles folder and opened each .cueprofiledata file in Visual Studio Code, one by one, until I found the one with the name of the profile in question. The name of the profile is on line 5 of each file: 1 <?xml version="1.0" encoding="utf-8"?> 2 <cereal> 3 <profile> 4 <cereal_class_version>317</cereal_class_version> 5 <name>Civ6-1</name> 6 <id>{9e82934e-d5ea-46fa-a476-e45a84bc90e9}</id> Once I had the name of the file (you can see it on line 6 "{9e82934e-d5ea-46fa-a476-e45a84bc90e9}"), I went and found it's counterpart file in my backed-up version from iCUE 4. I had both files opened in Visual Studio Code. I right-clicked the oldest version in the explorer panel, and clicked "Select for compare". Then I right-clicked the newer iCUE 5 version and clicked "Compare with Selected". Once the comparison screen opened I did a term search for the name of the action "ToggleBanners+Icons", which took me way down into the file: 1171 <name>ToggleBanners+Icons</name> 1172 <id>{5bbb52c3-94ef-48ba-b826-9ca8dad9e195}</id> Once there, I stared at this ungodly mess for many a minute before I could make any sense of it: 1164 <value1> 1165 <first> 1166 <polymorphic_id>14</polymorphic_id> 1167 <ptr_wrapper> 1168 <id>2147483663</id> 1169 <data> 1170 <base> 1171 <name>ToggleBanners+Icons</name> 1172 <id>{5bbb52c3-94ef-48ba-b826-9ca8dad9e195}</id> 1173 <repeatOptions> 1174 <repeatCount>1</repeatCount> 1175 <repeatMode>NoRepeat</repeatMode> 1176 <delay>0</delay> 1177 <delayMode>Constant</delayMode> 1178 <randomDelayFrom>0</randomDelayFrom> 1179 <randomDelayTo>0</randomDelayTo> 1180 </repeatOptions> 1181 <executionHints> 1182 <terminateOnSecondExec>false</terminateOnSecondExec> 1183 <restartOnSecondExec>true</restartOnSecondExec> 1184 <execHint>OnPress</execHint> 1185 <retainOriginalKeyOutput>false</retainOriginalKeyOutput> 1186 </executionHints> 1187 <actionLighting>{00000000-0000-0000-0000-000000000000}</actionLighting> 1188 <actionSoundPath></actionSoundPath> 1189 <attachedActions size="dynamic"/> 1190 </base> 1191 <terminationMethod>Interrupt</terminationMethod> 1192 <highPriority>false</highPriority> 1193 <events size="dynamic"> 1194 <value0> 1195 <polymorphic_id>15</polymorphic_id> 1196 <ptr_wrapper> 1197 <id>2147483664</id> 1198 <data> 1199 <base/> 1200 <keys size="dynamic"> 1201 <value0>U</value0> 1202 </keys> 1203 _KeyStroke 1204 </data> 1205 </ptr_wrapper> 1206 </value0> 1207 <value1> 1208 <polymorphic_id>16</polymorphic_id> 1209 <ptr_wrapper> 1210 <id>2147483665</id> 1211 <data> 1212 <base/> 1213 <useRandom>false</useRandom> 1214 <delay>33</delay> 1215 </data> 1216 </ptr_wrapper> 1217 </value1> 1218 <value2> 1219 <polymorphic_id>15</polymorphic_id> 1220 <ptr_wrapper> 1221 <id>2147483666</id> 1222 <data> 1223 <base/> 1224 <keys size="dynamic"> 1225 <value0>I</value0> 1226 </keys> 1227 _KeyStroke 1228 </data> 1229 </ptr_wrapper> 1230 </value2> 1231 </events> 1232 </data> 1233 </ptr_wrapper> 1234 </first> 1235 <second> 1236 <key>MouseProfileSwitch</key> 1237 <layer>StandardLayer</layer> 1238 <event>Click</event> 1239 <distance>0</distance> 1240 </second> 1241 </value1> It's really hard to tell becuase the code isn't formatted for human readability, but this is basically one code block for a single action. All of the actions that are present in your profile will show up somewhere in this file, even the ones that aren't mapped to a key. As far as I can tell, all you need to do is add the name of the mouse button in between the <key></key> tags of that action's code block. So, for example, the only difference between the old file and the new iCUE 5 version is that the key name was missing from line 1236: So I just copied that over and saved it. Voila!

Besides profile switching being laggy and slow, there is also another problem: there is no way to apply macros/actions to the MouseProfileSwitch key on my scimitar.

I just updated to 5.1 and I have noticed that profile switching is not working as well as it used to. When the current profile is "Desktop 1", I have the profile switching button on my RGB Scimitar Pro set to switch to "Desktop 2" when clicked. Once in Desktop 2, clicking the same button will switch back to "Desktop 1". Switching to "Desktop 2" works good, very quick switching. But switching from "Desktop 2" to "Desktop 1" is very slow, and can take over a second to switch.

Thanks for fixing the second assignments!

I seemed to remember it was working for me in November when I started playing DOOM Eternal, sure enough I tracked down the iCUE version from that month and it does work: https://downloads.corsair.com/Files/CUE/iCUESetup_4.30.162_release.msi.

More and more I am having to turn to AutoHotkey to be able to do the things that I used to be able to do with iCUE. Makes me wonder...