Facing import issues in version 4.0 and 3.8

eddy

In version 3.8 and 4.0 i import a animation file (Json and animation project) into another spine file. Then, I faced some missing mesh related issues. But in version 4.2 there was no problem, it was buttery smooth. So why was it happening in those versions?

Misaki

eddy Unfortunately, due to differences in terminology, I was unable to understand exactly what you did. You mentioned “Json and animation project,” but I think you are referring to the skeleton data file exported in the JSON format. Is the “animation project” you mentioned a Spine project (.spine file)? Also, which version was the original file created in, and which version are you attempting to open it with?

Spinebot

In versions 3.8 and 4.0, you may encounter issues with missing meshes when importing animation files due to differences in how data is handled between these versions. Specifically, when exporting JSON from a newer version like 4.0 to an older version, you might lose certain data such as Bezier curves because of incompatibilities in how these are stored. Additionally, ensuring that the images path is correctly set after import can resolve issues with missing images. In contrast, version 4.2 has received numerous bug fixes and improvements, which likely accounts for the smoother import experience you observed.

eddy

First, I created some spine animations into seperated files using ver 3.8 and when I import those files using import data (json) into one spine file(ver 3.8), the bones' positions automatically changed and some meshes weren't visible. This problem happened in 4.0 also. But interestingly, when I converted those file from ver 3.8 to 4.2 and imported as same way into one file( ver 4.2). It was perfect and clean.

Nate

It's hard to say. We fix hundreds of bugs or more in each version, likely if it works better in 4.2 it's because bugs were fixed in the newer version.