Just what is happening here?  That is, I wonder why the converted range will
be 0-.5 not 0-1.  When I did my Bozo tutorial waaaaaay back when (I think
it's on the first POV CD), it appeared that there were spots with values at
both 0 and 1, and I thought it was symetric -- both colored spots were the
same size.

Ah, the new Bozo range is .25-.75, so the end value is stretched to fit.
So, in the old formula, that was happening too?  Meaning my spots were too
big and not fuzzy, right?

Anyway, it looks like dividing by 2 on the Granite and changing filter to
transmit everywhere (Stone9 uses T_Crack1 also) gave me the same spirit as
the original.  Thanks!

So... what's the "layered texture change" you refered to in your earlier
note?

--John

"Nathan Kopp" <nat### [at] koppcom> wrote in message
news:3ab047cb$1@news.povray.org...
>
> "Mark Wagner" <mar### [at] gtenet> wrote g...
> > To port color_maps/pigment_maps/whatever_maps from the old (clipped)
> noise3D
> > to the new (scaled) version, divide all map indices by 2 and add 0.25.
> For
>
> This formula works for bozo, which is a direct use of noise.  However,
> granite uses multiple iterations of noise, so this doesn't work.  However,
> you can get very close results by simply dividing all indices by 2 and NOT
> adding the 0.25.
>
> For granite, the converted example should look like this:
> color_map{
>     [.1 rgb 1]
>     [.25  rgb <1,1,0>]
>     [.35  rgb <0,0,1>]
> }
>
> I tested this and it works great for T_Grnt9.
>
> Also, make sure to convert rgbf to rgbt if layered textures with filter
are
> being used (not necessary for T_Grnt9).
>
> -Nathan
>
> > example,
> >
> > color_map{
> >     [.2 rgb 1]
> >     [.5 rgb <1,1,0>]
> >     [.7 rgb <0,0,1>]
> > }
> >
> > becomes
> >
> > color_map{
> >     [.35 rgb 1]
> >     [.5  rgb <1,1,0>]
> >     [.6  rgb <0,0,1>]
> > }
>
>
>

Post a reply to this message