Hi Mitch, thank you so much for the assistance thus far.

We followed your video step by step exactly but still, the same issue. (Random material dropping).

We are using spine 2.0.13 and downloaded the latest runtime from github. We deleted our existing player and exported as per your video, and everything seemed ok. We then used rightclick->spawn to add the spineobject to the heirarchy. We then attached a movement script and a script that changes animations depending on direction, as well as a collider and ridgidbody, and then dragged this object into a prefab folder to create a prefab from this object, the existing prefab created by the spine export is left untouched in the folder.

We then made a change to one of the animations and exported with the same path/settings as before, but unity now has an exception because the material is gone, if we inspect the skeletonData the preview window shows pink where our textures should be.

We have a spine project, that I've created that has a series of animations for different perspectives (ie: player walks up you see the back of him and the walk "up" animation, walks right you see the right walk animation etc) all these skeletons are in 1 spine project).

Upon updating\adding more animations everything just falls apart, even though we followed your video to the T. Now is this a 2.0.13 issue? Do you absolutely recommend that we use an older version of Spine to carry on with our workflow?

In a nutshell: We have a spine project with a skeleton for each direction (this is not a platformer, so 8 directions of movement, like Zelda) So we want to be able to export as you did in your video then attach a movement script as well as a script for controlling the animations while still being able to update animation files whenever we need to. (After iterations). Without breaking everything.

Thanks! :bang: