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

Slight Optimisation to SkeletonComponent

danthat

With a lot of Skeleton Animations in my scene, I noticed SkeletonComponent.Update was taking up a lot of space in the Unity Profiler.

So I slapped this at the top, and it's now hardly a bother. Is this a stupid thing to have done, or is it a clever thing that can go in the runtimes proper so I don't have to keep copy-pasting it across?

public virtual void Update () {

  if (!renderer.isVisible)
     return;

Framerate shot up 25 points with that.

Pharan

I assume you were using the old runtime?

I was recommending something like this to Nate for the new runtime refactor.
I dunno if this specifically will make it into the official thing but I think Spine-Unity will have something very similar to it eventually.

In the meantime, this should help others looking for the same optimization.
I assume you had a lot of skeletons that weren't in the camera's view so that's why you got the significant bump?

In Unity's animation system though, users are given a choice through a checkbox in the inspector to continue animating/updating specific instances even when the thing is outside the camera's view. It's sometimes useful for things that need to make sounds (by emitting events) or are driven by root motion or other stuff like that.

The new runtimes have better separation of "rendering" and skeleton updating so even if you still want the skeleton to animate, you can still have performance savings by not updating the mesh when the Renderer isn't in view.

Nate

https://docs.unity3d.com/Documentation/ ... sible.html
It doesn't say when isVisible returns true. Probably it uses the mesh's bounds, but we can only guess. For some reason, Unity seems to use the initial bounds of the mesh for culling purposes. If the skeleton is animated and much larger later, the bounds don't seem to increase in size, even though we call mesh.RecalculateBounds(). :tmi:

There is another problem with using the mesh bounds to avoid updating the skeleton and mesh unnecessarily. If updating the skeleton would make the bounds bigger, then you may avoid updating the skeleton when it should be visible. :bang:

You can see this in the spineboy example for spine-unity. Move him down so only his head is visible and put if (!renderer.isVisible) return; in SkeletonRenderer#LateUpdate. Spineboy will never render. Because his center (0,0) is off screen, the skeleton and mesh are never updated. A better check would be:

if (submeshMaterials.Count > 0 && !renderer.isVisible) return;

This causes the mesh to be updated at least once. However, if you move spineboy down, just off screen, then when he jumps he won't be visible.

Any ideas with how to make this work with Unity would be great. :smoke: