logue1993

Thanks for the update! I hope it's actually fixed in 5.8 then, that update can't some soon enough 😅

Also, I'm using new version 5.7.106 (probably just released). And it also didn't fix it!

Same here, I have a Sapphire Pulse 5700XT and no GPU Temperature controls anymore. This is really annoying because it basically nulls the whole point of using iCue and their ecosystem to effectively cool my PC. PLEASE FIX THIS SOON, it can't be THAT hard, since even the Windows 10 Task Scheduler can properly see my GPU temps.

Is there a way to backup the Murals section? Cuz I may want to revert back to 4.32 while they don't fix this, but I'm not sure iCue allows to install an older version over a newer one, so I might have to uninstall current iCue (4.33) before installing the older one and then I'm worried I'll lose my murals layout, which took a while to get just right, so... Any way to back it up?

this... happened here too. The Stream Deck iCUE plugin doesn't work anymore, saying it needs to be updated. Also, I remember having this problem in the past as well, solution was as mentioned: Corsair provided an updated version of the plugin and it worked.

Came here precisely to check this... So, great, Corsair products not working with themselves. It's been two versions. You've bricked it. Unbrick it. Pretty, please?

I just use the "Fn" key as a profile switcher. There, I have one which is basically lights out for everything. It turns every single light off. My computer then is only lit by the logo from my graphics card (a red Sapphire logo) and the Q-Code LED and the drive activity LED in my motherboard.

Look, I love iCue and have a bunch of iCue enabled products from Corsair. However, I can't see a reason why, in setups such as mine, iCue has to use so much system resource (CPU and I/O in particular). svchost has 16 million I/O entries (see attached image). And I bet you that this particular instance of svchost has something to do with iCue, because if uninstall it, there's no other svchost that has that many I/O operations. My setup has 2 commander pros (which have 12 LED strips in total), 3 LL fans (from the 680X case) and 4 Corsair Vengeance RGB Pro memory sticks (4*8 = 32GB DDR4) and a K68 keyboard. However, all those lights have different profiles and most of them are static solid colors effects (appart from the keyboard keys light up white when I press each one). So, being solid color effects (however mostly a mix of 2 colors and hence why I don't like to just close it and use the hardware profile - doesn't allow each channel of strips to be controlled), there's no need for processing. It should be set and forget, maybe a few checks every 10 or 20 minutes just to see if the lights are still synchronized for whatever reason. I don't know, maybe there's a way to code a "switch" for low usage and then limit the options to solid static colors only (which is basically what I use).

The problem is they've programmed the software in a poor way. For most users, who are using static lighting (static being the keyword here), there's no need for any software control over that. It's static lighting. I don't see how hard that can be with addressable RGB LEDs, unless you're programming it poorly. Also, check your Task Manager, under Details (enable the column "I/O reads"/"writes"), you'll notice iCue has millions of I/O operations EVEN WHEN YOU'RE USING STATIC LIGHTING. Maybe that's for fan curves, but even then... That's too f****** much, Corsair!!!! :mad::mad::mad: I don't know, there should be a way to reduce so many operations. This kind of software should be more "idle" focused, instead of so many live operations stealing CPU and I/O cycles from the system. It's colored LEDs, we're not crunching Pi or going to the Moon here, folks! \o

Found the link for the 'Juicy Tech' version of Asus Aura that actually works. I recommend uninstalling previous versions and any other software Asus installs (Patriot RGB controls, some others like this, etc.), running CCleaner registry scan and a restart before installing this one. It's version 1.06.17. At least, that way you can somehow control the motherboard LEDs. https://drive.google.com/file/d/1boOJ4P97ufAVA6Y1oSlIPwfPAO0O5qUs/view

