 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi guys,
Can't figure out while I am getting different object's colors when using
definition for 'finish' component compared to 'non-defined' 'finish'.
Could anyone please explain this behavior ?
Scene in attachment.
Thanks in advance.
Post a reply to this message
Attachments:
Download 'out.zip' (827 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
"yesbird" <nomail@nomail> wrote:
> Can't figure out while I am getting different object's colors when using
> Could anyone please explain this behavior ?
can't, really. best guess is that in only one of the two scenarios the colour
value(s) are subject to "rounding errors"[*]. also think, looking at the code,
that I probably would use the "full-spec" 5-vector notation for colours.
[*] <https://wiki.povray.org/content/Reference:Color_Expressions>
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"yesbird" <nomail@nomail> wrote:
> Hi guys,
>
> Can't figure out while I am getting different object's colors when using
> Could anyone please explain this behavior ?
> Scene in attachment.
>
I can't readily see the difference - they ought to be semantically the same?
What I DO notice is that you're using color values like:
rgb <8.00, 2.00, 3.00>
and POV-Ray uses rgb channel values ranging from 0-1. So - maybe something is
happening "under-the-hood" when those values exceed unity. I'm suspecting it's
the "metallic" keyword coupled with the large rgb values, as it causes
reflections to multiplied by the rgb pigment values. But why defined and
undefined are different....?
Maybe fiddle with that, and if it still doesn't work, try some other
permutations of defined and undefined texture/pigment/finish and see if anything
pops out.
Just an aside:
It would be easier for the forum readership at large to see your render issues
and review your code if you kept everything in a monolithic scene file (no
#include dependencies) and just attached the scene file and the render to your
post.
It just might make the difference between you getting a speedy, helpful answer,
or waiting a day or two before someone dowlnloads, unzips, and renders your
scene file(s)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"yesbird" <nomail@nomail> wrote:
> Hi guys,
>
> Can't figure out while I am getting different object's colors when using
> Could anyone please explain this behavior ?
> Scene in attachment.
>
It's early, and I'm headed out.
I'm at the stage where I'm rendering both versions, and they look the same to
me.
I'm just commenting out the relevant code in the same code block, but switch
case break end would be a good swapping strategy for intentional "version"
switching.
no need for the "color" keyword - it's completely superfluous.
#declare finish_default = finish {phong 1 reflection {0.10 metallic 0.4} }
#declare tex_pink = texture { //Polished_Chrome
pigment{ checker rgb <8.00, 2.00, 3.00> rgb <8.00, 2.00, 3.00> }
//finish {phong 1 reflection {0.10 metallic 0.4} }
finish { finish_default }
}
Maybe do a difference with a plane, and assign one texture version to the left
side, and the other to the right, with the inverse difference (or an
intersection with a box) and compare side by side in the same render.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> #declare tex_pink = texture { //Polished_Chrome
Aha! It's that //Polished_Chrome that doesn't belong there for any reason.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Just an aside:
> ...
>
> It just might make the difference between you getting a speedy, helpful answer,
> or waiting a day or two before someone dowlnloads, unzips, and renders your
> scene file(s)
Thanks, I will take in into account.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> ...
> I probably would use the "full-spec" 5-vector notation for colours.
>
> [*] <https://wiki.povray.org/content/Reference:Color_Expressions>
>
Thank you, I will.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscape net> wrote:
> > #declare tex_pink = texture { //Polished_Chrome
>
> Aha! It's that //Polished_Chrome that doesn't belong there for any reason.
Exactly, 'Polished_Chrome' has influence, I can fix it now.
Sorry for stupid question, probably I need examine documentation more carefully.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
"yesbird" <nomail@nomail> wrote:
> ... stupid question ...
no such thing. stupid answers, otoh, are a different kettle of fish. </grin>
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
