- Đã chỉnh sửa
Spine to Fiction Factory
Hello!
Im currently working on a game with a team that is new to Fiction Factory and Spine. It was discovered after some work was done in Spine that FF doesn't work with newer versions of Spine (i was using 3.5), only vs. 2.1.27. Is this a known issue? Is there a way we can patch our json to make it work? As it stands all of my animations will need to be scrapped so I can revert to an older version of spine and reanimate everything. Is this the only solution? Curious as if we could have a fix that'd be amazing.
I'm super new to Spine as well as FF. I'm getting in touch with FF as well to see if it can be an issue fix on their end. Any info would be really awesome! Thanks so much
Ideally FF updates to the latest Spine Runtimes. FF does a number of optimizations in their integration that are neat, but likely unnecessary. It would be simpler and easier to update to newer Spine Runtimes in the future if they simplified the integration, basically just rendering the vertices from the Spine Runtimes.
You can try exporting to JSON with 3.5, then importing into an older version of Spine. 2.1.27 is over 2 years old, so this may not work well. You can try the JsonRollback tool, explained here:
Spine editor and runtime version management
You may also be able to hand edit the JSON. The goal is to match the 2.1.27 JSON format so you can import it into 2.1.27. If you want to know how something looks in the 2.1.27 format, you can create it in 2.1.27 and export to JSON. If you used any newer features in 3.5: shear, paths, keying anything that didn't exist in 2.1.27, etc then you will need to either delete those sections from the JSON, or stop using those features before exporting from 3.5.
I tried opening a 3.5 version of a JSON in the 2.1 vs of Spine but it doesn't work, we just get error codes. The jsonrollback tool is great thank you! Hopefully FF will get up to date at some point...
Looks like our programmer was able to fix the jsons according to this, so thanks Thats a big help! And I'll be sure to make note of the version issue for the future.