Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Spine-Unity 4.2 to 4.3 Upgrade Guide

chrisoshea

Thanks for the reply. I'm stuck on the step number 3, update your code. I want to follow the "Optional Two-Step Migration from 4.2"

Unity when I try to add the csharp git link with src#a07b1de on the end in Unity package manager, it says there is an error adding. It's also not clear which git link to use to for the unity runtime.

This is so I can get the updated api, update my code and then delete the package, install 4.3 packages

Harald

@chrisoshea Sorry for the troubles!

My fault, Unity Package Manager does not support short-form git URLs like a07b1de, it has to be the long a07b1de9ce972d4e38898ccf2cc84de16ff66c9b hash. The correct URL is therefore:

https://github.com/EsotericSoftware/spine-runtimes.git?path=spine-csharp/src#a07b1de9ce972d4e38898ccf2cc84de16ff66c9b

We've updated the upgrade guide .md files in the repository accordingly.

chrisoshea

Harald Thank you Harald.

If I'm importing from git that particular commit ofr the csharp runtime via package manager, which version of the unity runtime should i be using for it to match that commit above?

Harald

chrisoshea You would normally use the same commit hash at the spine-unity URL as well.

[Edit: added:] This is because the spine-unity runtime will always receive the required changes in the same commit if the spine-csharp runtime commit contains a breaking commit.

Harald

chrisoshea We are using runtime 4.2 in the project but I just realised the artist is using editor 4.3. They seem to work in Unity, but should they be working? Docs suggest you need 4.3 runtime.

Skeletons exported with version 4.3 can't be imported in spine-unity 4.2, see the documentation. The spine-unity runtime would log an error message if the version does not match, so I doubt that's the case. If you have verified that the skeleton contains version 4.3 in it but still opens on a 4.2 spine-unity runtime, please do let us know.

chrisoshea

So the way the reference animation files are created has changes, from a folder of multiples to a single asset. Is it worth deleting the old ones and making the new styles ones, if this is the way going fowards?

Harald

chrisoshea So the way the reference animation files are created has changes, from a folder of multiples to a single asset. Is it worth deleting the old ones and making the new styles ones, if this is the way going fowards?

For an existing project which already uses existing AnimationReferenceAssets, please do not delete the old assets and re-generate them, or you end up with broken references at your scenes or prefabs. The old assets can exist alongside the new ones without any issues. You can of course delete them if you want your project uniform and are happy to do some additional work with the re-assignment of animation assets.

gunspike

안녕하세요, Spine 팀.

최근 Unity 프로젝트의 Spine Unity 런타임을 4.2에서 4.3으로 업그레이드했습니다.

업그레이드 후 Spine Editor 4.3.04에서 모든 Spine skeleton 파일을 다시 내보내기 했고, Unity에서 다시 임포트했습니다. 이전에 발생하던 버전 불일치 오류는 해결되었으며, 현재 Unity 콘솔에는 import 관련 오류나 다른 에러가 표시되지 않습니다.

하지만 Unity에서 애니메이션이 재생되지 않는 문제가 있습니다.

환경:

Unity 버전: [Unity 버전 6.4]
Spine Editor 버전: 4.3.04
spine-unity 런타임 버전: 4.3
Export 형식: Binary .skel
플랫폼: [Editor / Windows / Android / iOS 등]

진행한 작업:

Unity 프로젝트의 spine-unity 런타임을 4.3으로 업그레이드했습니다.
Spine Editor 4.3.04에서 skeleton 데이터를 다시 export했습니다.
Unity에서 Spine asset들을 다시 import했습니다.
기존 scene/prefab을 열었고, Spine Unity 4.3 업그레이드 알림이 표시되었습니다.
해당 알림에는 Skeleton 관련 컴포넌트가 animation component와 rendering component로 분리되었다는 내용이 있었습니다.
이후 Unity 콘솔에는 별도의 오류가 표시되지 않습니다.

기대 결과:

업그레이드 전과 동일하게 Unity에서 Spine 애니메이션이 정상적으로 재생되어야 합니다.

실제 결과:

skeleton 파일은 정상적으로 import됩니다.
Unity 콘솔에 오류는 표시되지 않습니다.
하지만 애니메이션이 재생되지 않습니다.

추가 정보:

이 프로젝트는 기존에 Spine Unity 4.2를 사용하던 기존 Unity 프로젝트입니다.
문제는 Spine Unity 4.3 업그레이드 및 Spine 4.3 재export 이후 발생했습니다.
Import 자체는 성공하지만 runtime에서 애니메이션 재생이 시작되지 않는 상태로 보입니다.
Spine Unity 4.3에서 SkeletonAnimation, SkeletonMecanim, SkeletonGraphic 등이 animation component와 rendering component로 분리된 구조 변경과 관련이 있을 수 있다고 생각하고 있습니다.

Spine Unity 4.3의 split-component 업그레이드 이후 기존 prefab이나 scene에서 반드시 확인해야 할 항목이 있을까요?

또한 기존 스크립트에서 SkeletonAnimation, SkeletonRenderer, SkeletonGraphic, AnimationState 등을 참조하고 있는 경우 필요한 마이그레이션 절차가 있는지도 안내 부탁드립니다.

감사합니다.

Misaki

gunspike From the situation you described, it sounds possible that some of the required upgrade steps may have been missed. The main post in this thread explains the upgrade procedure, and when upgrading from 4.2 to 4.3, it is important to follow the steps described there carefully. Since there were quite a few significant changes between Spine 4.2 and 4.3, please make sure to review the guide first if you haven’t already.

