"Alun" <tho### [at] lineonenet> wrote in message
news:web.3f5f2d3e6dc97f052667dc700@news.povray.org...

<snip>

Weird - very much looks like a bug.

You can 'fix' it by adding "translate y*1/750" to the hills (oddly, translating
the mountains up by 1/750 doesn't fix the problem - it creates a slightly
different one).

The problem only seems to occur when you render the iso - by this I mean that if
you declare both isos as objects, you then have to use both objects in the
scene.

Here's the scene I played with (just the modified bits):

#declare mountain_octaves=12;
#declare hills_octaves=4;     // Try changing this to 4 ...

#declare IS1 =
isosurface {
  function { 2+y - f_hetero_mf(0.2+x,0,z, 0.9, 1.7, mountain_octaves, 0.5,0.9,
3 ) }
  contained_by { sphere {0 1} }
  evaluate 5, 1.2, 0.95
  pigment { rgb <0.7,0.8,0.9> }
  translate x*1.2
}

//

#declare IS2 =
isosurface {
  function { 2+y - f_hetero_mf(0.2+x,0,z, 0.9, 1.7, hills_octaves, 0.5,
0.9,3 ) }
  contained_by { sphere {0 1} }
  evaluate 5, 1.2, 0.95
  pigment { rgb <0.5,0.8,0.6> }
  translate -x*1.2
}

object{IS1}
object{IS2 translate -y*1/750} //this is okay!

Post a reply to this message