![]() ![]() That sounds like it could be the cause then as the example assets seem to be included with the runtime. The git repository is compatible with the 3.8-beta format changes (except the example asset updates), so if that is the problem, you could either wait one or two more days until the new unitypackage is out, or download it via github. Unfortunately the latest 3.8-beta spine-unity runtime unitypackage is not up to date with the latest Spine 3.8-beta export yet (the example assets need an update). Only the un-numbered Editor folder contains files ( SpineSettings.asset and ). Update: So I just killed Unity and looked in my Assets folder - it seems like there is some kind of loop going wrong somewhere? May be an issue/error on my or their side though. unitypackage anymore, so double clicking doesn't work. unitypackage using the Assets browser context menu (right click ->Import package or similar, I'd check but Unity still hangs □), as at least for me Unity 2019 downloaded through Unity Hub does not seem to associate. can the exported "2D" characters turn freely in 3D?Īlso, you may want to point out on that you can also import a. Would you recommend using Spine to animate 2D characters in a 3D world in Unity? (Think Paper Mario) Would there be any expected friction with this? Are Spine exported meshes double-sided, ie. Is that still correct (as there are references to Unity 2019 in the changelog)? If it is, what is the expected timeframe for Unity 2019 support? The latest Unity version listed as supported on is 2018.3b. In addition to that, I have a few questions: Also feel free to reach out via the email I registered with. If you need any more info for debugging, let me know here. ![]() I just tried importing the Spine Unity runtime into Unity, and the import hangs forever on the "Importing small assets" step. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |