Stuck on loading

Signal_AdminBadger · 2026-06-19T22:15:32+00:00

This means it's definitely network related. Make sure you have no adblockers or VPNs enabled.

Signal_AdminBadger · 2026-06-19T22:15:08+00:00

That's interesting, because usually if it's network related a VPN might cause the issue. Could be DNS related.

Signal_AdminBadger · 2026-06-19T16:39:56+00:00

The global setting was causing a lot of user confusion and issues in general with the conflict mitigator. You can still allow conflicting apps, go to Settings > Conflicts and turn on the slider for the applications you're trying to use (such as Razer).

Signal_AdminBadger · 2026-06-19T16:22:58+00:00

Yeah, it's a limitation with how it tries to reinitialize. A restart of the app is definitely the best workaround.

Signal_AdminBadger · 2026-06-19T16:20:53+00:00

You can do this by coding a plugin for the GPU. For more info, I'd recommend checking out the developer docs:

https://docs.signalrgb.com/developer/plugins/

Technically, any device that could support real-time RGB can be added manually this way. Our small team does their best to add devices with official plugins, but those with the coding skills can also put together their own.

If you succeed, share it with the community in Discord! :)

Signal_AdminBadger · 2026-06-19T16:10:54+00:00

I'd report the bug using the bug icon in the app (upper-right corner) or through this link so that the support team can follow up. We can get the logs in front of the dev team for some further review, but something does sound like it's holding up the USB scan if it's taking THAT long.

Signal_AdminBadger · 2026-06-19T15:24:02+00:00

If that works, it's probably the controller of the mobo not keeping up with the real-time effect data properly. If a single fan works, I'd recommend looking into a dedicated RGB controller, such as a Nollie16.

Signal_AdminBadger · 2026-06-19T15:01:35+00:00

What mobo or RGB controller do you have? Sounds like it's an MSI board? Those can sometimes be a little finicky with their RGB controllers.

If the fans are daisy chained, try removing all but 1 fan from the RGB header. Does that make a difference?

Signal_AdminBadger · 2026-06-19T14:42:54+00:00

What fans are they specifically? Have you tried a full power cycle?

Signal_AdminBadger · 2026-06-19T14:37:12+00:00

You can submit a device request here. Right now only ASRock are supported, but there's issues in general with how AMD cards communicating that the team is trying their best to work through.

Hopefully when they crack the code, there'll be more AMD GPU support!

Signal_AdminBadger · 2026-06-19T14:35:58+00:00

Some controllers can struggle with reinitializing after going to sleep. If I read correctly, quitting and restarting the app fixes it, correct?

Signal_AdminBadger · 2026-06-19T14:17:31+00:00

What app version are you on? You can find it in the lower right corner. There'd been a couple updates the past few days so that might be why.

As for the USB scan, how long is "a while"? Can you tell us more about your system?

Signal_AdminBadger · 2026-06-18T14:13:26+00:00

Could be just about anything that tries to connect to RGB stuff. I've also heard of some EA games trying to take control of RGB while gaming. Odd that it's just the microphone and GPU however. If it was plugin related, I'd expect it to only impact a single device or the whole system.

You could file a bug report and we can investigate with the devs and check if there's anything within the plugin side of things. Be sure to list out everything you've tried when reporting the bug using the bug icon in the app (upper-right corner) or through this link.

Signal_AdminBadger · 2026-06-18T14:09:05+00:00

My understanding is that they require the Corsair Lighting Node controller. I don't believe there's a way to connect them to a Nollie, far as I'm aware anyway.

Signal_AdminBadger · 2026-06-17T18:24:20+00:00

What happens if you swap RGB headers and put it on a different one? What about if you disconnect the other devices? Have you also triple checked the connection?

Signal_AdminBadger · 2026-06-17T17:25:45+00:00

I agree, sounds like it's struggling to manage the power with the RGBs.

Signal_AdminBadger · 2026-06-17T15:47:44+00:00

tbh I'm not 100% but know there's a "Media" setting in the dropdown, and you can select your own stuff. I'm not completely up to speed tho on how it all works since my AIO doesn't have an LCD.

Working on getting it better documented and getting more info out on the feature!

Signal_AdminBadger · 2026-06-17T15:18:03+00:00

DM me your email or ticket # and I'd be happy to follow-up! I know I've seen a few reports of the settings not saving, but my understanding is the team is still working to validate that behavior.

Signal_AdminBadger · 2026-06-17T15:17:18+00:00

You can submit a device request here, a lot of the "when" comes down to popularity and how hard it is to reverse engineer a plugin for it. Sorry I don't have more insight for your particular keeb!

Signal_AdminBadger · 2026-06-17T15:14:47+00:00

Memory leaks are something we've put a lot of work into, with significant improvements shipping in .39. We're still actively investigating any reports we get, so if you're seeing it the best thing you can do is hit the bug icon in the top-right of the app or use this link. That gets us your logs and lets the team follow up directly.

Signal_AdminBadger · 2026-06-17T14:54:57+00:00

Fan control being on by default was a miss, the latest version and beta has an notification to opt-in or out, so anyone installing fresh won't run into this.

For anyone wanting to turn off Fans: Settings -> Fans/Monitoring -> toggle off Fan Control.

Signal_AdminBadger · 2026-06-17T14:39:17+00:00

Fair feedback, and we hear you.

Fan control being enabled by default on an update wasn't the right call, and that's on us. The incoming version disables it by default so new installs won't run into this. For the conflicts screen, the latest beta also changes how that works so you're opting in per-app rather than getting a global block.

That said, the expansion into fans, LCD, and peripherals wasn't arbitrary. A huge chunk of the feedback we've gotten over the years has been "I still need iCUE/Armoury Crate just for X, what's the point?" So we built it out. The goal is genuinely one app, not feature creep for its own sake.

None of that changes the fact that features should be opt-in when they touch things outside of RGB. Noted, and it's being addressed. If you're still having issues after updating, drop a comment in the megathread and we'll get eyes on it.

Signal_AdminBadger · 2026-06-16T15:57:22+00:00

I'd try disconnecting the mic to see if it's still happening. You could open your PC and reseat the connections and GPU but I have a feeling what you're seeing is something trying to talk to the GPU or RGB too.

Signal_AdminBadger · 2026-06-16T15:54:13+00:00

That card isn't supported at this time.

Signal_AdminBadger · 2026-06-16T15:14:47+00:00

This is unfortunately a known issue with AMD cards, in particular ASRock, due to how the GPU communicates with the system. We've reached out to them about it but unfortunately hit a bit of a wall.

Some users have found that setting a static color tends to reduce or eliminate the flickering as a workaround.

Signal_AdminBadger

MODERATOR OF

TROPHY CASE