|
 |
On 2026-03-20 08:10 (-4), Bald Eagle wrote:
> "GioSeregni" <gms### [at] hotmail com> wrote:
>
>> triangle{<3.2475,.9143,6.0001><3.4358,.9376,5.9847><3.2475,.9376,6.0047>
>> pigment{color rgb<255/255,63/255,0/255>}}
>>
>> triangle{<3.2475,.9143,6.0001><3.4358,.9376,5.9847><3.2475,.9376,6.0047>
>> pigment{color rgb<1,63/255,0>}}
I'm confused. Both colors specifications should be orange, but I see no
orange in the images. The only difference I see is areas that are black
on the left and white on the right, and that does not look like a gamma
issue.
It would help if we had more context for this code. When I incorporated
the triangles in a scene, they both were the expected orange.
> This is VERY interesting Gio.
>
> Apparently the color keyword applies gamma handling,
> but using just rgb is linear color.
>
> Remove the color keyword and see if the colors are the same.
>
> I'd also be interested to see what happens if you do your multiplication first.
> #declare Color = <255/255,63/255,0/255>;
> pigment{color rgb Color}}
>
> I guess "color" triggers legacy gamma correction rules, which exists for
> backwards compatibility.
>
> - BE
>
> “The color keyword causes POV‑Ray to treat the given RGB values as
> gamma‑encoded color values, applying the scene gamma correction rules.
> The plain rgb keyword specifies linear RGB values.”
>
> And:
>
> “The color keyword is deprecated and should be avoided in new scenes.”
Whoa, this is news to me! Where is this in the documentation?
This has implications for macros that force promotion on its arguments
or that return vectors to be used as colors. Sometimes the only way to
avoid a parse warning or parse error is to use the color keyword.
Post a reply to this message
|
|
