Corsair iCUE - Not all LED's lighting up as before

[Theos25]

Updated my iCUE software to 4.10.273 and at first the Dark Core mouse RGB stopped lighting up when synced with wallpaper engine. Then I started noticing more and more fan LED's not turning on LL120/140. RGB Strips and even 1 out of 4 DIMM's no longer lights up. Quite odd. Everything was working fine before. Anyone have any ideas? Also it may be important to mention that before I noticed this there was an update in Armoury Crate for the mobo, GPU and Adressable RGB header version 2.0.2.6

[Mael]

Same issue, but with an MSI MB. 1/2 memory sticks is off and fans controlled by a Lighting Node Core and mouse are off as well. Capellix cooler, keyboard, mouse pad, and Commander Pro seem to be working. I'm new to Wallpaper Engine so I'm not sure if this is a new problem or not.

[Biohazard]

If the update of iCUE caused this problem then it's very unlikely there is anything we could do to help, I would suggest contacting Corsair directly. They might not be aware of the issue yet.

There is no newer version of the iCUE SDK than the one we are already using and Wallpaper Engine merely sends rudimentary colors to iCUE - it doesn't know about how many RAM sticks are installed or how many LEDs are on your fans.

[Biohazard]

I just noticed that this v4 is a complete revamp and my iCUE is not auto updating to it.

That makes it likely that it still has bugs. This would probably be a good place to post your issues with v4: https://forum.corsair.com/v3/showthread.php?t=204855

[ManTool]

I have the same problem. Prior to iCUE update 4.10.273 all "Corsair compatible" wallpapers worked great with Wallpaper Engine. Now after this update, half my Corsair lights are dead . . . as in dark (when I load Wallpaper Engine). Please fix.

[Biohazard]

Originally posted by ManTool:

Please fix.

Please post on Corsairs v4 feedback thread that I just linked. https://forum.corsair.com/v3/showthread.php?t=204855

This is not an issue in Wallpaper Engine meaning Corsair needs to fix their new v4 of iCUE to make everything work again as it used to. There is nothing new they are providing developers with for v4 or anything, it's simply a bug in v4.

[Mael]

Originally posted by Biohazard:

Originally posted by ManTool:

Please fix.

Please post on Corsairs v4 feedback thread that I just linked. https://forum.corsair.com/v3/showthread.php?t=204855

This is not an issue in Wallpaper Engine meaning Corsair needs to fix their new v4 of iCUE to make everything work again as it used to. There is nothing new they are providing developers with for v4 or anything, it's simply a bug in v4.

I've started a new thread on the Corsair forum to address this so it doesn't get lost in the ICUE4 Megathread. They are referring me back to you. I downgraded to ICUE3 and things worked almost perfectly with the exception of the RAM which is lit but at default colors. I agree that it seems to be an issue with ICUE4. We'll see if I can convince Corsair.

https://forum.corsair.com/forums/showthread.php?p=1090814#post1090814

[Biohazard]

Thanks. Like you quoted me in your reply, I still don't see any new SDK on their website, the latest version still seems to be 3.0.361 which Wallpaper Engine is using already. Meaning there is just nothing we could update it with.

But I think they just didn't know that you didn't have problems with version 3 before, yeah, which you mentioned in your reply now.

[Mael]

I was able to get it to mostly work by doing a complete uninstall including folders and registry entries, re-installing ICUE4. Everything works except the lights on my mouse.

[Mael]

Stopped working again after I added some new ICUE devices. I was able to go into "Apps and Features" on Windows 10, select ICUE, modify, and Repair Installation. This got everything up and running again without a full removal and install.

Corsair is no help. They don't seem to even read the posts. They just come back with some sort of knee-jerk reaction that is unhelpful at best, and ignorant at worst.

[Theos25]

Originally posted by Mael:

Stopped working again after I added some new ICUE devices. I was able to go into "Apps and Features" on Windows 10, select ICUE, modify, and Repair Installation. This got everything up and running again without a full removal and install.

