iCUE 3.15.101 - Feedback

[rocsen]

Good question. I just ran Prime95 and the pump does then jump to 2000rpm
In Link the pump would stay at 1000rpm when set to quiet.

Is there a way to lock it to 1000rpm in iCUE?

One more thing, in Link if I choose one of the default fan profiles (quiet, balance, performance) I can still change the temp sensor source.
In iCUE this doesn't seem to be possible.

And one suggestion. It would be very helpful to access fan/pump profiles from the dashboard. Again this is possible in Link and reduces a lot of clicking and back and forth.

For now I'm sticking with Link.

[Djiddy]

Sorry Corsair but I would like a PC silent at idle.

I paid 3500€ for a gaming PC!

[P33R]

Originally Posted by Djiddy

8% CPU charge on i9 9900k???

That doesnt sound right, i have a 9900k too and 9 devices in iCue, all with various lighting effects and the service is around 1% usage +/- 0.5

Edit: Forgot to mention i went back to 14.104...did you have this with 14.104 too or just with the newest version?

[BlaiseP]

Originally Posted by Djiddy

8% CPU charge on i9 9900k???

Originally Posted by P33R

That doesnt sound right, i have a 9900k too and 9 devices in iCue, all with various lighting effects and the service is around 1% usage +/- 0.5

Edit: Forgot to mention i went back to 14.104...did you have this with 14.104 too or just with the newest version?

I just checked mine: 9900k / EVGA Z370 Classified K / 2 x Commander Pro / 4 x RGB strips / Vengeance RGB RAM / AX1200i / K95 Platinum / M65 Pro RGB...

CPU usage 0.4~0.8% ("Enable full software control" is disabled for the RAM in ICUE v3.15.101)

[DevBiker]

Originally Posted by Djiddy

8% CPU charge on i9 9900k???

Do you have full software control enabled for the RAM? If so, uncheck it. The effects won't be as good but CPU usage should drop.

This is a known issue and one that Corsair is working on.

[zeroXII]

My LL120 fans do not light up on PC boot after a shutdown. For some reason, iCue doesn't save the lighting settings on my Lightning Node Pro even though its detected upon system bootup. Everything else seems fine though. My H100i Platinum and Vengeance RGB Pro all light up as intended. Annoying to have to keep opening up iCue and manually set the lighting up for my fans upon every PC startup.

[schangtil]

There is still errors in current measurements for the AX1600i, 3A on ports not connected to anything.

[rocsen]

I managed to resolve the USB sound which I think is actually a connect sound, by connecting the AIO directly to the motherboard USB header.

Originally Posted by tjgodin

Upon windows startup, after login, when the iCUE program is activated I hear the USB disconnect sound as the software initiates the iCUE application.

I have a Commander Pro connected to the motherboard USB header, with my H100i AIO connected via the USB port on the Commander Pro. I also have a HX750i power supply connected via USB for monitoring in iCUE.

Its unclear if it is the Commander Pro which is disconnecting or one of the other devices. The disconnect only occurs on the first launch of the iCUE software. If I close the application and restart during the same windows session, no disconnect occurs.

I'm using an ASRock Z390 Phantom Gaming ITX/ac motherboard with Window 10 Pro x64 (1903) installed.

Tony

[aska]

Hi Corsair®,

Please fix the flatlining custom fan curves asap, thanks.

[Josey Wales]

What Release Show me a download link or release notes? This is a deceptive practice calling a patch without a download a release??

[Promethus]

"Play on Key Pressed" stopped working for me with this update. Now my entire keyboard lights up instead of the specific key I pressed.

[Corsair James]

First, I will apologize for not releasing patch notes earlier - I was traveling out of the country on business and I am the only one who publishes the patch notes. They have been posted today.

Second, the Gradient Play on Key has been bugged and we will resolve this in v3.16. My apologies for any inconvenience related to this bug.

