spine-unity 下载地址

最新推荐文章于 2024-08-22 21:21:08 发布

鱼儿-1226

最新推荐文章于 2024-08-22 21:21:08 发布

阅读量2.6k

点赞数

分类专栏： spine 文章标签： spine runtime unity3D

本文链接：https://blog.csdn.net/qq_21743659/article/details/107236769

版权

spine 专栏收录该内容

19 篇文章 0 订阅

订阅专栏

http://zh.esotericsoftware.com/spine-unity-download/

spine-unity

Getting Started

Getting Started Documentation

Download

spine-unity 3.8

spine-unity Unity package

spine-unity 3.8 (updated 2020-05-29, changelog)
Compatible with Spine 3.8.x and Unity 2017.1-2019.3.

URP Shaders UPM package com.esotericsoftware.spine.urp-shaders

Unity 2019.3: spine.urp-shaders 3.8 (updated 2020-03-27)
Compatible with spine-unity 3.8 from 2019-12-20 or newer and Unity 2019.3.

LWRP Shaders UPM package com.esotericsoftware.spine.lwrp-shaders

Unity 2019.1: spine.lwrp-shaders 3.8 (updated 2020-03-27)
Compatible with spine-unity 3.8 and Unity 2019.1.
Unity 2019.2: spine.lwrp-shaders 3.8 (updated 2020-03-27)
Compatible with spine-unity 3.8 and Unity 2019.2.

Timeline Extensions UPM package com.esotericsoftware.spine.timeline

spine.timeline 3.8 (updated 2019-12-02)
Compatible with spine-unity 3.8 from 2019-10-3 or newer and Unity 2017.1-2019.3.

spine-unity 3.9-beta

spine-unity Unity package

spine-unity 3.9-beta (updated 2020-05-20, changelog)
Compatible with Spine 3.9.x and Unity 2017.1-2019.3.

URP Shaders UPM package com.esotericsoftware.spine.urp-shaders

Unity 2019.3: spine.urp-shaders 3.9-beta (updated 2020-03-27)
Compatible with spine-unity 3.9-beta from 2019-12-20 or newer and Unity 2019.3.

LWRP Shaders UPM package com.esotericsoftware.spine.lwrp-shaders

Unity 2019.1: spine.lwrp-shaders 3.9-beta (updated 2020-03-10)
Compatible with spine-unity 3.9-beta and Unity 2019.1.
Unity 2019.2: spine.lwrp-shaders 3.9-beta (updated 2020-03-10)
Compatible with spine-unity 3.9-beta and Unity 2019.2.

Timeline Extensions UPM package com.esotericsoftware.spine.timeline

spine.timeline 3.9-beta (updated 2020-01-10)
Compatible with spine-unity 3.9-beta from 2019-10-3 or newer and Unity 2017.1-2019.3.

Installing spine-unity in a new project

Create an empty Unity project.
Import the spine-unity.unitypackage you downloaded. (double-clicking on the unitypackage should open it in Unity).

If you are just getting started, there are more detailed steps in the documentation section on Getting Started.

Updating an existing project

As with Unity updates, it is always recommended that you back up your whole Unity project before performing an update.
Always check with your Lead Programmer and Technical Artist before updating your Spine runtime. Spine runtimes are source-available and designed to be user-modifiable based on varying project needs. Your project's Spine runtime may have been modified by your programmer. In this case, updating to the latest runtime also requires reapplying those modifications to the new version of the runtime.
Read the CHANGELOG.md file included in the downloaded unitypackage or on github. You can find the necessary documentation here when obsolete methods have been replaced with new counterparts.

In-place Update (.unitypackage)

Open your Unity project.
Import the .unitypackage into your existing project by double-clicking on the unitypackage file or dragging it into Unity editor Project view.
The Import dialog will show which files are updated and will update them regardless of where you moved them in your project since you last imported.

