earlysetr.blogg.se - Spine numbers

#SPINE NUMBERS UPDATE#
#SPINE NUMBERS ARCHIVE#
#SPINE NUMBERS PATCH#

It's not as easy to update to a newer Spine Runtimes version, as the new version needs to be downloaded, the old version replaced, and possibly code fixed up. Otherwise, it can be easy to accidentally update to a newer Spine editor version.ĭevelopers must make sure to use the right version of the Spine Runtimes. This dependency is very important.Īnimators must make sure to use the right version of the Spine editor by choosing a specific version. If not, the Spine Runtimes will not be able to read the data. The major and minor version for the Spine editor used to export JSON or binary data must always match the Spine Runtimes version. and type the version number for any version we've ever released. All versions you have downloaded are shown, or you can click Other. You can also choose a specific Spine editor version.

You won't see the Latest beta option if there is currently no beta in progress. Beta versions let you try the latest new features, but exports may not yet be supported for all Spine Runtimes. If you choose Latest beta, it will run the newest Spine editor beta. If you choose Latest stable in the version select box, it will run the newest stable, production ready release of the Spine editor. In that case, to stop Spine from starting automatically, just click anywhere when the launcher window first appears. If the launcher doesn't stop to let you choose a version, it's because you've previously checked Start automatically. You can also set the Spine editor version on the settings dialog. When Spine starts, the launcher window allows choosing which version of the Spine editor to use. Once out of beta, the beta Git branch for the Spine Runtimes is removed and replaced with a stable version number. Each runtime's README on GitHub specifies the most recent Spine version it works with. Some runtimes will be updated before others and we don't do a stable release until all runtimes are updated.

You know the runtime you are using has already been updated to work with the beta editor version.

You can always go back to a stable or older Spine editor version, just be careful not to save your projects with the newer version.

You want to explore the newest Spine features.

You want to use the newest Spine features and don't mind waiting until the runtimes have been updated.

You are exporting images or video, so lacking runtime support doesn't matter to you.

Here are a few reasons you may want to use a beta release: Also, exports from a beta version may not yet be supported by all Spine Runtimes. For example, 4.0.73-beta for the Spine editor and 4.0-beta for the Spine Runtimes.īeta versions let you use the latest new features, but the Spine editor may crash occasionally or have features that are not completely implemented. Beta releasesĪ beta release is any that ends with -beta. Updates to stable releases are mainly to fix bugs. We don't make risky changes to stable releases in order to reduce the chance that new problems are introduced. For example, 3.8.99 for the Spine editor and 3.8 for the Spine Runtimes.

#SPINE NUMBERS PATCH#

Git commits to a branch are used instead of patch version numbers.Ī stable release is any that doesn't end with -beta. Git branches are used for each version of the Spine Runtimes.

The source code for the Spine Runtimes is provided in the Spine Runtimes GitHub repository. The Spine Runtimes version numbers use the format major.minor.

#SPINE NUMBERS ARCHIVE#

The changelog archive provides a list of all Spine editor versions we have ever released. When only the patch version number changes, it means that we have fixed bugs or have done minor improvements and it is safe for you to update. When the major or minor version numbers change, it indicates a significant difference and caution should be used before updating to the newer version. Spine editor version numbers use the format. Keeping track of your Spine editor and Spine Runtimes versions is an important part to using Spine.