Thanks @Harald

Hey guys - I'm assuming I can follow this guide to upgrade from Spine-Unity 3.6 to 3.8, am I correct? Or do I need to upgrade to 3.7 first?

Thank you Harald!

After updating to 3.8, I got a lot of errors.

Updated your Spine-Unity runtime to 3.8 according to your guide.
Most of the problems have been solved successfully, but there is one problem.

Like the attached image, there are a lot of errors in "Assets \ Spine \ Runtime \ spine-unity \ Components \ SkeletonGraphic.cs" and I can't test the game.
Do you know this issue?
How can I solve this problem?

And I'm currently using Unity version 2019.3.0a5.
If the cause is in the Unity version, is there a version you recommend?

A couse of error is that class or namespace "MaskableGraphic" does't exist in Asset.

Dear Harald,
As you advised, I downgraded Unity.
A large amount of Prefab data has been corrupted, but the Spine animation can now be played back safely.
Thank you for your constant support.

I hope that all versions of Unity will be supported over time.

Also, I will take care not to inadvertently update Unity.

Hello,
I'm unity3d c# programmer, but I have few spine animation, from different versions 3.7 and 3.8. How I can use it in one project without re-export. I dont have Spine, I ordered this animations. Thanks for a reply)

I'm afraid you must export from the version of Spine that matches the version of the runtime you are using. You could try using the JsonRollback tool to make 3.8 JSON compatible with 3.7 runtimes, but this is not officially supported:
Open project in an older version

Also please note that using the Spine Runtimes without a Spine license has restrictions: all users of your application will need their own Spine license. Read more here:
Spine Runtimes License Agreement

Thank you always, Harald.
My prefab was able to be restored with almost no damage the way I found it on the net.

But I still have problems.
I have a license for the latest version of Spine.
If you try to import a character created with it into Unity 2019.2.01f by drag and drop, Unity will crash.
However, deleting the imported file from Windows Explorer will no longer crash.

This problem happen only the case of Spine exported files, not other files(for example, png files).

Do you know how to solve this problem?
Did you also recognize this issue?
Please give me some advice.

P.S.
My problem is the same case of below URL:
Unity Crashes when importing spine files

Dear Harald,

Thank you for your reply.

I tried as many times as I could until I received your reply, but I couldn't solve the problem.

Some data was lost, but I found an older version of Spine data in the backup data.

I will wait for the runtime to support Unity 2019.3x.

Hi,

I'm updating from Spine 3.6 to 3.8 and using Unity 2019.1.9f1.

I have a custom implementation of the mix and match script and I get the following error:

'AtlasAssetBase' does not contain a definition for 'materials' and no accessible extension method 'materials' accepting a first argument of type 'AtlasAssetBase' could be found (are you missing a using directive or an assembly reference?)

referring to the following code in Start():

skeletonAnimation = GetComponent<SkeletonAnimation>();
         if (sourceMaterial == null) 
         {
            if (skeletonAnimation != null)
               sourceMaterial = skeletonAnimation.SkeletonDataAsset.atlasAssets[0].Materials[0];
         }

What could be the issue?

Hi Harald,

No worries. Thanks!

Hi Harald,

Im having an issue for some days i cannot resolve.
I updated to spine 3.8, using Unity 2019.2. Re exported all spines.

and i keep getting this error:
InvalidCastException: Specified cast is not valid.
Spine.Unity.Editor.SpineEditorUtilities.IssueWarningsForUnrecommendedTextureSettings (System.String texturePath) (at Assets/Spine/Editor/spine-unity/Editor/Utility/SpineEditorUtilities.cs:172)

And cannot edit the spine object (the skeleton animation component is broken).

Am i missing something here?

thanks a lot

Hi Herald!

Thanks for responding.

I exported the file using Spine 3.8.68, and using the unity package "spine-unity-3.8-2019-08-23".
I will send you a zip file.

Thanks again

Hello,

We are updating to spine 3.8 - was the Ragdoll and the Kinematics Shadow Modules removed from the integration completely?
Got error in scripts using those two, since they no longer exist. Is there a substitute in the pkg?

It seems their namespace has been changed, see the notes on SkeletonRagdoll2D etc. in the CHANGELOG spine-runtimes/CHANGELOG.md at 3.8

Finally upgraded to Spine 3.8! Aside from fixing the changed method/variable names, it went pretty smoothly. Only one issue spotted so far and it's related to Attachment's "GetRemappedClone". On Spine 3.7, region attachments would copy any color tinting, but mesh attachments wouldn't. So I had code like this:

