Ah, thanks - I'd been playing with the functions to see what the effect was
so that's probably where the x,z,y came from.

I didn't think it was a bug exactly, I thought I was doing something wrong
;-)

How would we isolate the bug?

I was wrong about the news link, it's
news:news.povray.org/povray.binaries.animations, "Rot and Renewal".  And now
that I check it, I had the x,z,y *lol*.  Back to the IDE ..

      == John ==



"Bob H." <omn### [at] msncom> wrote in message
news:3b489d64@news.povray.org...
> "John D. Gwinner" <jgw### [at] hotmailcom> wrote in message
> news:3b488a38$1@news.povray.org...
> >
> > Maybe I'm doing something wrong, but actually, y+WrinklesFunc doesn't
> work -
> > it's basically what I tried before (I used y-).  It looks fine as a
single
> > frame, but when you animate it the surface goes down.  I'm posting the
> > animation in news:news.povray.org/povray.animations
>
> Yep, that's curious.  It isn't due to turbulence being used anyway,
checked
> on that.
>
> Using just the regular color_map as before it undulates up and down.  It
is
> as if phase effects the color_map or isosurface (or function) in a
> unexpected way, as you described.
> Although shifting the color_map as it goes might seem a solution I think
it
> more a bug rather than something to work around.  Maybe someone has more
> ideas on this, like whether the behavior is correct or not?  Could it even
> be related to the noise clipping?
>
> Btw, the last sample of script had the function x,y,z written as x,z,y
this
> time so I put it back to x,y,z.
>
> Bob H.
>
>

Post a reply to this message