Jump to content
Corsair Community

iCue not saving settings/No RGB on startup


KrustyKrab
 Share

Recommended Posts

I'm running a Dual Boot Hackintosh system at the moment with Windows 10 and Big Sur both installed on separate NVME Drives.

 

I bought 2x Corsair Vengeance RGB Pro but the iCue software has been causing me so much grief.

 

In my first attempt at installing iCue on Windows 10, everything worked fine to some extent. Upon rebooting my machine to either Windows or Mac, the previous RGB settings were automatically loaded. However, every time I put my computer to "Sleep", the RGB's were still running.

 

I did a firmware and software on iCue (Windows 10), and now the RGB's actually turn off when my computer goes to "Sleep".

However, whenever the computer does a fresh boot after a Shutdown, the RGB's don't even come on anymore. On Windows, I will have to actually open the iCue software, and then it will say "No Devices Detected" for half second and my Vengeance RGB Pro will pop up. After that, the RGB's will work.

If my computer is shutdown again, I will have to repeat the process.

When I boot to Mac OS, the RGB's don't even work anymore.

 

I've got 3 other RGB softwares from NZXT, Gigabyte and Sapphire. All 3 of them work seamlessly and work when I boot to Mac with previous settings set from Windows. The Corsair's iCue is the only one with the issue.

 

Any help would be much appreciated!

Link to comment
Share on other sites

  • Corsair Employees
You set the hardware profile for the RGB to be off. When the computer is running without the iCUE software, or the system is in a Sleep mode the hardware lighting profile you set will take effect and the lighting will be off. Meaning when you boot into your MacOS drive it still runs the hardware profile. Also that hardware is not supported with the MacOS version of the software due to limitations of the OS.
Link to comment
Share on other sites

You are kind of in a bind there. You are going to be in "Hardware Mode" anytime CUE is not running. That will be all the time on the Big Sur side and also boot, shutdown, and Windows when not running CUE. There is nothing wrong with that and there are a bunch of effects to choose from that will be persistent. The problem is sleep mode. All RGB RAM is going to stay on in sleep mode because the modules are still powered. No way around that. What most of us do that use sleep mode is delete the HW Lighting Effect or set a static value to 0,0,0 to make it dark during the sleep state. That is going to conflict with your other uses. You will have to choose between off during sleep and all other times without CUE running, not using sleep, or HW Lighting on during S3.

 

Hardware Mode on the RAM is a bit different than other devices. To toggle it between software/hardware mode, boot up Win 10 and open CUE -> Settings -> Vengeance Pro and check box "enable full software control". When checked you are in software mode and hardware mode when unchecked. What's also different is the lighting effects are linked to the mode you are in.. So if you add "Color Wave" in HW Mode, it will not be there in software mode (and vice versa).

Link to comment
Share on other sites

Thanks for the responses, guys.

 

That explains it. It's so darn strange that there's nothing that can be done to turn the RGB's off if you choose to save the RGB settings on the hardware itself.

I've decide to revert back to Hardware Mode so I can have the RGBs on the Mac OS as well.

 

Since I use my computer like I did with previous Macs, I tend to leave it on Sleep more often than Shut Down. With the RGBs left running without rest for most of the time, any ideas what its lifespan might be?

 

Also, what is the difference between checking or unchecking the box of having iCue start during Startup (Windows 10)?

Edited by KrustyKrab
Link to comment
Share on other sites

That explains it. It's so darn strange that there's nothing that can be done to turn the RGB's off if you choose to save the RGB settings on the hardware itself.

I've decide to revert back to Hardware Mode so I can have the RGBs on the Mac OS as well.

 

I am not sure how much change we will see on this. It would require the LEDs to be able to separate themselves from the rest of the power delivery through the RAM slots. That seems like a tricky subject on something that is already complex and expensive. The workaround is to use the software mode and leave the HW Mode to the off state, but that is where you are caught between the rock and the hard place.

 

 

Since I use my computer like I did with previous Macs, I tend to leave it on Sleep more often than Shut Down. With the RGBs left running without rest for most of the time, any ideas what its lifespan might be?

 

I am not sure we have any hard data or MTBF projections on the LEDs. It's not something that comes up very often and the RAM should have a lifetime warranty. Extremely likely you run out of uses for it before the LEDs go out.

 

 

Also, what is the difference between checking or unchecking the box of having iCue start during Startup (Windows 10)?

 

Your other devices have hardware modes as well, both for lighting and some saved elements for KBs and mice. With it checked the software will load about 10-15 seconds after the Wind 10 desktop appear and put you into software mode. If you leave it unchecked, you start in HW Mode until you manually launch the app. Since the bulk of your use will be in HW mode, you can probably leave it unchecked and only launch when needed.

Link to comment
Share on other sites

 Share

×
×
  • Create New...