|
![](/i/fill.gif) |
Remco de Korte schrieb in Nachricht <3A7A893D.1E61F9DA@xs4all.nl>...
>I may use this in a larger scene (animated) so I'm sure I'll optimize it a
bit
>in that case, but I'm also considering using heightfields.
>
I don't know for sure, but does the new pattern image type work with
function-pigments? If so, you could generate the heightfields for the
animation "on the fly" with the formulas you have here. Should be faster
than an isosurface, shouldn't it?
Marc-Hendrik
Post a reply to this message
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
Marc-Hendrik Bremer wrote:
>
> Remco de Korte schrieb in Nachricht <3A7A893D.1E61F9DA@xs4all.nl>...
>
> >I may use this in a larger scene (animated) so I'm sure I'll optimize it a
> bit
> >in that case, but I'm also considering using heightfields.
> >
>
> I don't know for sure, but does the new pattern image type work with
> function-pigments? If so, you could generate the heightfields for the
> animation "on the fly" with the formulas you have here. Should be faster
> than an isosurface, shouldn't it?
>
> Marc-Hendrik
If I use heightfields I'll generate them with an external program. That'll take
only seconds.
Remco
Post a reply to this message
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
Oopsie!
I accidentally posted the wrong isosurface from the wrong source. I just noticed
it now when I wanted to use it.
Here is the original (non optimized) code:
isosurface{
function{
y*(1
+sin(x+z+sin(x)-clock*pi/8)
*sin((x+z+cos(x)-clock*pi/8)*2)/2
+sin(x*.75+z*.5+sin(x)-clock*pi/16)/4
)
*5
+noise3d(x+z,y*2,z)/2
}
threshold 1 sign 1
bounded_by{ box{<-20,-12,-20><20,12,40>} }
pigment{rgbt<.2,.7,1,.5>}
// pigment{rgb 1}
finish{phong .7 phong_size 120
reflection .5
brilliance 4
}
}
Sorry,
Remco
Post a reply to this message
|
![](/i/fill.gif) |