• Unity

  • Unity not importing atlases correctly anymore.

Related Discussions
...

Hello.

We've been having an annoying issue for several weeks now that we thought was a Unity problem at first, but keeps happening after updating anyways and seeing that nobody has posted about this, makes us think the problem is on our side.
We are on Unity 2020.1.0f1 and the latest Spine version.

Seems that Unity does not recognize atlas files anymore when you automatically import the atlas.txt, json, and png files.
You get this message:

Also, the console message when Unity tries to import the files is this one:

You can assign the atlas manually anyways, but we'd love to know what has gone wrong, because it makes the workflow very tedious when iterating fast.

Any help would be appreciated!
Thanks a lot.

6 days later

Oh dear, sorry for the trouble and thanks very much for reporting this issue!

While we officially don't support Unity 2020 yet, we will in the very near future as Unity 2020.1 just came out of beta, so any issue reports on Unity 2020.1 are very welcome, please don't suffer in silence for weeks.

I created an issue ticket for it here for you to subscribe:
[unity] Automatic asset import broken in Unity 2020.1 · #1727
We will let you know once the issue has been resolved.

This issue has just been fixed. This also fixes import problems when using Import Pipeline V2 in Unity 2019.X.

The updated 3.8 unitypackage is available for download here as usual:
Spine Unity Download: Download

Thanks for reporting!

Awesome, Harald! Thank you very much!

Thanks very much for reporting!

4 months later
Harald wrote

Thanks very much for reporting!

[UPDATE #2]
Ok I think I solved it. I'll leave it here for anyone else that runs into this problem.

1) Delete the Spine \ Spine Example folders

install new runtimes
2) Do not enable these export settings.

It worked for me. Not sure why. But I can get skins working finally. :detective:

[UPDATE #1]
I thought it was Skins related, but it might be a Spine 3.8 ~> Unity 2020.1 issue instead?

I tried exporting JSON and as a binary (renamed to .skel.bytes and still get the Missing Atlas error.) 🙁

I've attached the test PSD (with GIMP exported JSON) and the exported atlas files.

I'm wondering if the spine runtimes are conflicting with older versions? If we completely delete the Spine \Spine Examples folders, does it clean out the runtimes?

I get this red error in Unity

Error reading skeleton JSON file for SkeletonData asset: Prop_Truck_GIMP_SkeletonData
Error reading attachment: Truck, skin: SkinA
  at Spine.SkeletonJson.ReadSkeletonData (System.IO.TextReader reader) [0x00ec8] in C:\ProjectY\Assets\Spine\Runtime\spine-csharp\SkeletonJson.cs:315 
  at Spine.Unity.SkeletonDataAsset.ReadSkeletonData (System.String text, Spine.AttachmentLoader attachmentLoader, System.Single scale) [0x00014] in C:\ProjectY\Assets\Spine\Runtime\spine-unity\Asset Types\SkeletonDataAsset.cs:244 
  at Spine.Unity.SkeletonDataAsset.GetSkeletonData (System.Boolean quiet) [0x0009d] in C:\ProjectY\Assets\Spine\Runtime\spine-unity\Asset Types\SkeletonDataAsset.cs:170

Unity 2020.1.15f1 Test Project
https://www.dropbox.com/s/yheoqyd8y8bg5gg/New%20Unity%20Project.zip?dl=0

I followed this tutorial. Is there a newer method now?

Hi @[deleted]

I'm running into the same issues also. Please find the current installs.

Unity 2020.1.15f1
spine-unity 3.8 (updated 2020-12-09, changelog)
Spine 3.8.99 Pro

Am I missing anything else?

  • Resolve atlases

It will ask to browse, but cannot find the .asset file

  • stop import

will stop the import

  • Import without atlases

won't import anything.

I tried with SpineBoy and got the same error

Thanks for your help :wounded:

IndieDoroid wrote

It worked for me. Not sure why. But I can get skins working finally.

Glad to hear you've figured it out, thanks for letting us know!

If you enable Flatten Paths the folder names are removed from the attachment name:
Texture Packing - Spine User Guide: Options

"Flatten paths Subfolders are stripped from region file names. Image file names should be unique."

In case you mess things up in the Texture Packer Settings you can always revert to defaults via the defaults button, just don't forget to adjust the atlas extension to .atlas.txt again then.

IndieDoroid wrote

I'm wondering if the spine runtimes are conflicting with older versions? If we completely delete the Spine \Spine Examples folders, does it clean out the runtimes?

It depends on the version numbers of your spine-unity packages, upgrading from 3.7 to 3.8 or 4.0-beta will require you to delete the directories as described here:
spine-unity Runtime Documentation: Updating the spine unity Runtime
When upgrading patch version only (older 3.8 to newer 3.8 ), no leftover files should cause any problems.

Glad to hear you've figured it out, thanks for letting us know!

It was a stressful day of trial and error. But yea hope the thread helps others.

"Flatten paths Subfolders are stripped from region file names. Image file names should be unique."

I keep forgetting what this does. Does this have a mouse hover pop up? :wounded:

It depends on the version numbers of your spine-unity packages, upgrading from 3.7 to 3.8 or 4.0-beta will require you to delete the directories as described here:
spine-unity Runtime Documentation: Updating the spine unity Runtime
When upgrading patch version only (older 3.8 to newer 3.8), no leftover files should cause any problems.

Good to know! If we don't want to upgrade to 4.0... will we have that option? I can't bear the thought of dealing with more bugs. I'm in the middle of production now, any set back is likely to give me a heart attack now. :bigeye: :lol:

IndieDoroid wrote

I keep forgetting what this does. Does this have a mouse hover pop up?

Yes, it has a tooltip. As always, you can press F1 to display it immediately instead of waiting for it to appear.

IndieDoroid wrote

If we don't want to upgrade to 4.0... will we have that option?

Of course you don't have to upgrade from 3.8 to 4.0 if you don't want to 🙂. If I misunderstood your question there, please let me know.

Yes, it has a tooltip. As always, you can press F1 to display it immediately instead of waiting for it to appear.

Oh didn't know that was a thing! Thanks!

Of course you don't have to upgrade from 3.8 to 4.0 if you don't want to 🙂. If I misunderstood your question there, please let me know.

From what I understand, usually Spine auto updates when we boot up the application. :think: How can we stop the update to 4.0 whenever it gets an official release?

7 days later