Wallpaper Engine doesn't use iCUE automatically

[NPC846]

Hi, as I stated in the title every time I turn on my PC I have to go to WE settings and manually disable and re enable the iCUE plugin (It's enabled by default) for it to work.. What's the solution? Thanks.

[Tim]

This basically happens when Wallpaper Engine starts faster than iCUE. You can try switching from the "high-priority" autostart in the settings back to the normal autostart, that fixes it for some users. We may also incorporate a more sensible fix in an upcoming update about this so that this workaround will not be necessary anymore.

[NPC846]

Originally posted by Tim:

This basically happens when Wallpaper Engine starts faster than iCUE. You can try switching from the "high-priority" autostart in the settings back to the normal autostart, that fixes it for some users. We may also incorporate a more sensible fix in an upcoming update about this so that this workaround will not be necessary anymore.

That's what I suspected. It's already on normal autostart, hopefully it'll get fixed in the next update.
Thanks.

[Tim]

Until then, a quick fix that usually works is to set a hotkey for "Stop (free memory)" in the General settings of Wallpaper Engine and hitting it twice after your PC starts and iCUE is ready. That's a bit faster than going all the way to the settings.

[Biohazard]

Could you try this on the beta and see if it works better?

https://steamcommunity.com/app/431960/discussions/1/1746720717352689476/

We have been waiting for Corsair to implement a real fix but since that never happened, the beta version will now attempt connecting to iCUE again 60 seconds after logging in. That should solve the issue unless iCUE takes even longer to start.

[NPC846]

Originally posted by Biohazard:

Could you try this on the beta and see if it works better?

https://steamcommunity.com/app/431960/discussions/1/1746720717352689476/

We have been waiting for Corsair to implement a real fix but since that never happened, the beta version will now attempt connecting to iCUE again 60 seconds after logging in. That should solve the issue unless iCUE takes even longer to start.

The beta has solved the issue but I will roll back to the stable version. Btw I'm using an intel 660p and iCUE takes less than 60 seconds to start I believe you could reduce the attempt to reconnect to iCUE to 30/40 seconds maybe even less.

[Biohazard]

Thanks for checking! On my PC it already takes 40 seconds and it's not the worst system, iCUE just starts quite slowly. If there are too many people where 60 seconds isn't enough, I might turn this into an option somehow, but for now I'll leave it locked at 60.

In comparison, other SDKs don't have this problem and work immediately when WE launches. Though of course they have some other things where compromises have to be made.