Hi
I currently run windows 10 on my build and now I’m wanting to add windows 11 for dual drive boot setup.
So do the RGB peripherals like case fans, front case lighting, Li Lian Strimers, GPU et get affected by frequently switching between the two OS?
Should I make sure the RGB device software and processes are identical on both OS or just one/master?
To set my case fans and front lighting I use the cooler master software, to set the GPU I use the gpu software, RAM is by corsair software. I have found this works very well and I dont want to try and do things differently. All the RGB colors are permanently stored in the device except for the Strimers which get set back to rainbow only when the power goes out and they get set back to their settings once windows loads up.
When switching between each OS you’ll need the software installed on both OSes. It shouldn’t be a problem. Find the config file and copy it over and all SHOULD be fine.
At one point I had 4 separate apps installed for RGB , fans, AIO, and LCDs. Armoury Crate was causing boot loops (q-codes) and after some research I discovered these apps cause all kinds of problems. I uninstalled them all and switched to SignalRGB. Not only does it control ALL my hardware the effects options are endless. Its a thing of beauty to see all of your RGB in sync properly. I even got some external Govee wifi RGB light bars to sync up with my pc. If you want to dual boot Linux SignalRGB doesn’t support it yet, however OpenRGB does and its another great option.
OpenRGB is fantastic for cross-platform. Always has been. They actually reverse engineer (I think Signal does, too, unless they take ORGB’s code. I don’t know.) and should absolutely get donations if RGB is your thing.
I love openrgb. It doesn’t have the best UI, but it gives you pretty low level access and gets the job done. I did have to compile the latest master branch to get support for all my hardware (specifically MSI and Lian-Li RGB controllers) which can be done in Gentoo by unmasking the app-misc/openrgb-9999 build. (There were issues where the MSI code was bricking some controllers, but all the MSI code was refactored and it’s been re-enabled on latest … for the bold).
