• Unity

  • Optimization Spine2d in Unity

Related Discussions
...

Please tell me which settings to set in Unity for better performance in Player Settings? And what would you recommend for optimization? Whether Render Queue affects performance, very little is written about it, if you can explain.

Dmitriy Makeyev wrote

Please tell me which settings to set in Unity for better performance in Player Settings?

Settings under Other Settings - Rendering:
In general for performance reasons I would recommended the following:

  1. Static batching and Dynamic batching enabled,

  2. GPU Skinning enabled as well, however it will only affect your non-Spine animated assets. It has no impact on Spine assets.

  3. Graphics Jobs (Experimental): I would not yet use this setting in production to be honest.

  4. Lightmap encoding: only makes sense if you are using Lightmaps at all, then of course lower quality could help.

Nevertheless, you will have the highest impact on performance by simplifying your Spine skeletons, e.g. reducing then number of bones and the number of vertices.
I have previously posted some hints about optimization on this forum thread.

Dmitriy Makeyev wrote

And what would you recommend for optimization?

See above.

Dmitriy Makeyev wrote

Whether Render Queue affects performance

If you really mean this render queue setting, then this does not really affect performance. You cannot change the render queue of materials to your liking as this would cause incorrect rendering. E.g. you have to draw opaque materials before transparent ones, otherwise it will look incorrect.

Thanks for the answer! Regarding the rendering queue, I was advised to make changes to your shader and to the standard sprite-default shader for regular sprites too. What do you think about this? Is it worth making such changes?

So you have:
SubShader {
 Tags { "Queue"="Transparent" "IgnoreProjector"="True" "RenderType"="Transparent" "PreviewType"="Plane" }


Changed:
SubShader {
 Tags { "Queue"="Geometry" "IgnoreProjector"="True" "RenderType"="Opaque" "PreviewType"="Plane" }


No problem.

Regarding the changed tags: You have changed the material from transparent to opaque. This will always have a positive impact on performance - it will then be able to draw your objects sorted in front to back order and utilize the z-buffer to discard pixels early that are behind other opaque parts.

So what I meant above is that the Render Queue is always linked to the RenderType and cannot simply be changed without effect to the resulting image. It is preferrable to draw stuff in "Queue"="Geometry" (which means: early), but you cannot do this for "RenderType"="Transparent", then it will very likely look wrong.