Eriic520

Hi, I'm having this problem: I found an 'Attempt Reimport' button on the Inspector panel of the skeletondata files after I imported my spine animations into Unity.

My Spine-Unity Runtime version is 3.7 released on Mar.20, and my Unity version is 2018.3.9f1.

As this problem, I can't create SkeletonAnimation in Unity now. But strangely, among all the spine files, there's one not having this issue after imported whereas all of the rest are, while I don't see or make any difference between the settings of its and others'.

Is there anyone who has the experience in this issue? I really need this help. Thank you all. :)
Eriic520
  • Сообщения: 3

Harald

We are very sorry for the inconvenience. Could you please provide more information about the export of files - whether you exported everything at once, or exported one or multiple separate atlas pages manually, etc. Also knowing how many atlas pages (i.e. how many png files) were exported would be important to know.

Could you please create a zip package of the Spine files that are causing problems and send them to contact@esotericsoftware.com, that would speed up the resolution process by a large extent.

We have recently discovered a problem with export of multiple atlas pages, Nate has already fixed this problem, it will be released in form of a Spine editor update soon, so we hope that you encountered this exact problem which will be fixed soon.
Аватара пользователя
Harald

Harri
  • Сообщения: 1028

Eriic520

Thanks Harald. We're not using multiple pages and we didn't export at once. There are only 3 files exported from each spine animation: *.json, *.png, *.atlas.txt. And each spine animation only exports 1 png file. So I suppose we don't have the situations as you asked.

Anyway, I'm sending all the files by email. Hoping it could be followed up and fixed soon. And also, we'll try the update.

Thanks again for your reply. It's really important for us.
Eriic520
  • Сообщения: 3

Harald

There was actually a bug in the importer in the spine-unity runtime - I have now fixed it and uploaded a new unitypackage.
You can download it from here as usual:
Spine Unity Download

After importing the new unitypackage you might either need to select the parent folder of your assets, then right-click and select 'Reimport'. If this should not be sufficient, delete the SkeletonData file, then reimport the directory.

Please let me know if this solves your problem.
Аватара пользователя
Harald

Harri
  • Сообщения: 1028

Eriic520

Thanks so much, Harald. There's no more 'Attempt Reimport' button now D
Eriic520
  • Сообщения: 3

Harald

Great to hear. Thanks for letting us know.
Аватара пользователя
Harald

Harri
  • Сообщения: 1028

slothwerks

(edited from previous description)

I was upgrading to the Spine Unity 3.7 runtime today with Unity 2018.1.6 and ran into this exact same(?) issue, and the delete / reimport suggestion temporarily solves it - I can add the animation to my scene and it works fine. However, when I save and exit the project, the Attempt Reimport button re-appears when I relaunch it.

The only thing in the project that I can imagine might have some side effects that cause a behavior like this is that I'm using asset bundles, though I've made sure to rebuild the asset bundles after fixing the reimport issue.

The same issue does not happen with a brand new project and the same Spine animation, so presumably the issue is project specific, though I can't imagine how. When I launch, there are no Spine related errors in the console. Are there any other debug logs that Spine might emit that might shed light on what's going on?
slothwerks
  • Сообщения: 7

Harald

Have you been following the 3.6 to 3.7 upgrade guide by Pharan?
Spine-Unity 3.6 to 3.7 Upgrade Guide

Which versions of the Spine Editor and the Spine-Unity runtime are you using?
Аватара пользователя
Harald

Harri
  • Сообщения: 1028

slothwerks

Harald писал(а):Have you been following the 3.6 to 3.7 upgrade guide by Pharan?
Spine-Unity 3.6 to 3.7 Upgrade Guide
I'd read that guide, though I'll admit that I didn't notice the first step (starting in a blank scene) which seems like it was important in my case. I'd been more focused on the other changes listed. Properly following the documentation this time around appears to have resolved the issue. Sorry for the confusion!
slothwerks
  • Сообщения: 7

Harald

Great to hear that the issue could be resolved, thanks for letting us know!
Аватара пользователя
Harald

Harri
  • Сообщения: 1028


Вернуться в Runtimes