No mix & broken runtimes?

rxmarcus

I'm very sorry to post another one of these topics, but I am stuck and need help.

It seems like since I updated Spine to the newest version (1.8.14), I have had issues getting unity to recognize my spine animations. The "Mix" button will not show up. I've read many posts of people having this issue and they have resolved it by updating the runtime files.

I went ahead and did this, but now in Unity I'm getting the error "Assets/Spine/spine-tk2d/Assets/Spine/spine-csharp/src/AnimationState.cs(109,67): error CS1501: No overload for method Apply' takes6' arguments"

So basically seems like the 'Apply' method is no longer used in the new version of these runtimes? I'm just not sure what to do to resolve this problem. I went ahead and updated my 2DTK as well...

Any help would be appreciated.

rxmarcus

Pharan

EDIT:
Oh, you're right. There was a commit yesterday that changed AnimationState. How bizzare.

You should be able to use this version without problems: https://raw.github.com/EsotericSoftware ... onState.cs

Just replace your current AnimationState.cs with that one.

EDITEDIT:
Oh. It was just a typo on line 109. It was supposed to be a Mix call and not Apply.

rxmarcus

Thanks that allowed me to build my project with no errors. Still not able to get "Mix" buttons to show up and don't see any error messages to help me pin point the problem. I read in other posts that it should be putting errors to the console, but I don't see any... Any idea how I can view the errors so I can resolve my issue?

Søren

Im sure Nate will take a peak here and fix it if a fix is needed pretty quick. Sorry for the trouble.

rxmarcus

Sounds good, I'm sure it is a TON of work for you guys to offer so much support for so many different runtimes. Hopefully we can get this figured out soon.

Pharan

Pharan wrote
EDITEDIT:
Oh. It was just a typo on line 109. It was supposed to be a Mix call and not Apply.

rxmarcus

Would someone be willing to look at my json file and image files to see if they can understand what I'm doign wrong? Just not sure what to do when I have zero feedback on what error is happening.

Pharan

Since it's TK2D, I'm not sure I could be of much help. But go ahead.

rxmarcus

K i've attached a zip file with the images as well as the exported spine json file. I feel like its something I'm doing wrong in spine and not Unity. I wonder if there is any reason for me to even be using 2DTK for my spine characters? Just was doing it because I had 2DTK.

Pharan

Seems like you duplicated some attachments.
This causes Spine to automatically use paths so the attachments can have different names and share the same path/image.
I think the official Spine-C# doesn't support paths yet.
The log should've said that it couldn't find the regions.

To remove paths in the editor, you need to select the attachment and delete the contents of the path text box below the tree.

But on the runtime side, here's a commit in my fork that gives it support, if you wanna give it a shot on your end:
https://github.com/pharan/spine-runtime ... fee1463532

Some class structures changed since someone ported MeshAttachments to C# so... it'll take some minor thinking to make it work on the current Spine-C#. 😃

rxmarcus

Should my tree names be matching the path name found when you select a tree item? I'm noticing I have several tree items like "R_shoulder2" with a path of "R_shoulder". My brother actually does the animation so I'm not super familiar with spine, but seems like this might be the issue you are describing?

Pharan

That's correct. The current Spine-C# treats tree names as paths.

I assume R_shoulder is the actual image, and R_shoulder2 is the duplicate. But the runtime will attempt to look for an image called R_shoulder2 and will fail to find it because it has no knowledge of the path field.

If you're the programmer then, it shouldn't be too difficult to implement paths. Just check that commit and see the lines that were changed. The part where a new attachment object is created might not make sense because of the change caused by the MeshAttachment commit. Feel free to ask if you get lost.