"Kenneth" <kdw### [at] gmailcom> wrote:

>
> In other words, the material{texture{pigment[...}}} 'hierarchy of importance'
> actually stops at texture{...}, conceptually speaking.
>

To clarify that a bit more: A 'material' container's function (the only one I
know of) is to encapsulate a texture{...} with an interior{...}--since they are
both separate code chunks, and there's no other way to #declare them together so
that the combination can be easily used in multiple places in the scene code.

The 'transform' keyword serves the same sole(?) purpose--

#declare my_transform =
transform{
rotate{...}
translate{...}
matrix{...}
--etc. etc.
}

And the docs say that using a transform block like this is more efficient for
POV-Ray than typing all those various individual 'transforms' every time they
are needed, as-is, in a group. Perhaps the same efficiency is produced by a
'material' container.

Post a reply to this message