Functionality that I think would be helpful is a method to overlay a previously
textured object with
a new texture.  Perhaps this could be specified with an "overlay" keyword, such as
this:

object {
  o_PreviouslyTexturedObject
  texture {
    pigment { p_PartiallyClearPigment }
    overlay
  }
}

This simplistic example does not demonstrate how helpful this functionality would be. 
A better
example is a recent scene that I was working on in which I was building a brick road. 
I defined a
section of road as a union of 36x100 randomly textured bricks.  I then placed the
sections
end-to-end to form the complete road.  I wanted to have lines on the road too, but
wanted some
waviness to the lines for more realism.  Overlaying a texture on the entire road would
be the
simplest method, providing there was a method to do so.

Post a reply to this message

Kyle wrote:
> This simplistic example does not demonstrate how helpful this functionality would
be.  A better
> example is a recent scene that I was working on in which I was building a brick
road.  I defined a
> section of road as a union of 36x100 randomly textured bricks.  I then placed the
sections
> end-to-end to form the complete road.  I wanted to have lines on the road too, but
wanted some
> waviness to the lines for more realism.  Overlaying a texture on the entire road
would be the
> simplest method, providing there was a method to do so.

In this example, you could actually place all the bricks in a union and 
give them a single texture block.

-- 
...Ben Chambers
www.pacificwebguy.com

Post a reply to this message

> Functionality that I think would be helpful is a method to overlay a 
> previously textured object with
> a new texture.  Perhaps this could be specified with an "overlay" keyword, 
> such as this:
>
> object {
>  o_PreviouslyTexturedObject
>  texture {
>    pigment { p_PartiallyClearPigment }
>    overlay
>  }
> }

Uh - you can already do this can't you? just take out the "overlay" keyword 
and it works!

Post a reply to this message

scott <sco### [at] laptopcom> wrote:
> Uh - you can already do this can't you? just take out the "overlay" keyword 
> and it works!

  No, because a later texture definition will not modify an existing one.

-- 
                                                          - Warp

Post a reply to this message

Chambers <ben### [at] pacificwebguycom> wrote:
> Kyle wrote:
> > This simplistic example does not demonstrate how helpful this functionality would
be.  A better
> > example is a recent scene that I was working on in which I was building a brick
road.  I defined a
> > section of road as a union of 36x100 randomly textured bricks.  I then placed the
sections
> > end-to-end to form the complete road.  I wanted to have lines on the road too, but
wanted some
> > waviness to the lines for more realism.  Overlaying a texture on the entire road
would be the
> > simplest method, providing there was a method to do so.
>
> In this example, you could actually place all the bricks in a union and
> give them a single texture block.
>
> --
> ...Ben Chambers
> www.pacificwebguy.com

I think what he wants to achieve, is to have the subtextures for each brick
different by some degree and applied to each brick individually.
There are some ways this could be achieved with a single texture block, but they
would tend to be very complex, a texture overlay would be a lot simpler.

-tgq

Post a reply to this message

On Fri, 25 Jan 2008 01:05:15 -0800, Chambers <ben### [at] pacificwebguycom> wrote:

>Kyle wrote:
>> This simplistic example does not demonstrate how helpful this functionality would
be.  A better
>> example is a recent scene that I was working on in which I was building a brick
road.  I defined a
>> section of road as a union of 36x100 randomly textured bricks.  I then placed the
sections
>> end-to-end to form the complete road.  I wanted to have lines on the road too, but
wanted some
>> waviness to the lines for more realism.  Overlaying a texture on the entire road
would be the
>> simplest method, providing there was a method to do so.
>
>In this example, you could actually place all the bricks in a union and 
>give them a single texture block.

Yes, it would work.  The problem was that the memory used by a 2000x37 brick road
exceeded the memory I had available and drive thrashing ensued.  Breaking the road
down into sections resolved the
memory issue, but then I couldn't texture the road as one object.  Here's a link to a
thread where I posted an example and the discussion led to a solution, although it
used more memory than an
overlaid texture would...

http://news.povray.org/povray.general/thread/%3Chp0ro31f9m1dr7spccdp4g3j0hj5fvhdh0%404ax.com%3E/


There are other examples I can think of where overlaying a texture would be applicable
as well.  What if you want to add a texture layer to a predefined, pre-textured mesh
object, perhaps one that's
UV mapped using image maps?  That'd be kind of complex, if not impossible, without
being able to overlay the existing texture.

Perhaps you have a complex object that you've built and textured, but it looks to
clean and you want to add a little "dirt".  You can go back and use layered textures
on each piece of the object, or
you can overlay one dirt texture over the entire object.  Imagine trying to transform
the dirt texture on each piece of a complex object to have any patterns in the dirt
line up properly between
pieces of the object.  An overlaid texture would be much simpler.

Post a reply to this message

On Fri, 25 Jan 2008 11:30:10 +0100, "scott" <sco### [at] laptopcom> wrote:

>> Functionality that I think would be helpful is a method to overlay a 
>> previously textured object with
>> a new texture.  Perhaps this could be specified with an "overlay" keyword, 
>> such as this:
>>
>> object {
>>  o_PreviouslyTexturedObject
>>  texture {
>>    pigment { p_PartiallyClearPigment }
>>    overlay
>>  }
>> }
>
>Uh - you can already do this can't you? just take out the "overlay" keyword 
>and it works!
> 

With basic objects, yes, but not with complex objects.

Try this...


#declare p_PartiallyClearPigment =
  pigment {
    granite
    color_map {
      [0 rgbf 1]
      [1 rgb <1,0,0>]
    }
  }

#declare o_PreviouslyTexturedObject =
  union {
    sphere { 
      x/2, 0.5 
      pigment { rgb <0,1,0> } 
    }
    sphere { 
      -x/2, 0.5 
      pigment { rgb <0,0,1> } 
    }
  }

object {
  o_PreviouslyTexturedObject
  texture {
    pigment { p_PartiallyClearPigment }
    //overlay
  }
}

Post a reply to this message

On 25 Jan 2008 07:37:31 -0500, Warp <war### [at] tagpovrayorg> wrote:

>scott <sco### [at] laptopcom> wrote:
>> Uh - you can already do this can't you? just take out the "overlay" keyword 
>> and it works!
>
>  No, because a later texture definition will not modify an existing one.

Scott is partially right.  This works...


#declare p_PartiallyClearPigment =
  pigment {
    granite
    color_map {
      [0 rgbf 1]
      [1 rgb <1,0,0>]
    }
  }

#declare o_PreviouslyTexturedObject =
  sphere { 
    x/2, 0.5 
    pigment { rgb <0,1,0> } 
  }

object {
  o_PreviouslyTexturedObject
  texture {
    pigment { p_PartiallyClearPigment }
    //overlay
  }
}


... but it will not work with more complex objects.

Post a reply to this message

>> Uh - you can already do this can't you? just take out the "overlay" 
>> keyword
>> and it works!
>
>  No, because a later texture definition will not modify an existing one.

Didn't he want to add another texture over the top, not modify the existing 
one(s)?

Anyway, definitely weird that it only works for single objects, should be 
fixed to have the same behaviour with unions/merges etc.

Post a reply to this message

On Mon, 28 Jan 2008 10:10:40 +0100, "scott" <sco### [at] laptopcom> wrote:

>Didn't he want to add another texture over the top, not modify the existing 
>one(s)?

Yes, that's it exactly.

Post a reply to this message