Posted by E.Popov on June 01, 2000 at 14:10:09:
In reply to: To E. Popov posted by Bart on June 01, 2000 at 07:45:49:
> But for example the head-mesh contains a texture in texture tile #1 and in
> texture tile #7. Her foot does also. But Trviewer imports Texture tile 1 and
> 7 for her head and again for her foot.
Yes, that's the expected behaviour: when you import the head mesh, its textures are imported too. Then, when you import the foot mesh, its textures are imported also. The fact that it's the same textures as for a previous imported mesh is not known by TRViewer, so it imports the textures again. In fact, the feature lacking here is the moveable export: with it, you would have exported TR1 Lara moveable as a whole and then reimported it. And so, textures would have been correctly imported once.
Because it's the expected behaviour, it will not be "fixed". Instead, I'm currently working on an database object browser / editor that will let you export / import "base objects" of TR (sprites / animated textures / meshes / moveables / sound / ...). Because each mesh / moveable in this object database will have only its own texture fragments with it (as opposed to the whole tiles), it will only take the necessary room in the texture area when imported into a level, but no more.
E.Popov