Spine.Attachment newAttachment = templateAttachment.GetRemappedClone(atlasRegion, true, true, skeletonDataAsset.scale);
 if (newAttachment == null)
     Debug.Log("clone attachment failed for " + originalSkin + " " + regionName + " " + slot + " " + templateAttachmentName);
 if (templateAttachment.GetType() == typeof(Spine.MeshAttachment))
 {
     Spine.MeshAttachment newAttachmentCasted = (Spine.MeshAttachment)newAttachment;
     Spine.MeshAttachment oldAttachment = (Spine.MeshAttachment)templateAttachment;
     newAttachmentCasted.R = oldAttachment.R;
     newAttachmentCasted.G = oldAttachment.G;
     newAttachmentCasted.B = oldAttachment.B;
     newAttachmentCasted.A = oldAttachment.A;
 }

But I noticed in Spine 3.8, a bunch of our attachments were appearing white suddenly. So it turns out we need to also do this check for RegionAttachments now:

if (templateAttachment.GetType() == typeof(Spine.MeshAttachment))
        {
            Spine.MeshAttachment newAttachmentCasted = (Spine.MeshAttachment)newAttachment;
            Spine.MeshAttachment oldAttachment = (Spine.MeshAttachment)templateAttachment;
            newAttachmentCasted.R = oldAttachment.R;
            newAttachmentCasted.G = oldAttachment.G;
            newAttachmentCasted.B = oldAttachment.B;
            newAttachmentCasted.A = oldAttachment.A;
        }
        else if (templateAttachment.GetType() == typeof(Spine.RegionAttachment))
        {
            Spine.RegionAttachment newAttachmentCasted = (Spine.RegionAttachment)newAttachment;
            Spine.RegionAttachment oldAttachment = (Spine.RegionAttachment)templateAttachment;
            newAttachmentCasted.R = oldAttachment.R;
            newAttachmentCasted.G = oldAttachment.G;
            newAttachmentCasted.B = oldAttachment.B;
            newAttachmentCasted.A = oldAttachment.A;
        }

I'm not sure if this is intended but it's something I came across.

I'm having trouble getting the timeline package to work. I've installed the spine 3.8 UPM and fixed all compile errors related to that (we are upgrading from 3.7). But when bringing in the timeline package (I can't find a UPM, only a zip) I'm getting new errors stating that various spine namespaces can't be found. Could I be installing it incorrectly? I just unzipped the archive to the packages folder in my unity project. I tried importing the zip with the package importer, but it gives me an error that states that all of the files already exist in my project (they don't).

Any thoughts?

I'm also seeing an issue with certain meshes not displaying properly for re-exported skeleton files; it seems that some weighted meshes appear to have negative scaling or are skewed or something, although there is nothing on the bone rotation/scaling to suggest why this would be happening. Any help would be greatly appreciated.

Unity version is 2019.4.9f1

Please note that our resident Unity expert, Harald, is currently on vacation. He'll catch up to forum posts and everything else ASAP when he's back. I can try to help, but I apologize if only in a basic way.

There should not be any errors after installing, so that is a clue something went wrong early on. Did you get spine-unity from the download page? You should remove the old files first, otherwise you could have a mix of old and new files which would cause problems.

Thanks Nate, any help is appreciated. I completely removed all spine files and reinstalled (the spine-unity upm and timeline package are both from the downloads page). In the process of reinstalling, I've noticed that the namespace compile errors are only popping up when 'SPINE_TK2D' is defined. As soon as it's disabled, they disappear. Could there be a compatibility issue with the timeline package and tk2d support? Hopefully that helps to narrow it down.

Oy, it very well could be an issue with Toolkit2D. It is not as popular as using straight Unity, so likely sees less testing. I'm afraid this is Harald's domain, we may need to wait for him to return.

Is there no plan to make spine-unity 3.8 for Unity 5.6? It seems my artist was on auto update and now I have no ability to import the new assets into our 5.6 game due to the lack of package support.

I can understand removing Unity 5.6 support with the upgrade to 4.0, but I did not expect it with 3.8. Is there a way that I can downgrade the 3.8 files she made to 3.7 if there is not going to be a Unity package compatible with Unity 5.6 for Spine 3.8?

Thank you so much, it looks like I can export the 3.8 version files using 4.0 (as 3.8 does not have versioned exports that I can find) and import without issue to 3.7. I think she updated recently, thankfully, but I have requested she set her projects to 3.7 so we won't have any further issues.