In particular, please be sure to read the 4.3 Split Component Upgrade Guide linked from the main post.

Also, separately from the upgrade procedure itself, Spine Editor 4.3.04 had a critical issue where incoming curve handles were not being saved for non-Bézier keys. Because of this, we recommend re-exporting all skeleton data files using Spine 4.3.06 instead. We apologize for the inconvenience.

lxs

zf3d 重新导出好几十个动画 :

Harald

@lxs Did you accidentally cut off your text, or is there an image missing?

AnduoGames

Heya, I just updated to 4.3.86 unity runtime. I can no longer import spine files. It did work with 4.3.85.

Trying to reimport the .skel, I get "Could not automatically set the AtlasAsset [...]". When reimporting the .atlas.txt, it seems to just silently fail. The atlas asset seems to not get created.

I updated initially to get a newer version of the Timeline package, which did seemingly fix my issue of pre-existing SkeletonAnimation tracks not loading correctly. But now I'm obviously stuck at this.

Misaki

AnduoGames The main reasons for this error are explained in the FAQ section of the Spine-Unity runtime documentation, so please check there first: https://esotericsoftware.com/spine-unity-faq#Import
If the issue persists even after following the troubleshooting steps provided there, please email us the skeleton data file that is causing the error: contact@esotericsoftware.com

AnduoGames

Misaki As mentioned, the imports worked before with 4.3.85. I am upgrading a large already released project from 4.2 to 4.3. I re-exported our spine files with the 4.3 Spine program. With 4.3.85, the import worked perfectly. With 4.3.86 I'm getting the above mentioned issue. I don't think it's a problem with the files. All of our spine files show the same error, it's not any single one having an issue.

Misaki

AnduoGames I was unable to reproduce the atlas error you mentioned after importing the Spineboy skeleton data files (.json, .atlas.txt and .png files) exported from the latest Spine Editor into a Unity project with the latest spine-unity runtime installed. Could you please create a minimal Unity project that reproduces the problem and send it to us via email?: contact@esotericsoftware.com
Please include the URL of this forum thread in the email so we know the context. Then we can take a look at what's wrong.

AnduoGames

Misaki Sorry, it seems like all that was needed was a unity restart afterall... The files import fine again now.

There is another issue I'm seeing since updating to 4.3, which is the physics jittering, you can see it here: https://gofile.io/d/ZCnNy1

We're moving the parent of the gameobject containing the SkeletonAnimation & SkeletonRenderer components.

Misaki

AnduoGames I'm glad the import issue was resolved!

I watched the video, but it's difficult to determine the cause based on the video alone. There have been quite a few changes between versions 4.2 and 4.3, so simply watching the video doesn't tell us whether all the necessary upgrade steps have been completed in your Unity project.

We would appreciate it if you could email us a minimal Unity project that reproduces the issue.

chris-mightier

Hi, I'm migrating from Spine 4.1 (42635d2a8f) to Spine 4.3 (b817346a57). I've tried running the migration steps twice, including the split component steps. I'm fairly confident I'm encountering a bug, but hopefully I've missed something.

Primary question: does a SkeletonMecanim + SkeletonRenderer require a valid 4.3 assigned SkeletonDataAsset for the migration to succeed?

After migration, opening my prefab results in a null reference in Unity Editor:

NullReferenceException: Object reference not set to an instance of an object
Spine.Unity.SkeletonMecanim+MecanimTranslator.GatherAnimatorState () (at ./Packages/com.esotericsoftware.spine.spine-unity@b817346a57/Runtime/spine-unity/Components/SkeletonMecanim.cs:367)
Spine.Unity.SkeletonMecanim.MainThreadBeforeUpdateInternal () (at ./Packages/com.esotericsoftware.spine.spine-unity@b817346a57/Runtime/spine-unity/Components/SkeletonMecanim.cs:91)
Spine.Unity.SkeletonAnimationBase.Update (System.Single deltaTime) (at ./Packages/com.esotericsoftware.spine.spine-unity@b817346a57/Runtime/spine-unity/Components/Base/SkeletonAnimationBase.cs:511)
Spine.Unity.SkeletonAnimationBase.Update () (at ./Packages/com.esotericsoftware.spine.spine-unity@b817346a57/Runtime/spine-unity/Components/Base/SkeletonAnimationBase.cs:393)

I've made sure to save the prefab with both components added, and I've tried restarting the editor as well.

Best I can tell, this appears to stem from having no SkeletonDataAsset assigned to the SkeletonRenderer during the migration. SkeletonMecanim.UpgradeTo43() seems to implicitly require it for the translator creation. But possibly I've gone down the wrong track here.

Further detail on my end: this prefab's SkeletonDataAsset is assigned at runtime. The following code was use with Spine 4.1 to achieve this:
skeletonMecanim.skeletonDataAsset = def.spineSkeleton; skeletonMecanim.Initialize(overwrite: true);
Screenshot of how I have the prefab configured:

Any guidance would be appreciated, thanks!

Harald

@chris-mightier Sorry for the troubles, and thanks for reporting! This has indeed been an oversight. We've improved auto-upgrade robustness in several spots which should cover your case, among others (in this commit).

A new spine-unity unitypackage is available for download:
https://esotericsoftware.com/spine-unity-download
Please let us know whether your issues are resolved by this update.

chris-mightier

Harald Just ran the steps again: the issue has been resolved with commit de14116488. Null reference no longer occurs when opening the prefab.Thanks!

« Page précédente Page suivante »