It did work exactly one time after manually launching SignalRGB as admin and the RAM showed up in the Devices as “Aura compatible” and I was to control it.
However right after this I installed my chipset driver (new Windows install) then rebooted and since then, my RAM has not shown up again at all in Devices (even while launching as admin) and cannot be controlled. Below are the device models:
Motherboard: Gigabyte Z390 Aorus Elite
RAM: XPG Spectrix D41
Could possibly be an issue with that chipset version, are you able to try rolling it back? Might also help to double check for any updates to SMBus drivers or BIOS. Try a full power cycle too if you haven’t already, that helps with many issues as a base troubleshooting step to restart all the underlying services.
I’m on the latest SMBus and BIOS from the Gigabyte site. I was able to get this (mostly) working though. I installed and ran the Gigabyte RGBFusion, then launched SignalRGB after, and it would have no further issues with controlling the RAM even across reboots.
But if I do a full power cycle, the original issue comes back and the RAM doesn’t show up in SignalRGB. If this happens, I need to close SignalRGB, launch RGBFusion, then relaunch SignalRGB again and it starts working fine until then next full power cycle.
I did some internal investigation and found that power-cycle clue matches an open investigation. Could you email [email protected] two logs?
Turn on Settings > Application > Windows > Enable Debug Logging, restart, then capture one run with the RAM missing (no RGB Fusion) and one after RGB Fusion.
Send the two newest files from %LocalAppData%\WhirlwindFX\SignalRgb\Logs and link this thread (so we know it’s you!). Also fully close RGBFusion before opening SignalRGB, together they fight over the same bus.
Logs have been sent, thanks!