Nate No, it is a one off tool for moving JSON data from 3.4 to 3.3. It is not an officially supported workflow. It is better to properly manage your Spine versions so you don't need to rollback your data. 🙂
ccyy__ I USED Skeleton Viewer to export,but the version was still not changed.Actually, I want the version 3.6 to the version 3.4, butresult it's still the version 3.6. And cloud u tell how use the Skeleton Viewer? tips: I use the check Nonessential data.
tangwen how that the new runtime use an old exported json file. eg: runtime3.8 to use spine2.1 exported by editor? I'am using spine-cocos2dx and this update keeps crash at the json parse
Nate @tangwen That isn't possible. You must run Spine 2.1.xx, import the data, save a Spine project file, run Spine 3.8.xx, and export so you get 3.8 skeleton data that can be used with the 3.8 runtimes.
