Hi,
I'm still fighting against swap, just a quick Q.

Does a mesh2 object have the same memory-saving characteristics as a mesh
object, in that only one copy is stored?

Any help gratefully accepted.
-- 
Bill Hails

Post a reply to this message

In article <40659fbd@news.povray.org>,
 Bill Hails <bil### [at] europeyahoo-inccom> wrote:

> Does a mesh2 object have the same memory-saving characteristics as a mesh
> object, in that only one copy is stored?

Yes, the mesh2 "object" is simply an alternative syntax for the mesh 
object

-- 
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: <chr### [at] tagpovrayorg>
http://tag.povray.org/

Post a reply to this message

Christopher James Huff wrote:

> In article <40659fbd@news.povray.org>,
>  Bill Hails <bil### [at] europeyahoo-inccom> wrote:
> 
>> Does a mesh2 object have the same memory-saving characteristics as a mesh
>> object, in that only one copy is stored?
> 
> Yes, the mesh2 "object" is simply an alternative syntax for the mesh
> object
> 

Hmm, thanks, then I must be doing it wrong in some way.

I'm making a grass patch for a scene, much like
the famous "mgrass.pov" but using mesh2 so that
each blade has its own texture via a texture_list
section. The "patch" is a single mesh2 with 40 x 40
blades and eats a couple of dozen meg. But as soon as I
start making a hundred or so copies and doing no
more than Point_At_Trans and translate on them,
the povray process balloons from around 11% of
available memory to 100%, including all available
swap space.

It's quite obvious that it is making copies of the
entire mesh, is there anything I need to avoid
doing in order to stop the mesh2 being copied?

I'll keep on investigating.

-- 
Bill Hails

Post a reply to this message

Bill Hails wrote:


> It's quite obvious that it is making copies of the
> entire mesh, is there anything I need to avoid
> doing in order to stop the mesh2 being copied?
> 

After further investigation, I can answer my own
question here.

If I make the texture_list contain only a single
texture instead of one per leaf, and point all of
the face_indices for all the leaves at it, the
problem goes away.

I can live with that for my current needs, but
I'd suggest that it's a bug.

-- 
Bill Hails

Post a reply to this message