binary export not generating SkeletonData asset

Nick

I was re-exporting some old file when upgrading to v4 runtime. Export name is already named "*.skel.bytes" but still not getting SkeletonData asset. No error message. However, the same export but in json will works. Don't know why.

Both binary/json export files:
BinExportNotWorking.7z

the sample project from below can also reproduce this issue:

http://esotericsoftware.com/forum/exported-images-are-corrupted-in-latest-beta-15489

Nate

Thanks for the report. Turns out the binary data is good, this was a problem in the runtimes. We've now fixed it in spine-unity, spine-libgdx, and spine-ts in the 4.0-beta branch. :beer:

Nick

Excellent!

Harald

An updated 4.0-beta unitypackage containing the bugfix has just been released, you can download it here as usual:
Spine Unity Download: Download

Nick

FYI, while the SkeletonData do generate now. It doesn't parse correctly. On the other hand JSON export still works.

P.S. v4 Unity runtime from Mar-04 and 4.0.59 beta editor.

Failed to read version info at skeleton 'TapHintHand.skel'. It is likely not a valid Spine SkeletonData file.
System.FormatException: Input string was not in a correct format.
  at System.Number.StringToNumber (System.String str, System.Globalization.NumberStyles options, System.Number+NumberBuffer& number, System.Globalization.NumberFormatInfo info, System.Boolean parseDecimal) [0x00057] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Number.ParseInt32 (System.String s, System.Globalization.NumberStyles style, System.Globalization.NumberFormatInfo info) [0x00013] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Int32.Parse (System.String s, System.IFormatProvider provider) [0x00008] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at Spine.Unity.SkeletonDataCompatibility.GetVersionInfo (UnityEngine.TextAsset asset) [0x001bd] in D:\git_repo\UnityProject\Assets\AddOns\Spine\Runtime\spine-unity\Asset Types\SkeletonDataCompatibility.cs:133

looks like data around version number is incorrect in binary mode.

Harald

Unfortunately we could not reproduce your problem. When exporting some test projects from 4.0.59-beta it imported without any issues using spine-unity-4.0-2021-03-04-beta.unitypackage from the download page. Are you sure that you are using this 4.0-beta spine-unity unitypackage and not accidentally an older one?

If all versions are recent, could you please send us one of your problematic exported .skel.bytes files, either attached to a forum posting or to contact@esotericsoftware.com? Then we can have a look at it.

Nick

That's weird. Could that be there are some data cached in the binary parsing routine? Coz I was exporting from editor for both json and binary export alternatively. I do have clear the export folder during the test. Anyway, I couldn't reproduce it now. Will let you know if I get this again. Thanks

Harald

Thanks for taking the time to test it again, we will gladly fix it if it re-occurs.

Nick

I finally found the cause. I am exporting in batch with script and a few export.json has setting to export json but write file name as skel.bytes extension. When I test again in editor, it works because it no longer use export.json. Thats why I could not reproduce it before. It is not the version number is wrong but the parser try to parse the json as binary. Is the file header don't have the first few bytes used to identify if it is really a spine binary file? It would be better if the runtime can differentiate a total parse failure and a real wrong version binary format.

Nate

The binary format doesn't have a magic number at the start. Maybe if parsing fails, we could read the first X bytes of the file and if it's all ASCII, the error could mention that it appears to be textual. What do you think, Harald?

Harald

We could add this for spine-unity and perform the check in the Editor when the game is not playing. This way it would not waste any loading time in the game itself.

I have created a ticket here: https://github.com/EsotericSoftware/spine-runtimes/issues/1857