Yes, it does fix a bug.

In 3.1, if you attached a texture to a mesh and them moved the mesh, the
texture would not "move with the mesh", which means that the texture would
look like it was shifting on the mesh, because the mesh moved and the
texture didn't.  This occurs because each texture has its own set of
transformations, which are stored and computed separately from the object's
transformations.

Actually, the texture list in the mesh is not just a list of pointers, but
really is a set of complete textures.  This means that it has the potential
to require quite a bit memory in MegaPov (and 3.5) compared to the old 3.1.
But that is necesary to fix the bug.

-Nathan

"L'Harmonieux Forgeron" <jgr### [at] freefr> wrote in message
news:3C77665E.7C3A0186@free.fr...
> Hello,
>
> I was looking at the source code of some MegaPov 0.7 (one which include
the texture_list
> feature for triangle in mesh), I was wondering :
> why the textures array had been moved up from the mesh data into the
object data ?
> (Patch tagged NK 1998 / NK 1999)
>
> Is there a specific reason ? An unknown evolution plan ? does it correct a
bug ?
> It does not use much more memory  (because if I understood the code
correctly,
>  the texture array is duplicated with each copy of the mesh, whereas
previously it was
> not,
> and it's only an array of pointers to texture, not the real textures,
> and there is usually not a lot of different textures,
> but it keep me wondering...
> --
> Non Sine Numine
> http://grimbert.cjb.net/
>
>

Post a reply to this message