sorting out the mhstx feature

[robertltux]

okay since it seems that nobody has written any docs on it im going to ask some questions

the feature revolves around
1 a base texture
2 N "overlay" textures
3 the mhstx file

the format seems to be fairly simple
[
{ 'txt': 'dollvio-left.png', 'dst': (470, 1783) },
{ 'txt': 'dollvio-right.png', 'dst': (1803, 1546) }
]

giving us N lines (one for each overlay texture) with 4 fields the second and fourth field seem to be the biggest concern

each line has the overlay file as the second field and then the fourth seem to be coordinates in some sort of grid (a standard MH skin is 2048X2048)

my big question is what on the overlay should map to the given cords (and which way is the counting??)

do we count from the lower left , upper right or?? and is the given cord pair the center , upper left , lower right or?? of the overlay??

also is there a limit as to how many overlays can be in the file??

[mflerackers]

The format is standard python, and it's a list of dictionaries. The dictionary defines one sub layer, each layer has a texture (txt) and a destination (dst) into the big texture. The coordinates are just pixels like you would place it in gimp or photoshop into the skin file.

[robertltux]

The format is standard python, and it's a list of dictionaries. The dictionary defines one sub layer, each layer has a texture (txt) and a destination (dst) into the big texture. The coordinates are just pixels like you would place it in gimp or photoshop into the skin file.

great answer now for the details im looking for
1 Where is the Zero Point for the grid?? (gimp has zero on the upper left)
2 on the overlay what is the point given?? (are we just matching the zero pixels of both images??)


and can i assume that we could have a file with a dozen overlays??

[mflerackers]

Like I said, it's image pixels, so of course left top is 0, 0. And yes you can have as many files as you want in one sub texture file, but it constitutes one layer in the texture eventually.

[ThomasL]

Is it possible to save the modified image to disk? I tried with the Image.save() function. It does save a big tif file, but unfortunately all programs I have say that the file is corrupt.

[mflerackers]

It is always saved as tga at the moment, so be sure to give it that extension.

[ThomasL]

OK, now I can save a texture and import it into Blender. But the eyes are always brown. Is there some way to get hold of the modified image? Or a list of subimages, so I can blit myself.

[mflerackers]

Actually it is currently only written to the OpenGL texture, not the disk. You can add this in 3_libraries_eye_chooser.py in setEyes, after texture.loadSubImage(img, 0, 0). The plan is to move the layer code to a more general place (Human?), since we won't have only eyes, but I didn't have time to do it yet. Once there are other sub textures besides eyes, we need to keep track of the layers, like we do for clothes etc, so when for example a tattoo is added, the eyes are not erased.

[ThomasL]

So, can I get hold of the OpenGL texture? It should already be loaded into memory.

[mflerackers]

The data is already in img, which is copied to the texture:

texture.loadSubImage(img, 0, 0)

so just add

img.save("file.tga")