Hi,
I just discovered that my current project ( which I hadn't touched for a while) does not work with files exported from Spine 3.
I modified the code of the runtime a bit, and it's probably not totally trivial for me to update the runtime right now. I rather use an old version of Spine for this project.
I have an automated build set up that exports many .spine files to atlases+json files.
Looks like that this batch process now (using Spine 3) produces files that are not compatible with the old runtime code
When I switch Spine back to a 2.xxx version, it works.
Here's my question(s):
1.) Can I tell spine via command line to use a specific version (only) when exporting? ( Something like "
use-version 2.1.xxxx") .
2.) Where is the "currently used version" stored? (<
This is more a general question about how Spine uses different versions in parallel on the same machine).
I think that this might be interesting for other ppl: Imagine a build server which needs to build different projects with source files built with a different version of Spine.