关于 SkeletonBakingWindow 不支持的关键帧

simonyrl

我现在的项目有需求将spine动画烘焙成unity animation（由于性能问题，确切的说是移动端无法承受大量spine骨骼更新的开销，所以打算 spine=>skinned mesh Renderer+animation=>gpu instance），但是发现SkeletonBakingWindow这个工具不支持mesh deform keys，color keys，draw order keys。
但是我现在手头上的spine动画充满了mesh deform 和draw order。通过SkeletonBakingWindow烘焙出来的
skinned Mesh Renderer动画有不少的错误的形变和渲染顺序问题 🙁
请问有还有什么方案可以拯救一下。

Spinebot

Skeleton Baking in Spine does not support mesh deform keys, color keys, or draw order keys, which can lead to issues when baking animations to Unity's animation system. Since your animations heavily rely on these features, the baked animations may not behave as expected. Unfortunately, there is no direct solution to fully translate these unsupported features into Unity's animation system. It is recommended to use Spine's runtime components like SkeletonAnimation or SkeletonMecanim for better compatibility and performance, as baking should be a last resort due to its limitations. If performance is a concern, consider optimizing your skeletons by reducing the number of bones or attachments, or using weighted bones for animations.

Harald

@simonyrl In general your plan of using skeleton baking to receive a skinned mesh and animate it on the GPU would not be working, as the baking procedure of the Mesh Baking Window does not create a single SkinnedMesh but creates a Prefab with one GameObject per Bone, and one MeshRenderer per RegionAttachment and one SkinnedMeshRenderer per MeshAttachment. This will be worse performance wise. Please do not use the skeleton baking functionality unless you really have a good reason that you can't use anything else. The only baking that would be beneficial performance-wise while sacrificing a lot of the features (also mix transitions) would be to render out image sequences from the Spine Editor instead of having full skeletons. This is likely not what you want however.

If you just have a performance issue, there are various ways to improve the situation. First make sure you've done everything listed in the FAQ Performance section:
https://esotericsoftware.com/spine-unity-faq#Performance
What are the metrics of your typical skeleton, and what does the scene setup of your game look like? What optimization measures have you taken so far in regards to performance?
Also, the parallelization issue ticket is close to completion, which would bring performance benefits pretty much for free.

simonyrl

Harald 非常感谢你的回复。
我清楚 Mesh Baking Window会烘焙出一个多骨骼多SkinnedMesh的物体。我有一个专门针对这种情况能将所有骨骼和SkinnedMesh合并成一个SkinnedMesh的工具。只不过还没有到追究这个工具是否能正确运行的时候， Mesh Baking Window烘焙出来的物体就已经有错误的形变和渲染顺序问题。

常见性能部分，我已经做了所有我能做的了（我没有spine源文件，只有输出出来的文件）。

非常高兴看到有基于JobSystem优化的部分，我会尝试一下。(我有找chatGPT询问过关于spine基于jobSystem的优化，它没有找到这个网页🙁 )

关于我目前的骨骼指标，场景中大概会有同时400+的spine动画在运动，其中大概有80个的骨骼数量平均在60左右。剩下的320个物体的骨骼数量比较少，大概是不到5个骨骼？
从unityProfiler中看，大概占用了66%的cpu，希望能尽量降低cpu消耗。
目前内存占用并不高，渲染用时也不高，所以才打算用GPU Instance
最后，再次感谢您的回复，have a nice day 😃

Harald

Thanks for the additional info. If you don't have access to the skeleton project files itself and have to work with the exported assets: Be sure to disable off-screen updates via the Advanced - Update When Invisible property. Also if some skeletons are not as crucial, you could limit their update rate to every 2nd frame or similar.

Please note that the official not yet released threading solution will not be based on the Unity JobSystem, it is based on normal threads. I assume that you mean postings by another users, where some implemented their own version of a threading solution. While you could use one of their solutions as an intermediate solution, be aware that those are much more limited than the official solution will be (just parallelizing either mesh generation or animation instead of both, not handling callbacks correctly, allocating memory each frame, etc).