|
![](/i/fill.gif) |
Simen Kvaal wrote:
>
> Given this code (actual sample); why does not MinEllipsoide2 produce exactly
> the same results? What are the precedence of the textures here? Logically,
> the whole intersection should get the reflective finish, but instead it gets
> the default. What am I missing?
My guess would be that "pigment { ... }" all by inself is being
interpreted as if it were "texture { pigment { ... } }", that is
to say, because you assigned one element of the texture to the
component, it was read as if it were the full definition of a
texture (or at least as full as you saw fit to assign) so the fact
that that texture had no finish caused it to default. Then,
by the time it reached the stand alone finish at the end, all
the elements already had textures, so the finish at the end
was ignored since nothing seemed to need it.
Post a reply to this message
|
![](/i/fill.gif) |