I work in a small company that uses Spine software and Spine runtime provided in the cocos2d-x that we utilize.
All Spine files (json, atlas, png) in our app have been prepared using Spine 2.1.27. From the app perspective, we have been using Spine runtime 2.3, till now. Recently we decided to update the cocos2d-x engine and that update introduces an upgrade of old Spine runtime from 2.3 to 3.5.35.
Unfortunately, after the upgrade of the Spine runtime, creating a skeleton objects crashes the app. The Spine object is not able to read Skeleton data - spSkeletonJson_readSkeletonDataFile
returns NULL
.
I was trying to import the JSON file in Spine software 3.6.48 to re-export it, but the Spine 3.6 can't import it.
So my questions are:
- Is it possible to convert Spine files (json, atlas, png) to make them support the latest Spine?
- Was there a backward non-compatible Spine upgrade somewhere between 2.3 and 3.5?
- What's are best practices for working with Spine files? The idea of recreating all Spine files on every non-compatible backward Spine upgrades doesn't seem to be rational.
Thanks in advance for any hints.