I can't baked all the animations because I get the error sho

Iirask2 · 2022年10月26日

Unity: 2020.2.0f1

• Spine for Unity version: 3.8

• Used asset: Animated 2D Monsters (Fantazia) from Wurrad

• Problem: I can't baked all the animations because I get the error shown in the screenshot.

I wanted to baked out all the animations from the above-mentioned package, which requires Spine version 3.8 and while burning some animations is not a problem, the rest throws the error visible in the screenshot. I am not a developer so I cannot fix the bug.

Do any of you know how to tackle this topic? How do I fix this so I can burn out the rest of the animation

Harald · 2022年10月28日

Which exact version of the spine-unity 3.8 runtime are you using (name of the unitypackage, also listed in Assets/Spine/version.txt)?

Please note that spine-unity 3.8 is pretty old already and we've included many bugfixes since then on spine-unity 4.1, so if upgrading your Spine projects is an option, we would recommend you to do so. Also note that baking animations instead of using SkeletonAnimation or SkeletonMecanim components is not recommended and should be avoided where possible.

Iirask2 · 2022年10月28日

This is my version of Spine:
"This Spine-Unity runtime works with data exported from Spine Editor version: 3.8.xx
Package version: spine-unity-3.8-2021-11-10.unitypackage"

I am using version 3.8 because the author of the asset I am using required this version.

Why is baked animation not recommended?

Harald · 2022年10月31日

irask2 wrote
This is my version of Spine:
"This Spine-Unity runtime works with data exported from Spine Editor version: 3.8.xx
Package version: spine-unity-3.8-2021-11-10.unitypackage"

Thanks for the info. This is the latest available 3.8 version, so at least the issue is not coming from an outdated runtime.

irask2 wrote
I am using version 3.8 because the author of the asset I am using required this version.

Please note that you can upgrade exported Spine skeletons. You can use Spine - Import Data.. and Texture Unpacker in the Spine Editor set to version 3.8 to import from .json or .skel.bytes assets, then you can save your project, switch to Spine Editor 4.0 or 4.1 and re-export your skeleton.

If you have a lot of projects to convert, you might want to use the Spine command line interface as described here:
How to automate version migration of binary assets?

irask2 wrote
Why is baked animation not recommended?

spine-unity Runtime Documentation: Skeleton Baking
You lose a lot of Spine features (deform keys can't be mapped to Unity's animation features), risk incorrect interpolation, can't use skins, and so on.