Simonas Kazlauskas

The answer is the same as [before](https://github.com/nagisa/msi-rgb/issues/21#issuecomment-391360571). I simply cannot tell without having hardware in hand, because all the minor "features” may one way or another influence the board design...

SDKs are generally useless, as they rely on their own custom Windows driver to be loaded and present before any control can happen. Ideally we’d have reliable code for every...

It is very possible that it just doesn’t work, or if it does work, it controls something else than JLED1.

That being said, it is not something I can investigate on my own, as I do not have access to the hardware in question :)

Unless you’re willing to do the work of figuring out what Windows’ MSI app does, alas.

Thanks for the information. Sadly, I’m unable to do anything about it without access to the hardware, unless you are willing to fiddle with your motherboard like [this person did](https://github.com/nagisa/msi-rgb/issues/6#issuecomment-425721615)...

Are those captures of the 12th bank? Sadly, nothing, in how RGB control is done, seems to be similar to non-Mystic RGB. I could try implementing disablement of RGB (that...

Ah, now that I think about it does not matter, because the MSI’s tools change the “bank” to the correct one when fiddling with colours and RWEverything simply begins displaying...

Alas, it seems like there are very many motherboards that this tool won’t work with. The best way to make it work, is to boot up windows, figure out what...

Unclear. On my motherboard it controls the 5050 header and the LEDs on the motherboard itself, but control happens through a independent chip, which may also implement support for mystic...