This functionality may not work correctly if your meta files were corrupted or replaced. In that case, you may have to do delete the old version of the runtime before importing the unitypackage.
Much older versions of the unitypackage had inconsistent meta files for spine-c#. You may have to delete the older spine-csharp folder when updating. This otherwise works correctly.
Occasionally, major refactoring involves removing or merging some files. Importing the .unitypackage will not delete those leftover files when you update so you may have to do that yourself. Check here for announcements regarding changed/leftover files: Noteworthy Spine Unity Topics

For more options, see the spine-unity documentation page section on updating.

Installing Extension UPM Packages

Download the Unity Package Manager (UPM) package via the download links above or find it in the spine-runtimes/spine-unity/Packages subdirectory on the git repository.
If you have your Unity project open, it is recommended to either a) close Unity or b) close any scene containing Spine components (e.g. by opening a new empty scene).
You can then either unzip (or copy if using git) the package to a) the Packages directory in your project where it will automatically be loaded, or b) to an arbitrary directory outside the Assets directory and then open Package Manager in Unity, select the + icon, choose Add package from disk.. and point it to the package.json file.
The Project panel should now show an entry for your package, e.g. Spine Lightweight RP Shaders under Packages. If the directory is not yet listed, you need to close and re-open Unity to have it display the directory and its contents.

Updating an existing UPM package

The same principles as updating the Spine Unity runtime apply.
As mentioned above, it is always recommended that you back up your whole Unity project before performing an update.

In-place Update (via .zip file or git)

If you have your Unity project open, it is recommended to either a) close Unity or b) close any scene containing Spine components (e.g. by opening a new empty scene).
Copy the content of the new UPM package zip file or git directory over the existing one. Depending on how you have installed the UPM package, this will be either the project_root/Packages/package_name directory in your project or the arbitrary directory outside the Assets directory from where you have loaded it via Add package from disk...
If you have closed Unity, open your project again in Unity.
Unity will import the new assets and display a loading progress bar.

Known Issues:

You cannot drag SkeletonData Assets into the Hierarchy view if it is empty. You will need to drag them into Scene View, or create an empty GameObject before dragging into Hierarchy view.

Unity Limitations:

Unity's physics components do not support dynamically assigned vertices so they cannot be used to mirror bone-weighted and deformed BoundingBoxAttachments. However, BoundingBoxAttachments' internal vertex data at runtime is still being deform correctly and can be used to perform hit detection with your own code.
UnityEngine.UI.MaskableGraphic does not support using more than one texture, so uses of SkeletonGraphic are limited to skeletons with only one atlas page/texture. At the cost of masking, an experimental version of SkeletonGraphic which splits it into multiple UI objects can be found here: spine-unity experimental SkeletonGraphicMultiObject 3.6 2018-04-19
Spine animations are not imported as Unity.AnimationClip objects. Unity uses a different curve scheme and the set of features do not overlap well with Spine's features. Instead, spine-unity animates using core C# Spine.Animation objects which retain all of Spine's animation features. This means a few conveniences may be absent, such as playing back animations in edit mode using the Animation panel.
Unity does not recognize arbitrary file types, so atlases need to be exported as .atlas.txt. Likewise, binary files need to be exported as .skel.bytes. For more information on importing Spine assets, see the documentation section on Getting Started
Unity has had a long-standing issue with multi-material/multi-submesh meshes, sorting and dynamic batching. If you have many duplicates of a skeleton that uses multiple materials, Unity's dynamic batching system will attempt to batch the similar materials but it breaks sorting within skeletons in the process of batching submeshes with similar materials. To work around this Unity bug, add a Sorting Group component to your Spine GameObject. However, it is still better for performance if your skeleton uses only one texture and material.

Compatibility

Runtimes cannot load exported binary file versions that are newer or older than the version it supports.
Json exports are more stable and have better chances of being compatible with future versions, but may still break.
If you want to avoid incompatibility issues with a set runtime version, you can choose a Spine editor version that matches that runtime specifically. This can be done in Spine's Settings... window.
For more information, see this forum topic.