|
![](/i/fill.gif) |
In article <38b63a7e@news.povray.org>, "Gail Shaw"
<gsh### [at] monotix co za> wrote:
> The last texture should be layered over the others, instead
> of just applying to objects without a texture.
That is a good idea, although it would have to be used with a version
switch. Maybe also provide for switching this off for specific objects,
something like:
union {
no_layer_over {
object {MyObject1 texture {A...}}
}
object {MyObject2 texture {B...}
...
texture {C...}
}
MyObject1 would have texture A, and only texture A. MyObject2 would have
texture B with texture C layered over it. This would be nice if you have
a CSG with dozens of parts and which has one with a different texture.
no_layer_over(again, can someone please come up with a better keyword?)
could act like a kind of union, and contain multiple objects. Perhaps it
could contain the texture for it's objects itself...
Of course, this would need to be controlled by a #version switch,
otherwise nearly every CSG ever done will need to be redone.
Also, remove the limitations on layering patterned textures.
--
Chris Huff
e-mail: chr### [at] yahoo com
Web page: http://chrishuff.dhs.org/
Post a reply to this message
|
![](/i/fill.gif) |