Skeleton Viewer uses the spine-libgdx runtime, which is the reference Spine runtime upon which all others are based. It is very similar to the Preview view and can be useful for testing how skeleton data exported from Spine is rendered using a Spine Runtime. Unitypackage to re-activate the deprecated feature in its old form can be downloaded here:Ĭomplete Spine 3. Skeleton Viewer is an example tool that loads and displays skeleton data. So unfortunately we have to do some more work to include the features in the official 3.7 branch, all I can do for you is offer you a package made especially for you that reactivates the deprecated feature: It turns out that released the part you have been using only under his 'experimental' git repository only, the official Spine unitypackages have been using an updated version which has the mentioned menu entry SpineAnimationTrack removed and the other two entries updated in functionality. I will very soon provide you with an updated unitypackage which should restore the old desired behaviour! I have found the cause of the problem - there were some missing files that have not made it into the repository and thus were missing in later automatically created unitypackages. I have created a ticked for the issue here: Unity Timeline Editor error You could select the clip in the Timeline and then in the Inspector set the parameter Template-Animation Reference to your desired asset.Ĭould you please describe what your previous workflow was, how you added the "SpineAnimationTrack" etc, and create a screenshot of the elements in your Timeline Editor window?Ĭould you please also tell me which version of the 3.6 unitypackage you have been using? This would help a lot as well! The error you described is due to clipData.animationReference being null, so in the Timeline Editor window when adding a clip to the SpineAnimationStateTrack this clip is set to null and then dereferenced - I will fix this bug, it should not be issued (but can be ignored rather safely). It seems as if I can reproduce the problem and error message you are describing when using the 3.6 unitypackage spine-unity-3_6-, so it seems to not to be related to 3.7 upgrade but some other changes that seem to have affected both branches. Please do not yet replace or redo any of your work! I am having a look at the issue and it seems to be independent of 3.6 vs 3.7 changes.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |