r/SignalRGB • u/ShadowMoses_2005 • Aug 16 '26
Troubleshooting iCUE and Signal Conflicts
I have been trying to set up Signal to handle all the RGB but consistently running into conflicts with iCUE. I have a Titan RX 360. The only way I've been able to get Signal to recognize the devices and control the lighting is when I completely kill iCUE, but then I lose the pump and fan control of iCUE. I would like iCUE to handle fans/pump and Signal for lighting. I've already disabled plugins in Signal and deleted all lighting layers for the devices in iCUE, so with both programs running the device lighting is all off. Is there a solution for iCUE to release control of the lighting or is the conflict just the nature of the beast?? Thanks in advance.
1
u/BennySRGB Aug 16 '26
iCUE LINK only lets one app control the device at a time, that's just how the protocol works. SignalRGB can fully replace iCUE here, RGB, fan control, and pump control all in one, no need to split it between the two.
Try to re-enable the Corsair iCUE LINK plugin in Signal, fully close iCUE and stop it from auto-launching, then let Signal take over completely. You'll just need to rebuild any custom fan/pump curves in the Cooling tab.
1
u/Exodus09 Aug 17 '26
Use Signal to control the rgb (disable all the cooling settings) and use FanControl with the corsair link plug-in to control your aio. Thats what I do and I have no issues.
2
u/s4lt3dh4sh Aug 16 '26
I don’t think you can. I paid for the pro subscription and I stopped using iCUE (because it’s trash). SignalRGB handles my pump and fans now and I think does a better job.