Making everything else gamma-correct is actually complicated and potentially a lot of work. It was only done for Drawing Canvas

Ok, then maybe create an option only for Drawing Canvas? Ofcourse its probably not the №1 feature to implement, but I think its necessary.

Ashley

See this blog post about gamma for more background and theory.

Ok, for text and 3D I agree that gamma-correct colors looks better and it worth implementing, but for 2d gradients... Well, I would prefer to use the option that is used, for example, in Photoshop or any other software that I use to create/edit images. And if that softaware uses gamma-correct values, than ok, but if not, maybe let me force C3 to use gamma-incorrect colors? Like i said:

Maybe add project property to let user decide which option he wants to use?

And by default let it be like it is right now. What do you think?

Also, what is the "sprite gradient" everybody is talking about in this thread?

I guess its Sprite blend mode/effects related.

Note that Drawing Canvas gradients are gamma-correct, but sprite gradients are not. (In other words Drawing Canvas does gradients the right way, and sprite/everything else uses the wrong way.) So it is expected that if you compare Drawing Canvas to Sprite, you will see different results - the difference between gamma-correct and gamma-incorrect.

But why did you decide to make CORRECT results AND INCORRECT at the same time? It is inconsistent, I think. Maybe add project property to let user decide which option he wants to use? Like "Gamma-correct" (including Sprites) and "Gamma-incorrect" (including DrawingCanvas).

Alon

rgba(Red, Green, Blue, Alpha)

uses values for chanels and alpha from 0 to 100, NOT 255.

rgba255(Red, Green, Blue, Alpha)

uses values for chanels and alpha from 0 to 255.

Its not looking like you would expect, BUT much better already:

Alon

You can make what you want using the Drawing Canvas

Try this:

https://ufile.io/ki20dkr2

Yes, but there is one little problem:

To avoid this, you need to use "DrawingCanvas.PixelScale".

My version.

drive.google.com/file/d/1YvNtZMYXznLBOW7MqD_LI7OtbGzbAr0H/view

Move to X, Y works good, seems like a bug...but its still in beta, so, just use direct coordiantes :)