Palit RTX 3070 GameRock OC canvas mode not working at all?

I’m having problems with newly installed GPU, it is Palit RTX 3070 GameRock OC, SRGB recognize this card as RTX 3070 GamingPro OC and only allows me to control it in forced mode.

No matter what I try there is no way to get it to work in canvas mode, when switching to canvas mode it just starts to blinks on its own?!?

UPDATE: If I am using solid color as canvas pattern it works if I select, only R, G or B channel but if I try to mix colors it is not working properly which is strange…

Hi, @LaVitaeBela

I think what you are seeing is actually the card working on single led, this is a firmware limitation, you can bypass that by using the argb cable that comes with the card, that will allows you to control all LEDs individually. As for the wrong name, can you go to https://srgbmods.net/s?p=view/debuginfo and tell me which ID your card has? It should be on bottom of the page.

I think you are right but the problem is that I didn’t get this cable with the card and to make it even worse there is no way to find anywhere to buy so I contact producer directly couple of days and I finally get all I need the right pinots on the card so now all I need to to solder my own cable and test it again, will keep you informed however…

OK, here is the brief update, I upgraded led firmware, connected the ARGB cable and it is still not controllable in the canvas mode:

00

What is also interesting is that card is prefectly controllable through its own software and I can get any effect and control all of available leds individually, s I am pretty sure there is no problem with either, firmware or connection?!?

It is quite irritating (as well as ugly) to see that main part of the ARGB setup shines on its own…

This is the source of the problem?!?

once you’ve done this

https://www.palit.com/argbsync/

which I imagine is outdated and this is what you should enable instead

imagen

You need to add a custom strip in your motherboard’s (or whichever controller you plugged the 3pin argb wire into) component configuration tab in SignalRGB->My Rig->Devices

This video explains the process quite well

Also, since its a different controller handiling the GPU lighting now, you can disable the GPU in SignalRGB
imagen

Hi Vermis,

I tied that already and no luck so far, first of all I disabled GPU as standalone device and than it stop to light immediately:

Than I connect GPU’s ARGB input to controller and that I got controller the card again, I can turn on or turn off lights, I can use any solid color based scene, if I try to use any dynamic effect it looks like it tries to sync but with totally wrong colors.

This is how it looks like, if I use solid color it responds properly…


BTW: As U can notice on the 2nd photo, MBO is not responding to SignalRGB, that’s something I reported way back and still didn’t get any respond, fix, workaround, solution…?

Blockquote This video explains the process quite well

I know how to connect and how to control it, I connected like a couple of hundred different devices but this one is drives me crazy :man_facepalming: … … .

Anyway, the problem is that no matter how I connect the GPU, I can control it with all other software except SignalRGB… and to make it even worse friend of mine because os some other hardware components that he can only control with SRGB ask me to fix this this however I know,

UPDATE: Apparently with some effects such as Ruby or Cherry Berry or Embers it works while on other hand with my favorites effects such as Neon fire or some random such as Rainbow it doesn’t…

This is EMBERES video

Tis is RAINBOW video for example which is totally out of sync :confused: :disguised_face:

ALL solid colors light up correctly, not only red? So if you set it to #00FF00 it lights up green and #0000FF makes everything blue?

Let me try once again but yes, I tested that already to check if all of three leds work correctly…

0000ff:

00ff00:

ffff00


Hmmm :thinking: now the strange behavior, this is supposed to be bluesih because the green and blue channel are set to highest possible value…

00ffff


If you didn’t observe the same kind of color inaccuracy when mixing green and blue in the native software, that could be explained by the manufacturer having custom ordered all of the LEDs used for this product from a supplier that offered to hand pick those with roughly the same luminosity rating for each channel and then tune their software to compensate for the natural variation that is simply part of how RGB LEDs physically work, see as an example the spec sheet of WS2812B-2020

Notice the huge differences in luminosity for each color given the same working current.

Manufacturer software has the upper hand over SignalRGB in this regard for now (because the program simply cannot account for how the LEDs in the products of over three dozen brands were sourced) until a global color calibration feature can be implemented.

Moving on to the primary topic. The reason why I wanted to know the result of trying all three basic colors, is eliminating the possibility of the LEDs in that GPU using a color order other than RGB (some are GRB, BGR, etc…) so now that that’s off the table it’s time to move on to next possible point of failure which, in this case, I suspect could be the component dimensional settings and placement in My Rig → Layouts.

If the component added to the first channel (port 1 in razer controller) in Signal’s Component Config tab is in fact the strip embedded into the GPU you should be able to change its X and Y position in the canvas, its angle of rotation and its scale in the aforementioned menu.

In that picture you can see the component I called GPU FS and its properties in the bottom-right part. If I changed those values it would “capture” a smaller/bigger portion of the effect and from a different position/rotation and that would effectively make it look like it’s lighting up with the wrong colors in relation to the other devices.

“Side to Side” is a good effect you can use to properly adjust those settings in “Layouts”.

Failing that, I just can’t fathom what else could be wrong.