Having the same issues with an ASUS Crosshair VII Hero. I think what bricked it for me was update 3.28, but I'm not sure. ASUS Aura is installed, I can open it and control the RGB through there, but the MoBo no longer shows up in ICue. Also, that last part you mentioned, I used to have that error installing any version of Aura (the Check if Aura Service is running). Then I found a version online (don't remember where but it's by someone called 'Juicy Tech') of Aura that has a working installer and installs everything properly. Admittedly, it's not the latest version (I think it's 1.06.XXX or sth), but it used to work just fine and it used to show up in ICue. Waiting for responses too.

It's a port issue. I now would like to find out if I can recover these "dead" ports, since the rest of the Commander Pro works fine. I have 2 Noctua 3000 fans that I tried using with the CoPro and I believe they were the culprit of killing them. I'm now only using 3 ports in the CoPro (4, 5, 6) for fans: 1 140mm Noctua NF-F14 exhaust back (chromax version, so not industrial), 1 120mm Noctua NF-F12 exhaus top (industrial, but 2000 rpm so it works normally, had from previous case), 1 LL120 intake in the front (the bottom one, since it's probably the one that affects the GPU the most). All of the fans in my system are 4-pin PWM. However, ports 2, 3 (and 1 at times - more frequently than I'd like) in the CoPro (for fans) are dead. I've tested multiple fans in them (along with the ones included in the case) , none of them spin, working fans in other ports are stopped in this one, so I basically have a half working component. I'd really like to know if there's a way to recover those dead ports (why are they dead anyway? shouldn't it either fry the whole thing or nothing?)?????

Hey, this is 2 years old and I have had the exact same issues. Never used splitters, only individual connections to the CoPro, but have the Noctua Industrial Fans, tho never ran them at max speed for long. I'm in my 2nd Commander Pro and 2 of it's ports are dead. Assuming the Noctua fans used caused the problem (and I've never used them again in the CoPro, after all the ports died, so I was forced to start using MB controls, which is not ideal since it doesn't read GPU temps...). Is there a way to open it up and fix it? Would it be possible? Because my CoPro still works just fine for everything else (the other 4 ports are all working, except for one that's kinda funky, and the LED channels and USB ports work too)... So, is there a way to "fix" those ports? Some soldering involved, idk...? I'm asking this 'cause I'm not buying in dollars, local currency sucks.

Hey everyone! Just got my 680X, it's a gorgeous case! However, I'm having trouble controlling the 3 included LL120 fans through my Commander Pro. First things first: I HAVE used Noctua fans with my Commander Pro for a while (the Industrial PPC 3000RPM kind), until they stopped working. I found out that these fans are not so easily controlled because of motor differences with the regular type of fans. So now I'm afraid that some of the Fan ports in my Commander are dead... I've got everything connected and working, but I can't control the 3 front fans that are included with the case. My setup is as follows: The 3 included fans (LL120) are connected to the Fan LED Hub (in positions 1, 2 and 3). The Fan LED Hub is then connected to the Lighting Node Pro, which itself is connected to the Commander Pro. My Commander Pro receives two USB connections: 1 from the Lighting Node Pro (included with the case) and 1 from my RM850i (to monitor power and voltages). Also, there are 5 fans connected to it: the 3 in the front (which are the ones I'm having trouble with), 1x140mm Noctua (NOT INDUSTRIAL PPC) at the back (exhaust) and 1x120mm Noctua at the top, at the rear, also as exhaust (this one IS a Industrial PPC 3000, but since it's a 120mm, for some reason the Commander Pro works just fine with it). Weird thing is: the LEDs are all working (fans, my TWELVE strips - YEP), even the 3 in the front. I can control them just fine, change effects, etc. However they don't spin at all. Changing "fan profiles" through ICue does nothing. And the worst part is sometimes only ONE of the 3 spins for a little, then stops right after 1 second or something. Has my commander pro been killed by those 140mm noctua fans? And that's why I can't control those 3 front fans now? Please help!

Hi! Thanks for the reply! I wasn't aware of this compatibility problem. So, the current ports that are having problems are 1 and 3 in the Commander Pro, although it doesn't seem to be a port problem, as you said. I think all the times that I had trouble with it (the Commander Pro), were with the NF-A14 Industrial PPC 3000 RPM (I've edited the original post to name and correct some fans/ fan speeds). The only different Fans I have in the system, as I've updated the original post, is a 120mm in the back (NF-F12 which is also Industrial PPC 3000RPM max) and the 140mm in the top as exhaust (NF-A15 1200RPM max - the extra fan that comes with the NH-D15).