On this wiki page, I suggest adding steps to create a task that kills OpenRGB On workstation lock that kills the current OpenRGB process with the action taskkill /f /im OpenRGB.exe This is where my first suggestion comes in to play: I scoured the wiki and found your page on resuming from sleep which worked, but resulted in two instances of the app appearing in my taskbar - the one that ran on boot, and the one that started upon logging in. Unfortunately, as soon as the PC went to sleep, it would wake with the lights off. This is where things get weird.Ĭircling back to the LEDs being off when booting, I learned how to make OpenRGB run on startup, which resulted in a working solution for turning on and setting my custom static warm white color upon logging in. I learned from this post that OpenRGB had re-enabled support for Mystic Light devices, so I decided to do a clean install and set up Windows with only OpenRGB. Initially I found that my PC's power LED would flash while sleeping, I learned that I could change this behavior from flashing to dual-color which would result in the LED remaining static while sleeping - you will see why this is relevant. Restarting my PC would keep the lights on, I suspected this was because power wasn't completely killed. When first building and booting on this board, the LEDs default to a rainbow effect, upon setting up Mystic Light and messing with colors and profiles I noticed that my PC would boot up with the lights off, originally I thought this was because I had changed my light settings but we'll get to this in a bit. This all began with my desire to move away from using MSI's infamous Dragon Center which is required to get a version of Mystic Light that works with newer boards like my MSI B550 Tomahawk. I have been running the latest build from here, I wanted to share my troubleshooting saga of using OpenRGB with MSI Mystic Light motherboards, because I suspect once you re-enable on the main release that you will start seeing people sharing similar issues. It is the result of several days of troubleshooting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |