Skeleton Render Separator missing material

FelixW

When I attach the Skeleton Render Separator according to the guide from the github docs the material on my original renderer as well as the new ones gets deleted, so the game crashes immediately. When I set the material by hand again, it again gets deleted when I start the scene.

The guide I use:
https://github.com/pharan/spine-unity-docs/blob/master/SkeletonRenderSeparator.md

I downloaded the latest runtime from here:
Noteworthy Spine-Unity Topics

Unity 5.3.5p4

Pharan

There's no code in it that touches the original renderer.
What do you mean by "the material on my original renderer as well as the new ones gets deleted"?

The material arrays are also managed by SkeletonAnimation/SkeletonRenderer directly because it needs to manage multi-material/multi-texture skeletons. More on that here: Spine-Unity Runtime Documentation

FelixW

Hi,
after I have added the Separator component, chosen the node and added two parts renderer automatically (by clicking the button to do so) and start the game I get an error. Basically in ArraySubmeshSetMeshGenerator in the function StructureDoesntMatch the material on the variables lhs and hrs is null.
By "the material on my original renderer as well as the new ones gets deleted" I mean that on the mesh renderer that rendered the whole object before and gets deactivated by the separator there is a new material slot added to 'Materials' that's empty. Also on the two new mesh renderers that would render parts of the original mesh there is no material assigned - the slot is empty.

Any hints on this? Still can't get it to work...

Apparently it depends on which slot I choose for separation. If I choose the first one from the list it crashes with above error message.
Does it matter what bone I choose from the Skeleton Renderer if I just want to separate the mesh into two?

Pharan

The matter here is that the null material is never supposed to happen. And if it does, you're supposed to get errors higher up even before it even gets to the rendering code. This is unless you've added some code yourself that's supposed to set materials but incorrectly set it to null.

Can you send your Spine files and steps to reproduce this? Or your minimum Unity project that exhibits the behavior? 🙂
You can send it to unity@esotericsoftware.com

FelixW

Sure, I'll try to put sth together.

Alright, sent you a mail with a small test scene.
Cheers,
Felix

Pharan

Found the bug. It was silly and easy to fix. Should be included in the unitypackage by Monday.
But I notice that you're using old code. I think this is spine-unity 3.2?
In this case, you're free to edit it yourself.

Open SkeletonRenderer.cs.
Look for this code:

bool forceSeparate = (separatorSlotCount > 0 && separatorSlots.Contains(slot));
if ((vertexCount > 0 && lastMaterial.GetInstanceID() != material.GetInstanceID()) || forceSeparate) {

and replace it with this:

bool forceSeparate = (separatorSlotCount > 0 && separatorSlots.Contains(slot));
if (vertexCount > 0 && (lastMaterial.GetInstanceID() != material.GetInstanceID() || forceSeparate)) {

Only the parentheses/grouping differs.

That should handle the basic cases.
I've done some initial testing including with weird slot setups (everything invisible, etc). Seems to handle those too.

FelixW

Cool - thanks!