.json export missing skeleton transform information

PPhyre · 28 мар 2023

Hello! Bit of a niche discovery as no one on our team has been able to parse why this is happening just that we are fairly certain it is a problem within spine or while exporting.

Our problem is that one of our files upon export from spine is missing x/y and width/height data in the .json. So when we go to import into our engine there is no set scale for the animation to be seen. We can manually input a height/width etc into the .json as a bandaid fix but any new exports do not retain that information (as we expected).

This is what the .json file looks like upon export (in Visual Studio) and the expected behavior(in Notepad/images):

We have tried to narrow it down to what may be causing this but ultimately that has led to dead ends. Our best guess is something funky was done to the skeleton or we have corrupted the file somehow. Let me know if anyone may have any leads as to why this could be happening, thank you!

Misaki · 28 мар 2023

Phyre Sorry for the trouble. If you don't mind, could you please send us your Spine project via email?: contact@esotericsoftware.com
If the problem can be reproduced without images, you can send only the Spine project to us. Please briefly mention this forum thread URL in the email so that we know the context. Then we can have a look at what's going wrong.

Misaki · 29 мар 2023

Phyre Thank you for sending us your Spine project! Your skeleton does not seem to show any attachments in its setup pose, so it is the expected behavior that the x, y, width, and height of the skeleton have not been written in the exported JSON file. Because these are determined based on the AABB for the skeleton's attachments in the setup pose. You mentioned that your skeleton would not display correctly at runtime in this JSON file, but as far as I could tell from a quick test with the spine-unity runtime and Spineboy, it can be displayed correctly, even though it did not show any attachments in its setup pose, so the lack of those information in the JSON file itself should not be a problem. Could you describe how your skeleton is implemented in your project?