I implemented myself Perlin noise and got the same bug. Double/triple check 
the way you interpolate the values on non grid points: the code of the 
s's/t's (or whatever you call the interpolation fractions) is handled 
exactly the opposite on might resonably think (I consider Perlin noise code 
one of the most counterintuive algorithms I have ever implemented/debugged).

By the way, if POV had been a free software project, handled with CVS I 
would have fixed the bug more than one month ago...

Bye

-- 
Alessandro Coppo
a.coppo@<REMOVE_ME>iol.it
www.geocities.com/alexcoppo

Post a reply to this message