I keep getting "Could not automatically set the AtlasAsset "

tawak3500

Hey. So for some reason my updated spine files aren't working in Unity anymore. Older versions iteration were working perfectly but now I'm getting this (see attachment).

Thank you

tawak3500

Pharan

This happens when the filenames aren't predictable by the Spine editor utilities in Unity. (eg, when the filenames don't match, or there are missing stuff.)

Can you check if the filenames/file extensions in your export folder aren't weird?
Did you make sure to set the extension of your atlas exports as ".atlas.txt"?
Which version of Unity are you using?

tawak3500

I'm using version 2017.1.0f3

The files are:
skin.atlas.txt
skin.json
skin.png

I don't understand because the older version was working perfectly.

Thanks in advance.

I believe I figured it out. Apparently if there is a png that is completely or very close to being empty, it gives me an error. I had to make certain layers empty because certain skins had different sorting. I just left 1 pixel of 3% opacity and that did the trick.

DarkSlash

There's no answer for this? I have the same issue and I checked what Pharan suggest and is alright. How can I solve this?

Harald

You have just resurrected a very old thread. Pharan seems to have missed the last posting above.

Which versions of the Spine Editor and Spine-Unity runtime are you using? Did you reexport every asset and stick to the upgrade guide by Pharan: Spine-Unity 3.6 to 3.7 Upgrade Guide?
Have you tried selecting the respective folder and selecting Reimport in the context-menu?

If the problem persists, can you send us the respective assets to contact@esotericsoftware.com, then we can have a look.

DarkSlash

Well, I found the solution. The region was attached to a missing image. As Im a developer and have no access to Spine, I edited the json file, and erased everything related to that region and worked perfectly! also the animator is going to remove it on the spine file just to leave everything clean.

Harald

Glad you could resolve this, thanks for letting us know!

hamcha

For those who encounter the same issue in the future, I resolved it by unchecking (Export > Pack Settings > Flatten Paths)