EvanMulawski
RGB Megathread
This issue is a megathread for RGB/lighting knowledge and issues with Corsair devices when using this plugin. New issues that are created related to RGB will be closed and directed here.
Understanding Corsair Device Modes
Corsair devices operate in two distinct modes:
- Hardware Mode: This is typically the default mode of the device when it is initially powered on. Depending on the device, some limited cooling and RGB configuration that is stored on the device will be used. Nothing can read from or write to the device when it is in this mode. For iCUE users, this is generally the mode devices enter when iCUE is closed or not running.
- Software Mode: This mode allows reading from and writing to the device. When this plugin is initialized by Fan Control, all connected and supported devices are commanded to enter this mode. However, because Fan Control is not RGB software, all device RGB will enter either a default or uncontrolled state (depends on the device). It may seem that the RGB is "disabled" or "off," but it is simply because the device is waiting for some RGB software to tell it what to do.
Corsair devices cannot operate in both modes simultaneously, nor can the cooling features be placed in Software Mode when the RGB features are in Hardware Mode. Why? Corsair expects everyone to use iCUE for their hardware, which handles all functions.
Third-Party RGB Software
If you are here, you probably don't want to use iCUE for your Corsair devices. If you want to use Fan Control and this plugin, you will have to use another third-party program to control your device RGB.
Currently, there are two options:
- SignalRGB
- OpenRGB (limited device compatibility)
Every effort will be made to ensure this plugin is compatible with third-party RGB programs. In fact, I added support for the well-known mutex to OpenRGB and worked with the SignalRGB team to enable interoperability.
However, RGB-specific issues and requests are outside the scope of this plugin and only issues that are directly caused by this plugin or its interoperability will be considered for triage.
Current Exceptions
-
The "Hydro Platinum" series of AIOs.
This device family currently has minimal RGB support and can be configured. However, there are some issues, both reported and personally observed, with this implementation and it may be removed in the future.
Known Issues
RGB on the pump head of "Hydro Platinum" series AIOs may act strangely, reset brightness, or partially change color.
See #174, #189
Workaround: none
RGB stuttering or lagging with third-party RGB programs
This is a limitation of implementing interoperability using the well-known mutex. This issue can also occur when using RGB software with hardware monitoring software like HWiNFO. It is the responsibility of each program to hold the mutex for as little time as possible.
See #183
Workaround: none
I am struggling to understand why it is that openrgb will support the commander controllers and the Hydro Platinum, but not the icue link. Is there something im missing to make this work like a device ID needing to be added to the code? What's the difference with how SignalRGB is doing things? Thank you for the controller and your hard work on getting RGB working, I have been reading through as much as I can on github and gitlab.
Copy and pasting my issue from the Fan Control github-
Describe the bug
- Fans are connected to a Corsair Commander Core XT for both fan control and RGB 2, Corsair iCue was used to set 'hardware settings' for RGB, then exited the program so that iCue does not attempt to control the fans
- Stop the Corsair.Service etc in Task Manager
- Start Fan Control
- The RGB for the fans connected to the Commander Core XT turns off completely Notably, I also have a Corsair Commander Pro with other RGB components and these do not get shut off.
Is there a log.txt file next to FanControl.exe with recent date entries? [Link it here]
Relevant hardware specs and setup AMD 5800x NVidia RTX 3080 Gigabyte B550 Gaming X V2 32gb Corsair Vengeance RGB Corsair Commander Pro with Corsair XD5, XC7 attached to RGB and PWM Corsair Commander Core XT with misc RGB fans attached to RGB hub pins and PWM Fan Control v226 (NET v4.8) with Corsair Link plugin
I am struggling to understand why it is that openrgb will support the commander controllers and the Hydro Platinum, but not the icue link. Is there something im missing to make this work like a device ID needing to be added to the code? What's the difference with how SignalRGB is doing things? Thank you for the controller and your hard work on getting RGB working, I have been reading through as much as I can on github and gitlab.
OpenRGB relies on the community to provide implementations for device support. SignalRGB has a dedicated development team and the resources to implement device support themselves.
iCUE LINK has a very similar communication protocol to the Commander CORE devices, but iCUE LINK is a hub that communicates with multiple devices (which is why my implementation here is separate from the Commander CORE series).
Copy and pasting my issue from the Fan Control github-
Describe the bug
- Fans are connected to a Corsair Commander Core XT for both fan control and RGB 2, Corsair iCue was used to set 'hardware settings' for RGB, then exited the program so that iCue does not attempt to control the fans
- Stop the Corsair.Service etc in Task Manager
- Start Fan Control
- The RGB for the fans connected to the Commander Core XT turns off completely Notably, I also have a Corsair Commander Pro with other RGB components and these do not get shut off.
Is there a log.txt file next to FanControl.exe with recent date entries? [Link it here]
Relevant hardware specs and setup AMD 5800x NVidia RTX 3080 Gigabyte B550 Gaming X V2 32gb Corsair Vengeance RGB Corsair Commander Pro with Corsair XD5, XC7 attached to RGB and PWM Corsair Commander Core XT with misc RGB fans attached to RGB hub pins and PWM Fan Control v226 (NET v4.8) with Corsair Link plugin
This is explained above in the "Understanding Corsair Device Modes" section. The device cannot be in hardware mode for RGB and software mode for fan control - it's one or the other for both RGB and cooling.
Feature request.
May we please have a release with the RGB control code disabled?
I run a zero RGB system. The color defect bug consistently makes my pump light turn on. A behavior that didn't happen with SIV.
I just need this plugin to control fans.
curious if anyone has had this issue, everything worked fine but since windows detecting fancontrol as a trojan i uninstalled and have set it back up using the fix changing the .dll file, now all my fan curves are set back up but when i launch the app my rgb on the corsair aio fans and pump goes off, if i close fancontrol and open icue they come back on, is there a way to fix this without additional software as i haven't always had this problem?
@pete-ops Update the application and install https://pawnio.eu/
This is the new driver, you can alternatively install this via the app in the settings panel
