@jhuna11003 Thank you for sending the skeleton data files. I have now identified the cause of the issue.
Since the data you provided included several similarly named files, the confusion is understandable. The skeleton requires a texture atlas page named “Merry.png” (with an uppercase “M”). That file is not included in the set you sent, which is why the skeleton’s appearance cannot be restored.
In other words, the correct skeleton data set should consist of:
- Merry.skel
- Merry.atlas.txt
- Merry.png ←This file is missing.
In the video you shared, the texture atlas page “merry.png” was unpacked using “Merry.atlas.” However, the contents of “Merry.atlas” and “Merry.atlas.txt” are completely different.
Moreover, the image paths referenced by each attachment in the imported “Merry.skel” clearly match the regions defined in “Merry.atlas.txt.”
Because the filenames are so similar, this is understandably confusing. To clarify:
- Merry.atlas defines regions for merry.png. The attachments contained in this atlas page are not referenced by the skeleton data (Merry.skel).
- Merry.atlas.txt defines regions for Merry.png. This is the atlas that corresponds to the attachments referenced by the skeleton data (Merry.skel).
As an additional clue, according to the information in Merry.atlas.txt, Merry.png should be an image measuring 1778 × 523 pixels.
By contrast, merry.png is 1684 × 1032 pixels, which confirms that a different image file must exist.
Therefore, you will need to locate “Merry.png.” Without that file, the skeleton cannot display correctly.
I am not sure how your files are organized on your side, so I cannot estimate how difficult this may be, but I hope this clarification helps you track down the missing PNG file.
