the object-material connection

#1 Yes, the materials will be defined in the dts, and script will use a singleton datablock to define the location of the texture files. One way to get the names of the textures used in the dts (aside from looking at them in Milkshape or similar program) is to use %player.getMeshVisibility();

#2 Thanks. But i did not found getMeshVisibility() ...

#3 Oops, sorry. GetMeshVisibility() isn't a stock T3D function. Use dumpMeshVisibility();

#4 It works, thanks. The other way to get the assigned materials and textures can be:

function getMatInfo(%objID)
{
   %numSurfaces = %objID.getTargetCount();
   for (%i=0; %i<%numSurfaces; %i++)
   {
      %surface = %objID.getTargetName(%i);
      %material = getMaterialMapping(%surface);
      
      %diffuseMap = %material.diffuseMap[0];
      %normalMap = %material.normalMap[0];
      %specularMap = %material.specularMap[0];
   }
}

I think, the problem is the line "%material = getMaterialMapping(%surface);" because it sounds to me, that the used names of the surfaces have to be unique in the game and not only in the mesh itself.

#5 Can anyone confirm that?

#6 Yes, material mapping is global. This is a somewhat borked aspect of the system. mapTo really isn't the best of ideas.