このサイトを正しく表示するには、最新のブラウザを使用し、Javascriptを有効化してください。

Updating Spine and the Spine Unity Packages

acai

Hi, I have a few questions regarding updating Spine.
I just saw a bunch of changes in the Changelog on the start screen, and it looks like version 4.2.33 is out.

Question 1:
How can I update Spine? My current version is 4.2.14. I clicked the "Latest stable" button, but it doesn't seem to do anything.

Question 2:
If I update Spine, do I also need to update the Spine packages in Unity?
Or should I go to the Package Manager and update the Spine packages regardless of whether I've updated Spine or not?

Question 3:
Is this the correct page to get the latest Spine Unity package? https://esotericsoftware.com/spine-unity-download#Updating-an-existing-project

Question 4:
I read somewhere that after updating the Spine Unity package, I need to export all the Spine animations again to Unity. Is this true? (If it is, this is a major concern because I have a lot of animations.)

Question 5:
How often do you usually update? What's the average update cycle? If question #4 is true, I'd like to know how many times I might need to export all my animations while developing my game.

Thank you for reading my post. I just want to understand what to expect when using Spine for development.

Spinebot

Question 1:
To update Spine from version 4.2.14 to 4.2.33, you should be able to click the "Latest stable" button. If it doesn't work, you might need to manually download the latest version from the Spine website.

Question 2:
Yes, if you update Spine, you should also update the Spine packages in Unity to ensure compatibility. The Spine editor and runtime versions need to be synchronized. You can find more information on synchronizing versions here.

Question 3:
Yes, that is the correct page to get the latest Spine Unity package: Spine Unity Download.

Question 4:
Yes, after updating the Spine Unity package, you need to re-export all your Spine animations to Unity. This is necessary because the JSON and binary skeleton data files exported from Spine 4.1 or earlier will not be readable by the spine-unity 4.2 runtime. Automating the export process can help manage this task more efficiently. You can find a script for automating exports here.

Question 5:
Spine updates are released regularly, but the frequency can vary. It's important to stay updated with the changelog and plan your updates accordingly. If re-exporting animations is a concern, consider setting up automated export scripts to streamline the process.

acai

I'm exporting using .skel.bytes. Do I still need to export everything again?
Also, could you explain how to use the 'Automating the Export' script?

Misaki

acai Spinebot seems to have overlooked that the version update you are referring to is a patch version update. You do not need to update the runtime if you are only updating the patch version of the editor. The runtime should be updated together with the major or minor version update, e.g. update from 4.2 to 4.3.

Even if you don't need to just update the version, it is very beneficial to use scripts to automate the export process. Please see the following blog post for more details on that: Blog: New export shell scripts

acai

Thank you so much, Misaki! That's a relief. 😃
I'll take a close look at the link.