POV-Ray : Newsgroups : povray.bugreports : Two mesh bugs found in povwin 3.1g : Re: Two mesh bugs found in povwin 3.1g Server Time
28 May 2024 18:55:07 EDT (-0400)
  Re: Two mesh bugs found in povwin 3.1g  
From: John VanSickle
Date: 11 Aug 1999 22:26:26
Message: <37B233D6.7D286C9A@erols.com>
Steven Jones wrote:
> 
> I've found a way around both bugs.  For the crash bug, don't leave it
> up to Pov to define a colour map, do it yourself, even if it's the
> same as the default colour map.

Well, yeah, but it's still a bug.

> For the other one, declare your mesh as a macro and then invoke the
> macro inside an object statement.

Re-declaring the mesh (which is all that your procedure would use)
defeats one of the primary reasons for using the mesh:  Memory savings.
I have a model made of 21 mesh objects, for a total of 30,336 triangles.
If I had re-declared each mesh, each of these models uses 4.5 megs of
memory.  If I copy the meshes, each model uses about 32K or so.

Regards,
John


Post a reply to this message

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