POV-Ray : Newsgroups : povray.unofficial.patches : Bug in ridgedmf and heteromf : Re: Bug in ridgedmf and heteromf Server Time
2 Sep 2024 06:18:32 EDT (-0400)
  Re: Bug in ridgedmf and heteromf  
From: Hans-Detlev Fink
Date: 26 Apr 2000 03:51:55
Message: <39069FEF.ADBF7469@pecos.nospam.de>
Thanks David. I suspected something like this already.
But then, what IS the correct syntax to apply a built-in
function as f(x,0,z)? I can't find a way to combine
f(x,y,z) with function{"foobar"...}. Do I have to
first #declare something?

TIA

-Hans-

david sharp wrote:
> 
> Hans-Detlev Fink <hdf### [at] pecosnospamde> wrote
> 
> > If those two fractals are intended to work as described in
> > the mega docs there are two bugs in each of them:
> >
> > The docs say they are f(x,0,z). Consequently the y component
> > should be set to zero: V1[X]=x;V1[Y]=0;V1[Z]=z; at the beginning
> > of the functions. And they should return (y-result) and (y-signal)
> > instead of just (result) and (signal), respectively.
> >
> > Or did I miss something?
> 
> After looking at the ridgedmf and heteromf  sections (I guess I never
> actually looked at them in 'published form' before), there are at least
> a couple of errors. It should not give the impression that the
> correct syntax is f(x,0,z). That syntax can be used  to enforce
> a height field like surface, but the multifractals can be used nicely
> for many other types of surfaces (clouds, planets, thingamablobs, etc)
> Another error in the docs is where the -H is supposed to
> be an exponent on f, not subtracted from f. (probably html superscript
> got lost somewhere)


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.