vladdrummer написалIt happens in a completely new project as well. Spine is in multiple places of Unity menu , so it's not just folders in Unity project
The scripts from these two folders add menu entries to Unity menus. If you delete the two directories, your menu entries will be gone as well. If you extract the spine-unity 3.8 unitypackge into a clean project, the included example scenes and skeleton assets in the Spine Examples
directory all match this runtime and work fine.
vladdrummer написалit absolutely doesn't and gives me "change runtime" even on a new project with 3.8 installed
Which asset provides this error message for you? We doubt that any of the included Spine Examples
assets causes this error message.
vladdrummer написалSo why official site gives me 3.8 examples that I cannot use?
The provided examples on Spine: Example Projects are Spine Editor 3.8+ projects compatible with the Spine Editor set to version 3.8 and newer. They are intended to be examples for the Spine Editor. There are pre-exported .json
and .skel
files included in each zip package, but they are exported for the current 4.0 version, which might have caused your problems. Also, the spine-unity runtime has the special requirement of all Spine runtimes that the .atlas
asset needs to have the extension .atlas.txt
, which is an unfortunate Unity requirement (described here). For runtime examples, we provide the examples alongside each runtime, which is setup to work out of the box without modification. I assume that this confusion of Example Project (for the Spine Editor) and runtime example assets has caused your troubles.
If you try to import a 4.0 skeleton asset with the spine-unity 3.8 runtime, it will tell you that you need to use spine-unity 4.0 to import it, or re-export your asset from the Spine Editor set to version 3.8.
vladdrummer написалI don't have Spine Editor, I just wanted to test this solution with Unity and it went horrible from the start.
Sorry to hear.
vladdrummer написалThis doc: spine-unity Runtime Documentation: Getting Started says "get latest release" and this page Spine: Example Projects , which is your site, contain stuff I can't use.
As described above, these projects are example Spine Editor projects, for you to inspect in the Spine Editor. The pre-exported assets in each zip package are for 4.0 runtimes, and for spine-unity they need the .atlas
asset renamed to .atlas.txt
. Also the included assets in the zip packages contain several versions of assets, ess and pro versions of a skeleton, .json
and binary .skel
files, PMA and straight alpha atlases. Then you can use them in spine-unity as normal. If you have already imported the skeleton file, but your .atlas.txt
file was misnamed to .atlas
, you need to delete the _SkeletonData
asset before reimporting to automatically assign the atlas asset at the _SkeletonData
asset (and avoid having to manually assign it).
vladdrummer написалWhy not making choose runtime version in Unity? If you don't like deprecation model and old versions doesn't work on a new runtime - why don't you let us choose runtime version with a dropdown?
All scripts and example assets in the spine-unity runtime need to be replaced, a "choose runtime version" on the Unity side would not make sense, it would just download the respective unitypackage.
vladdrummer написал
As far as I understood, there is no solution other than buying Spine Editor which I don't need and convert old models from your site?
It seems like you misunderstood the situation in two ways, please be sure to check out the first paragraph of the spine-unity documentation page:
Integrating an official Spine Runtime into your applications requires a valid Spine license, though you are welcome to use the Spine Runtimes for evaluation purposes.
So without purchasing a license of the Spine Editor you are not allowed to include the spine-unity runtime in your product. Spine Editor License Agreement
Secondly, as mentioned above, you could use the pre-exported 4.0 skeleton assets downloaded as example zip packages as well without upgrading them, you need to rename .atlas
to .atlas.txt
to use it with Unity.