|
![](/i/fill.gif) |
Stepping above my area of expertise:
Wasn't the idea that instead of using an interval of 0 to 1, it went from
-0.5 to 0.5?
Nathan Kopp wrote:
> Ron Parker <ron### [at] povray org> wrote...
> > On Fri, 4 Feb 2000 12:50:49 -0500, Nathan Kopp wrote:
> > >This has been discussed in the past (with no resolution found). The
> problem
> > >is that POV's Noise() function is not "correct". A solution has been
> > >proposed which would, unfortunately, not be completely backwards
> compatible.
> > >My personal preference would be to provide an option to allow backwards
> > >compatibility but by default use a "correct" Noise().
> >
> > Why does noise3d() clamp? Is there some reason it should?
>
> The big problem is that it doesn't clamp correctly. Or, rather, it doesn't
> scale the output properly before it clamps. Honestly, I don't think it
> really is that necessary that it clamps, either.
>
> -Nathan
Post a reply to this message
|
![](/i/fill.gif) |