Corsair is no help. They don't seem to even read the posts. They just come back with some sort of knee-jerk reaction that is unhelpful at best, and ignorant at worst.

I've reported multiple issues to them. All involving 3rd party plugins, SDK's etc... as that portion is REALLY broken right now. They blame ASUS and everyone else even though developers such as here for wallpaper engine confirm that nothing changed from their side and that they were not supplied with any new SDK to reference.

[Mael]

Originally posted by Theos25:

Originally posted by Mael:

Stopped working again after I added some new ICUE devices. I was able to go into "Apps and Features" on Windows 10, select ICUE, modify, and Repair Installation. This got everything up and running again without a full removal and install.

Corsair is no help. They don't seem to even read the posts. They just come back with some sort of knee-jerk reaction that is unhelpful at best, and ignorant at worst.

I've reported multiple issues to them. All involving 3rd party plugins, SDK's etc... as that portion is REALLY broken right now. They blame ASUS and everyone else even though developers such as here for wallpaper engine confirm that nothing changed from their side and that they were not supplied with any new SDK to reference.

I vaguely remember from my last foray into Corsair hardware several years ago that software was always a problem. Sounds like nothing has changed.

I'm glad I finally got WPE working, especially since Corsair's own downloadable profiles are broken.

[Tim]

If you experience this issue and you close Wallpaper Engine from the tray menu and restart it without touching iCUE, does that help at all?

I think even before version 4 there have always been issues that Wallpaper Engine can start faster than iCUE and there is no clear method of dealing with that situation which is why we added numerous workarounds for that. Maybe this issue is just amplified in iCUE version 4.

But if you close Wallpaper Engine from the tray menu and restart it (long after iCUE has started) that should ensure iCUE is sending all required information to Wallpaper Engine.

[Theos25]

Originally posted by Tim:

If you experience this issue and you close Wallpaper Engine from the tray menu and restart it without touching iCUE, does that help at all?

I think even before version 4 there have always been issues that Wallpaper Engine can start faster than iCUE and there is no clear method of dealing with that situation which is why we added numerous workarounds for that. Maybe this issue is just amplified in iCUE version 4.

But if you close Wallpaper Engine from the tray menu and restart it (long after iCUE has started) that should ensure iCUE is sending all required information to Wallpaper Engine.

Nothing for me. I've gone ahead and sent diagnostic info to Corsair today with regards to this. With 4.0 only the mouse stopped lighting using WE. In 4.10 version (latest one) Half of my gear doesn't light up. I tried WE betas, uninstall re-install. I will see what Corsair comes back to me with.

[Mael]

Originally posted by Tim:

If you experience this issue and you close Wallpaper Engine from the tray menu and restart it without touching iCUE, does that help at all?

I think even before version 4 there have always been issues that Wallpaper Engine can start faster than iCUE and there is no clear method of dealing with that situation which is why we added numerous workarounds for that. Maybe this issue is just amplified in iCUE version 4.

But if you close Wallpaper Engine from the tray menu and restart it (long after iCUE has started) that should ensure iCUE is sending all required information to Wallpaper Engine.

I had it working. Worked fine for several days. This morning Nvidia drivers updated and now it's not working again.

I've tried your suggestion and it didn't help. I'm not sure why the GPU driver update would break things again, but it was working and after updating the drivers and restarting it immediately wasn't. I'm sure it had to do with the driver install. Maybe it changed something in startup? Increasing the delay hasn't helped.

[Tim]

If possible you can just downgrade to v3 right now, it does not seem to auto-update to v4 for the time being.

I am not entirely certain what could be causing these issues and since we are using the latest iCUE integration and everything has worked fine up until now, it just looks like a bug in iCUE v4 or like some sort of backwards-incompatible change that Corsair did not communicate to developers.

I have sent our contacts at Corsair an email and I am waiting to hear back from them, if anything new develops I will post an update here.