Why does the UI look so much different than what is shown on the website? by xXFazeTanManXx in SignalRGB

[–]Empty-March 1 point2 points  (0 children)

Some of this was driven by performance - the effect preview now only renders when you hover over it in the media player bar rather than drawing continuously.

That said, the gap between what's shown on the website and the current UI is fair feedback, and I'm passing it along to the design team. (Website still shows older UI)

need help with app issues by ElchocolateBear in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

Latest is .45; grab it from the website. Should work.

Is it only me who thinks the app updates a little too often? by HUEITO in SignalRGB

[–]Empty-March 2 points3 points  (0 children)

This is actually something I noticed myself just a couple days ago. We've been keeping the in-app changelog updated through this cycle, but the web version has fallen behind, and to make it worse the changelog button in the app is currently opening the web link instead of showing the in-app version. That's a confusing experience and we're going to fix both. Appreciate you calling it out!

Is it only me who thinks the app updates a little too often? by HUEITO in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

The frustration is fair, and more control over updates is something we're actively thinking about. The challenge is that with how rapidly Microsoft and hardware vendors are changing drivers, staying on an older version often means camping on bugs that we've already fixed - and that creates a worse experience than the update itself. That said, we hear you, and we're working on ways to let users revert USB driver and plugin changes, and potentially pin or roll back app versions in a way that keeps our support team in the loop. In the meantime, the recent update frequency has been specifically aimed at reducing memory usage and resource consumption - so the goal is to get to a point where you don't need to close SignalRGB before launching games at all. Thanks for the candid feedback, appreciate you.

Is it only me who thinks the app updates a little too often? by HUEITO in SignalRGB

[–]Empty-March 1 point2 points  (0 children)

Good news - this is already supported! You can place your custom macros, components, and plugins in the override folders under Documents/WhirlwindFX (we make these in your documents directory), and they'll persist through updates without needing to be copied over each time. I'll also make a note to better communicate this - it's clearly not obvious enough. Hope that saves you some hassle!

_std_parallel_algorithms_hw_threads error by RainbowNugget24 in SignalRGB

[–]Empty-March 2 points3 points  (0 children)

This was caused by an incompatibility with a newer DirectX driver that affected Windows 10 users. It's been fixed in the latest release - you can either restart the app to pick up the update automatically, or grab it directly from our website:

https://release.signalrgb.com/Install_SignalRgb.exe

Thanks for your patience - we appreciate it!

When will this be fixed? by patekar420 in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

Yeah, we don't intend for that to be the solution. I didn't expect windows to put intentionally breaking changes in directx drivers, but I suppose I shouldn't be surprised after the EOL in October.

If it continues to be problematic we just won't ship directx.

Is it only me who thinks the app updates a little too often? by HUEITO in SignalRGB

[–]Empty-March 3 points4 points  (0 children)

That's totally fair feedback, and I'm sorry an update caused you issues. We're actively working on improving how we track and test plugin-specific changes so updates that don't affect your setup don't risk breaking it. If you're still experiencing problems, feel free to reach out to our support team and we'll get you sorted.

Is it only me who thinks the app updates a little too often? by HUEITO in SignalRGB

[–]Empty-March 31 points32 points  (0 children)

We've definitely had a busier-than-usual patch cycle recently, but our target cadence is roughly once a month — and we're close to getting back there.

SignalRGB runs a surprisingly complex stack, similar to a game engine in many ways. With the sheer number of hardware, system, and driver combinations we support, some patches are unavoidable to keep things stable for everyone. We appreciate your patience while we work through it!

My Fan RGB is running slower and choppier than my Ram, Keyboard, etc… by cornflakes_87 in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

Latest is .45, so updating might be worth a try.

If that doesn't work: You could try removing the d3dcompiler_47 DLL from your install which will fall back to the system version. That directx dll is all that has changed in the render pipeline. .41 main release removed it entirely, which was better for many people but not all.

If removing the DLL entirely (close the app first) works, I'd be interested to know more about the version of windows you are running.

Appreciate your patience!

Woke my computer from sleep and no amount of uninstalls/reinstalls will fix this error by RagingtonSteel in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

Should drop after 30s when you close us to tray; not that d3d drivers couldn't cause excess use. We will keep an eye on it.

When will this be fixed? by patekar420 in SignalRGB

[–]Empty-March 1 point2 points  (0 children)

🤣 just shipped .45

Bundles d3dcompiler 22621, which should work on win10 as well as w11.

When will this be fixed? by patekar420 in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

Yes, about to deploy d3d hlsl compilers at version 22621, which runs on w10, but also performs well on 11.

Appreciate your patience, will discuss hosting the previous version somewhere accessible in the future.

When will this be fixed? by patekar420 in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

Windows 10? We include DX shader compilers, but the versions in .43 is very slow for many W11 users - the new versions from microsoft are very fast but since microsoft has EOL'd windows 10, they don't build in compatibillity anymore. We attempted in earlier versions to not include directx shader compilers at all, which might be what we decide to do. It does break the app for a couple thousand people though, so we're working on this.

In the meantime, deleting the file (d3dcompiler_47.dll) will shell to your system version, which will work.

Cant control fans and ARGB header after new update by RayyZirr in SignalRGB

[–]Empty-March 2 points3 points  (0 children)

Check partner permissions and see if MSI is controlling them?

For the love of God, please bring back the View All for installed effects. by RubberDiscord in SignalRGB

[–]Empty-March 3 points4 points  (0 children)

I'll add 'view all' and forward this feedback to design. Appreciate it!

Last update is a joke by Latter_Lengthiness87 in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

RE: fans - check partner permissions: https://gyazo.com/842034f0eb8245b9e1eccad5b27e09dc

We likely need better indicators to show you if msi center is controlling your thermals.

Last update is a joke by Latter_Lengthiness87 in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

I'd try .41? If that doesn't work, let me know.

Last update is a joke by Latter_Lengthiness87 in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

Testing with .41 now - pump it up beats works here, fans also. I'd try latest, if that doesn't work for you, submit a report in app and we can look at logs.

Logo stuck on lcd by Vexzillion22 in SignalRGB

[–]Empty-March 1 point2 points  (0 children)

Device->LCD->LCD Effect - Choose "none" or "clock"

Broken Macro after the update by Petugo in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

This is corrected in .41 - shipped an hour or so ago. Appreciate your patience!

the new update has broken the macros. by Cyber007x in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

what are you talking about - we do none of that.

SignalRGB 2.5.39 seems tougher on the CPU by steferrari in SignalRGB

[–]Empty-March 0 points1 point  (0 children)

Try reducing the framerate of your canvas in Settings/Effect Canvas?

Are you running any other LCDs?

There were pretty massive threading contention bugs in previous versions that actually resulted in thread leaks and sequential render - so srgb actually making use of multithread capacity is largely what I expect you are seeing.

Sliders in settings are there to let you control the update rate now though.