"Dave Dunn" <poi### [at] aolcom> wrote in message
news:3BA### [at] aolcom...
> Batronyx wrote:
>
> > Pentium II 266, 96MB, Windows98 SE, POV3.5b2
> > Problem in pigment_pattern with bozo/f_noise3d:
> >
> > When using bozo as the pattern type in a pigment_pattern
> > the results are 'extremely' plateaued. So far, random tests with
> > other pattern types produce the expected behaviour however.
>
> Bat, Long time.... Try using "pattern" instead of "pigment" and the bozo
> will smooth right out  : )
>

So you ARE that Dave Dunn. :D  Long time indeed.
You are correct. It does. However, it depends on how and where you use it:

I can't see where I would really ever 'just have to' use pigment_pattern
in a function. The third sphere in the code sample, though, shows where
I might need pigment_pattern in general though.

Very often I have a texture but would like to vary the finish attributes
across the surface for that extra touch of realism. Layered textures won't do
since only the finish of the topmost texture is used, and no form of mapping
syntax is supported for finishes in general ( the new variable reflection
being an exception - sort of).

Prior to the new pigment_pattern and/or image_pattern types, my only choice
was to create a material_map and/or pigment_map with 256 ( just two won't
do since they're taken modulo N [for material_maps anyway])texture entries
that vary only in finish. That's a lot of memory overhead. Now I 'can' get by
with as few as two textures since the new types interpolate. :)

Besides, <gleeful_clapping> It's still a bug. I found it. I got to help
</gleeful_clapping>, maybe. :D
--
Batronyx ^"^
bat### [at] cadronhsacom
http://www.batronyx.com

Post a reply to this message