shocksim

@Steevie This is what you need to do to restore control to the lighting unfortunately. This is a known issue with our newest firmware update but should be a one-time thing. Sorry about the inconvenience, but the update significantly changes the way the software addresses each device and it creates this quirk when upgrading in rare instances. I posted more about this on Reddit here: https://old.reddit.com/r/Corsair/comments/1caiub4/2_qx_fans_not_getting_detected_in_new_icue_link/l0sd1sv/ You can also read about the Known Issues here: https://www.corsair.com/us/en/explorer/diy-builder/blogs/addressing-over-current-protection-issues-expanding-the-icue-link-system-hub-to-24-devices/

Did you delete your settings when you reinstalled? It doesn't fix the issue if you keep your settings between the reinstallation. I would suggest following SW20's instructions on how to backup your settings, make sure your profiles are backed up, and do the installation deleting the settings and/or using RevoUninstaller (free) to clear out any old stuff. If you still have issues, I'd suggest opening up a support ticket so our team can help troubleshoot one on one and provide any older firmwares as necessary.

You can contact the support team and they'll provide the v1.8 firmware. As a heads up, if you add any new hardware to your LINK system in the future, we add support for those new/unreleased devices via firmware ID, so you'll need to be running the newest firmware version. Believe you have to delete your settings for the reinstallation to fix the issue. If you change your mind, SW20 also provided instructions on how to back up your settings to minimize how annoying this is here: We get it that having to reinstall iCUE is unideal and was not a decision that the team made lightly, hence running a beta and delaying the deployment of this 6 weeks, but this is something we have to do to improve the foundation (device architecture) that we're building on for LINK and really deliver as flexible of a build process as we can.

Oh were you using a shared PCIE power connector? These are designed to run on their own PCIE power and not to be shared.

Interesting. I've raised this to the Firmware team. We haven't seen any OCP flashing issues in any of our testing recently. Is it possible for you to open a ticket, submit your iCUE logs, and PM me the ticket number? That way I can get those logs to my firmware/software team to see what is going on?

I would try a complete uninstallation of iCUE with Revo Uninstaller and then re-install v5.12. Make sure you back your profiles up somewhere and when you're uninstalling check the box that says delete all user data. Make sure you delete all of the registry and other leftover bits that Revo points out. If this still doesn't work, you can roll back using the Force Update under the System Hub firmware update to roll back to v1.8.

Download only right now. If we don't see any bigger issues with the firmware in the field or in our extended regression testing, we'll eventually push this via the update server (in iCUE).

I would try clicking the Device Enumeration under the device settings. If that still doesn't work, then I would do a clean iCUE install. Be sure to back up your profiles beforehand.

Then your pump is at the correct brightness. The black AIOs have a tinted cap, like a taillight. So these will always be a little dimmer than the parts that don't have tinted diffusers.

The team posted the KB article on the help desk with a link to the firmware, as well as the explanation on how to update it. Would suggest people go there to download. https://help.corsair.com/hc/en-us/articles/25118278321549-iCUE-LINK-System-Hub-Beta-Firmware-v2-3-427

We're a west coast company, so bear with us while we eat lunch. I reviewed the post and firmware file with the team earlier. This is still going to go live today...

Yea, seeing this issue with the firmware package as well. Apparently I can't edit and remove my link, so I'll just delete it. We'll get this posted tomorrow 100% with a working firmware package.

It should've been posted by the end of the week. The larger team signed off on a Beta FW to be posted here but I'm unsure why it's not up. I'll look into this when I'm back in the office tomorrow...

All firmware before the firmware that we will release has this issue, so it doesn't matter whether it's 1.6 or 1.8. I also posted on Monday that we'll have something this week. That's the best ETA I can provide and we're still working towards that.

We've got a candidate firmware that's working its way through testing right now. Once we're confident that it doesn't introduce any other issues, we'll either release it as a Beta FW or push via the FW update server. Goal is to have something available this week if possible.

Hey everyone, I wanted to briefly comment before the weekend and just let everyone know that this is something we're aware of and chasing. Looks like the team has figured out the issue is related to the current (old) firmware not playing nice with our new device logic. We'll be prepping a new firmware that addresses this and communicate more information next week (I hope) with info related to when the new firmware will release. In the short term, you can either dismiss the brightness warning and deal with the lower brightness until we have the new firmware out or step back to 5.11 since it shouldn't run into this device count logic issue. The warning has no bearing in terms of cooling or performance, but it will dynamically step the brightness down if you have more than 7 devices total, not 7 per channel like it should be doing. I'd just like to say I'm sorry this happened and that it's annoying. Give us a little bit of time and we'll fix this as soon as possible. In the end, this FW update should be a big upgrade for the everyone, expanding the total number of devices per controller from 14 to 24, and allow people to chain a lot more stuff on one channel, making building with LINK even easier. Especially for people running a 360mm LINK cooler with an LCD that are struggling to stay under 7 devices per channel with that product counting as 5 devices (including the fans).

https://help.corsair.com/hc/en-us/articles/19029648696589 For anyone else reading this, if you don't have a ticket open and are experiencing this issue, please click through to the help link above and it will give you instruction as well as the firmware file to flash. Once we've rolled out the RC firmware later in September, we'll deprecate this page.

Beta FW got the greenlight end of the day today, so our support team should be replying to tickets with it. I'm sure there will be a post put up soon with a download link somewhere as well.

Use Lighting Link. It's can do pretty much the same as Scenes. Or change the device lighting on each device to exactly what you want. Can also import a fancier profile from the iCUE Library for something cooler than anything Scenes did.

Go into the device you want to control (e.g. your cooler) and under Lighting Effects, you can select Rain or Lighting Link Rain if you want it to propagate across devices. There's no lost functionality going from Scenes to Murals, just as c-attack has said.

Scenes is unequivocally worse than Murals and can't do anything that Lighting Link doesn't. ASUS motherboard/GPU support will probably come soon. (Not on the iCUE team so I can't promise) But just set them to a static color if you're animating with Murals? Or just use Lighting Link or a profile to light those parts.

FYI - we've been working on that for a while. Just went live with 4.30.xxx. Can look at the bottom of your LCD Screens to find Gallery Mode. Can set which screens/sensors you want to see and what the delay in rotation is. Re: more screens with dual sensors, this is on our radar.

RGB ELITE does not, ELITE CAPELLIX does. For ELITE CAPELLIX, you have to use the Commander CORE since all of the brains is built into that device instead of the cooler. You have to connect the pump tacho 3-pin to your CPU Fan header to prevent POST/CPU Fan errors. Single wire comes off the pump for ELITE CAPELLIX, for RGB ELITE it comes off the USB-C wire harness.

Probably. This is a Beta feature... Beta means stuff will get worked out and added.

What does the liquid temp say in iCUE? Might need to use iCUE 3.x if it's not working with iCUE 4.x, but I thought we had added support for legacy coolers.