Spine Timeline Update?

lucky

Hi ,
We're updating spine to latest 4.2, but it looks like on the doc page the latest spine timeline package is at 4.1
http://en.esotericsoftware.com/spine-unity-download
And if installing via UPM there is a 4.2 version but it requires spine 4.2.13, so I wanted to ask
Is there a non UPM version of Spine Timeline 4.2 so we can both update spine and the timeline extensions to both be up to date?

Thanks

Harald

lucky We're updating spine to latest 4.2, but it looks like on the doc page the latest spine timeline package is at 4.1
http://en.esotericsoftware.com/spine-unity-download

Could you please describe where you found the latest Spine Timeline UPM package to be "at 4.1"? Do you see 4.1 links? I just checked the download links on the download page and found nothing wrong, also the Timeline zip package content of the second zip package is correctly depending on spine-unity 4.2.13. Did you perhaps miss to refresh the download page?

lucky And if installing via UPM there is a 4.2 version but it requires spine 4.2.13

The latest spine-unity 4.2 UPM version is currently 4.2.63. As you're saying "but it requires spine 4.2.13": why would you want to use an older version than that? Please be sure to update to the latest spine-unity 4.2 package in Unity Package Manager.

Is there a non UPM version of Spine Timeline 4.2 so we can both update spine and the timeline extensions to both be up to date?

It's right there at the download page, as usual:
http://en.esotericsoftware.com/spine-unity-download

lucky

Thanks, also @Harald We're now on Unity 2023.3.21f1
But the spine library's newest version looks like is using a legacy function (TextureImporter.spritesheet)
Spritemeta data can not be accessed from textureimporter anymore and we need to use Unity new API to build it.
Screenshots of file affected

Context from when it was changed ( I think, we've been hounding this error this morning)
https://unity.com/releases/editor/whats-new/2022.2.0
2D: Obsoleted: Support for accessing sprite meta data through TextureImporter.spritesheet has been removed. Please use the UnityEditor.U2D.Sprites.ISpriteEditorDataProvider interface instead.

Harald

lucky We're now on Unity 2023.3.21f1

Please note that 2023.3 is not officially supported yet:

spine-unity unitypackage
Compatible with Spine 4.2.00 or newer and Unity 2017.1-2023.1.

Nevertheless, thanks for reporting the issue with Unity 2023.3. We will publish a bugfix for this issue soon.

Harald

@lucky FYI: I have deleted the posting by Spinebot, which listed outdated 4.2-beta UPM package download links. Please never use old beta packages when non-beta 4.2 packages exist.

Harald

@lucky Having checked the latest Unity 6 Preview 6000.0.0f1 (with all UPM packages updated), no such error occurred on our end. When jumping to the declaration of .spritesheet, we just see a normal Obsolete with no bool error=true, thus only being a warning:

//
// Summary:
//     Array representing the sections of the atlas corresponding to individual sprite
//     graphics.
[NativeProperty("SpriteMetaDatas")]
[Obsolete("Support for accessing sprite meta data through spritesheet has been removed. Please use the UnityEditor.U2D.Sprites.ISpriteEditorDataProvider interface instead.")]
public SpriteMetaData[] spritesheet { get; set; }

Could you please have a try whether updating resolves the issue for you?
Also I wonder where you got Unity version 2023.3.21f1 from. Could you share a download link, or how you installed this?

lucky

Hi @Harald apologies for the late reply, wasnt feeling well yesterday

And super sorry on the version number , 2022.3.21f1 , not 23

So to your first question, I innitially deleted all previous versions of spine (which were installed via unity package) And i did the Package manager route
http://en.esotericsoftware.com/spine-unity#Alternative-Installation-via-Package-Manager

Installling via using "EsotericSoftware/spine-runtimes.git?path=spine-csharp/src4.2" which gave me the C Sharp runtime 4.2.23
Then I used the follow up instructions http://en.esotericsoftware.com/spine-unity-download
"Use this package if you have installed spine-unity via UPM packages using the Package Manager, instead of from a unitypackage. Compatible with spine-unity 4.2 and Unity 2017.1-2023.1.
Add package from git URL:"
"EsotericSoftware/spine-runtimes.git?path=spine-unity/Modules/com.esotericsoftware.spine.timeline#4.2"

Which gave me the timeline extension which wasn't compatible (version 4.2.15 seen in screenshots above)
(i ran update on both too, no change)

So I posted here, and then I undid those changes so I went the manual route.
And by that I mean , from the unity-package page

i got the latest .unitypackage Package version: spine-unity-4.2-2024-05-07.unitypackage
And then I got the newest version of the timeline unity package which was
Package version: com.esotericsoftware.spine.timeline-4.2-2024-04-17.zip

Which on testing works and is functioning fine with Spine runtime on the scene i tested with.

The errors we're getting are from
/Assets/Spine/Editor/spine-unity/Editor/Asset Types/SpineAtlasAssetInspector.cs
Line 319
Of the newest runtime I could download at the time.
You can get it from https://unity.com/releases/editor/archive

Does this help?
Where would you recomend i insert that code?
Currently on updating the project/opening from 21 to 22 (to the version above) it enters safe mode due to the errors

lucky

Oh in regards to the code, are you discussing changing the definition in my local unity install? I'm not sure if that would be a good idea long term for a big team , unless you mean changing built in property definition on a per project scope. Haven't had experience with that as of yet , i'll look into it

Harald

lucky Oh in regards to the code, are you discussing changing the definition in my local unity install?

No, you can't change that thirdparty method declaration (and shouldn't if it were possible), I was just referring to what I see with the latest package, which should just issue a warning and not an error.

lucky So after digging we found our internal engine on top of Unity , and which we build a lot of our IPs on treats outdated warnings as hard errors so we’ll whitelist this file for now !

Great to hear you've figured it out, thanks for letting us know!

lucky I’m guessing the old method is still in there so the runtime can be compatible with Unity 2021 🙂

2021? You mean 2022.3 I guess 😉.

Yes, the method is still functional, it's just deprecated for now. The alternative to the deprecated method comes with the problem of requiring an additional UPM package dependency, which we would like to avoid if possible since it's just for a single less used feature.

lucky

Update ! So after digging we found our internal engine on top of Unity , and which we build a lot of our IPs on treats outdated warnings as hard errors so we’ll whitelist this file for now ! I’m guessing the old method is still in there so the runtime can be compatible with Unity 2021 🙂

That’s the update for anyone who finds this error/ warning