View Single Post
Old 04-22-07, 08:02 AM   #30
UBOAT234
Weps
 
Join Date: Oct 2005
Location: Repubblica di San Marino (Italy)
Posts: 362
Downloads: 0
Uploads: 0
Default TMAP

Some information for TMAP, I think the big problem for rework unit.

To store information on texture maps EI uses a TMAP chunk. TMAP chunks are associated with an object. An object has one TMAP chunk for every texture that is applied to it. This chunk contains information about the texture image such as the dimensions of the bitmap image (this can be troublesome for the exporter as it simply cannot reference a texture map and output its name; rather, it must load the image header for the file from disk to determine its dimensions so that the exporter can store that information in the TMAP chunk). The TMAP chunk also stores the type of projection to use when it is being mapped onto the object. This seems like a very strange thing. Another chunk (TMEI) stores information on what the projection looks like but doesn't store the type of projection it represents! This is why the TMAP appears before the TMEI in the file. The TMAP chunk also includes information about the images bounding box.

If you do not import this chunk, you must delete the secondary image stored in folder unit: O01 and N01, but it work without MIPMAP render.
Is not the best solution

BEST REGARDS
UBOAT234
UBOAT234 is offline   Reply With Quote