Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

version 2.0.00 binary export issue

timotron

If anyone else noticed...

The hash string and the version string have been flipped in the binary file.

Normally repositioning such entries would not be an issue, except that version was moved from first to the second string in the spine binary export file.

Which means that all old exported binary files no long load, and the there is no clean way to check the version to correctly load.

I have hacked around this by inspecting the first string to check if it looks like the version and then either push it to the hash string or load the hash string so that I can still load old binary spine file exports.

In short... Can we please not randomly change exported binary code so that the version info is repositioned like this in the future?

Tim :bang:

timotron

Nate

Sorry about that! I wanted the hash to be first so it could be checked before bothering to read anything else. I meant to make the change sooner, but the 2.0 release took longer than expected. I did not expect anyone to be using the hash and version strings yet.

Old binary files should still load, since the fields that were swapped are both strings. I guess you do something if you read a particular Spine version?

Note that the binary format is very brittle, almost any change to the format will require all your skeletons to be exported again.

timotron

Thanks for the reply.

The binary version is no longer that "brittle" now that you write the version in the file. With that I have been able to keep my importer for the binary file up to date and able to handle any changes since it has been added (mostly the IK stuff so far).

Note: You could probably do the same in your code base as well 😉

Tim

Nate

Ah I see. Yeah doing that is an option, but I think it is cleaner to not try to support previously exported data. Exporting the data again is pretty reasonable (will be even easier when there is command line support...).