Цей сайт найкраще переглядати в сучасному браузері з включеним JavaScript.

How to calculate UV when use Strip whitespace export option

megafiers

use spine-c

spine export option "strip whitespace" option make size and orig size not the same para

but uvs in attachment still in original size coordinate system, this differ will cause texture mapping error.

get uvs

spMeshAttachment* attachment = (spMeshAttachment*)slot->attachment;
spMeshAttachment_computeWorldVertices(attachment, slot, worldVertices);
uvs = attachment->uvs;

Mario

Are you trying to write your own attachment loader/renderer? Check out spine-runtimes/RegionAttachment.c at master (spRegionAttachment_setUVs and spRegionAttachment_updateOffset) which compensate for the whitespace stripping and rotation of a region in the atlas.

Pharan

He's asking about MeshAttachment.

offsetting those for MeshAttachments would cause the UVs to bleed into other images in the packed texture, or outside of the packed texture.
This is why we recommend not using Strip Whitespace when using meshes, and instead pre-trim them before using them in Spine. Texture Packing - Spine User Guide: Regions

megafiers

Pharan написав
He's asking about MeshAttachment.

offsetting those for MeshAttachments would cause the UVs to bleed into other images in the packed texture, or outside of the packed texture.
This is why we recommend not using Strip Whitespace when using meshes, and instead pre-trim them before using them in Spine. http://esotericsoftware.com/spine-texture-packer#Regions

tks for answer.

so no other way to fix the uv calculation?

Pharan

I think you can check this guy's calculations. Patch for trimmed atlas meshes in c-sharp/unity.
Again, even if you correct the UVs, you'll probably see bits of images where you don't want them to be precisely because of whitespace stripping.