Kyle <hob### [at] gatenet> wrote:
> SharkD,
>
> What you've done here is nothing more than nesting unions to build the complete road
brick by brick, which will be a 
huge memory hog.  It's basically the same as removing the outer union and loop (the
> one using the S variable), and then increasing Z to a value of Z*S.  In the original
code, the road is built from pre
defined sections of bricks, which consumes considerably less memory and saves allot
> of parse time as compared to the brick by brick method.  Plus, I think the way
you're applying the second texture wil
l still show breaks between the sections.
>
> I think I'm going to have to change my scene.  Instead of having the brick road fade
out into the distance, I may try
 curving it enough to have it diminish from view more quickly.  Another possibility
> is that I may use the brick by brick method to a point, and then switch over to
another object for the distant bricks
, such as a box with a home-brewed brick pattern applied.
>
> I still think a method to layer a texture over a union of individually textured
objects would be a greatly welcomed f
eature addition to POV-Ray.  This isn't the first time I've run into a circumstance
> where such a feature would provide the simplest solution to a problem.

I did this to illustrate the fact that, in order for the texture not to repeat
for each section, the value for S must be passed to the texture. This is not
possible if the declaration of the object comes before the declaration of the
parameter, S.

This was in response to your remark that my *earlier* suggestion would not work
for this reason. If you combine the two methods (e.g., define an object that
gets re-used for each section, apply a texture to each re-use of this object
that takes into account the parameter S), it will work.

Post a reply to this message