even if  Statler doesn't want that explanation, I'd rather like it, as I'm
getting more and more interested in the internals of raytracing.

Thanks in advance (I'll thank you also after I read it, mind you, but it
will be in a long while, as I'm a little short on internet access right now
and I don't want to seem rude ;)

"Warp" <war### [at] tagpovrayorg> wrote in message
news:413465ea@news.povray.org...
>   Basically if you have this:
>
> #declare MyMesh = mesh2 { ... };
>
> object { MyMesh translate <1, 2, 3> }
> object { MyMesh translate <-1, -2, -3> }
> object { MyMesh translate <-4, 5, 6> }
> object { MyMesh translate <4, -5, -6> }
> object { MyMesh translate <1, -2, 3> }
>
> you will have 5 instances of the mesh in your scene, but POV-Ray will
> only have one instance of it in memory. That is, this scene only takes
> the memory needed for one instance of the mesh (and not five).
>
>   When POV-Ray is raytracing the scene, it will read the mesh data from
> this single mesh in memory for each instance you have in the scene
> (even though all the instances may be in different places and rotated
> and scaled differently).
>   (If you can't figure out how this is possible, it has to do with how
> POV-Ray manages transformations internally. I can explain that if you
> want.)
>
> -- 
> #macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb
x]
> [1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
> -1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// -
Warp -

Post a reply to this message