• RuntimesUnity

  • Separator hides the whole Skeleton after upgrading to URP 15 using ShaderGraph

    anglais

Hello Spine,
at the very beginning I'd like to apologize for simplifying the problem to this post's title that may not be describing the root of what is going on, so I follow specifying what we experience more thoroughly:

We've been using Unity 2022.2 with URP 14 until now and for some Skeletons in our project we use custom shaders made in ShaderGraph. To utilize URP 2D Lights, we use ShaderGraph set to "Sprite Lit" in the Graph Settings. Things have been going well.

After attempt to upgrade to Unity 2023.1 (URP 15) we observe that Skeletons with Materials using such ShaderGraph sprite shaders are rendered fine, but when the SkeletonRenderSeparator is enabled - the whole animation disappears and nothing is rendered at all. Spine shaders working well as expected.

Do you please have any idea what is going on, what had changed, or how we may fix this if we are doing something incorrect?

Related Discussions
...

Attaching a project where Spine Boy is being separated and rendered in Unity 2022 but not visible after opening and upgrading the project to Unity 2023

spinetest2022219.zip
1MB

@gunther Thanks for reporting and sorry for the troubles!

The problem was with assigning the MaterialPropertyBlock at the part renderers when the Copy Property Block option is enabled at the SkeletonRenderSeparator component. If no MaterialPropertyBlock is used at the main renderer, it seems that uninitialized data is received in Unity 2023.1 and thus assigned at the other renderers. This issue has just been fixed.

New spine-unity 4.1 and 4.2-beta unitypackages are available for download:
https://esotericsoftware.com/spine-unity-download

This issue ticket has been tracked under this ticket URL:
EsotericSoftware/spine-runtimes2358
Please let us know if this fixes the issue on your end as well. Thanks for reporting!

@Harald After update everything works great as expected. Thank you for your immediate fix and for describing the problem as well.

@gunther Thanks for the feeback, glad we could resolve the issue. Thanks again for reporting.