Third, CPU Usage in DRAM Software Mode Enabled is a known issue and related to how SMBus is configured in order for us to drive lighting in real time. This is a hardware consequence for the moment, but we are working hard to implement a brand new driver to resolve this problem. Its a monumental (and a first of its kind implementation for RGB DRAM) so it's currently in internal testing right now, but preliminary results show a drastic reduction in CPU usage. I am sharing this so there is some transparency into what we are working on to address the issues being reported here.

Third, I am disappointed by some of the snark that exists in a feedback thread. While I understand that there are some poor experiences with our iCUE users, most of these problems are not wide and rampant despite what you may see and read. We always strive to resolve any issues reported to us but the challenge in software is always being able to reproduce it on our end in order to determine the true source of the problem. There are other times that, although may be related to iCUE, it may not actually be the software causing these issues. iCUE is made up of hundreds of separate components (including CPUID SDK) and as we expand on product and software enhancements, there will always be issues that come up. I appreciate any patience and I truly understand any frustration you're all experiencing. No one, especially me first and foremost, wants a bad experience to result from our software. We do everything we can to deliver an amazing experience - it just takes time and research sometimes and why we deploy updates monthly.

[Glzmo]

Originally Posted by Djiddy

Is this normal? 8% CPU charge on i9 9900k???

No, I don't think so. On my system it consumes 0.3-0.8% of the 9900k. 0.3-0.4% when iCue is "closed" and running in tray only mode, 0.5-0.8% with iCue open or minimized to the taskbar.

[tjgodin]

Originally Posted by Corsair James

First, I will apologize for not releasing patch notes earlier - I was traveling out of the country on business and I am the only one who publishes the patch notes. They have been posted today.

Second, the Gradient Play on Key has been bugged and we will resolve this in v3.16. My apologies for any inconvenience related to this bug.

Third, CPU Usage in DRAM Software Mode Enabled is a known issue and related to how SMBus is configured in order for us to drive lighting in real time. This is a hardware consequence for the moment, but we are working hard to implement a brand new driver to resolve this problem. Its a monumental (and a first of its kind implementation for RGB DRAM) so it's currently in internal testing right now, but preliminary results show a drastic reduction in CPU usage. I am sharing this so there is some transparency into what we are working on to address the issues being reported here.

Third, I am disappointed by some of the snark that exists in a feedback thread. While I understand that there are some poor experiences with our iCUE users, most of these problems are not wide and rampant despite what you may see and read. We always strive to resolve any issues reported to us but the challenge in software is always being able to reproduce it on our end in order to determine the true source of the problem. There are other times that, although may be related to iCUE, it may not actually be the software causing these issues. iCUE is made up of hundreds of separate components (including CPUID SDK) and as we expand on product and software enhancements, there will always be issues that come up. I appreciate any patience and I truly understand any frustration you're all experiencing. No one, especially me first and foremost, wants a bad experience to result from our software. We do everything we can to deliver an amazing experience - it just takes time and research sometimes and why we deploy updates monthly.

Thanks for posting your note and the updates. I continue to find the updates helpful and I would echo that its unfortunate that a few forum users simply "step up on their soap boxes" and are providing little value to the broader forum community. I would note their concerns have been heard loud a clear and simply leave it at that.

For the rest, I'd say I've found Corsair's employees are actually utilizing the forum for feedback and many actually are reaching out to help troubleshoot and improve the functionality of their products. I've found them to be respectful and actually engaged with the forum users. I spend time on a number of other big tech company forums and posts go unanswered, with no resolve. So, I'd acknowledge there is a lot of value to the forum from both the positively engaged users that actually are helpful to others and on Corsair's part.

Tony

[tjgodin]

Originally Posted by Glzmo

No, I don't think so. On my system it consumes 0.3-0.8% of the 9900k. 0.3-0.4% when iCue is "closed" and running in tray only mode, 0.5-0.8% with iCue open or minimized to the taskbar.

Less than 1% on my 8700K with either software control enabled or disabled for my Vengeance RGB Pro memory. iCUE sits at 2%-2.5% if I leave iCUE Spaces up and running on the desktop.

Tony