"Could not automatically set the AtlasAsset for" ...AGAIN!

mistermalte

Hey Spine-Team & Community,

I am trying to import to unity and get the above error message.

I know this is not a new problem, but I read through all solutions so far and still nothing worked for me. I have a single Spine Project that will always trigger this error, while all other projects can be imported to Unity without any problem.

Here is a short list of things I tried:

checked for the .atlas.txt expansion -> no mistake there
tried it with Unity 2020.1.4 AND Unity 2018.4.27 in a vanilla project -> same problem
tried to export other projects with the same settings -> all other projects worked fine
tried to resolve atlas manually -> it now says that all regions are missing.
checked the atlas.txt file -> all regions are there
tried the binary export -> same error
tried all kind of changes in export settings e.g. flatten path -> nothing worked
checked the log for the export -> it says it's all fine
tried the import on another Computer -> still the same problem

I thought, I might just upload the zipped project and maybe someone can take a look at it?
Unfortunately the exported png is bigger than 2 MB and I don't want to upload a split image as this could be a whole new source of problems ;-) so it is just the zipped Spine Project -> but I am pretty sure that the error must be found in there,

I am really thankful for any help.

Best wishes,
Malte

mistermalte

Jamez0r

I downloaded the project and opened it - the attachment called "machete case" wasn't properly linked to its source image (it showed a red box saying "Image Not Found"). I fixed the link by selecting the machete case attachment, and typing in "machete case" into the Image Path. It had said <machette case> in there originally, but something must have gotten messed up to cause it to lose the reference.

Then I exported the project, dragged all 3 files (puncher.atlas.txt, puncher.json, and puncher.png) into Unity, and it looked fine with no errors.

Is your Atlas Extension set to ".atlas.txt" in your Texture Packer Settings?

mistermalte

YESSS!
Thank you Jamez0r for your help - I could finally fix it - even though I don't understand the problem really - and I am pretty sure there is a Bug in there some where.

I also saw the red box in the first version our animator passed to me - but she managed to "fix" that somehow - but it seems the potential fix was just superficial. at least the "machete - case" - image was shown in Spine then..

But now I recreated the error by actually changing the external image file name by handfrom "machette case.png" to "machete case.png" (and so the red warning square appeared again) and then I also changed the Image path of the attachement to "machete case" just like you did and now the export finally worked.

Like I said - I think there is something wrong with naming errors not being recognized inside spine - but thanks to your approach I could at least fix my problem at least.

I heared a lot of good things about the spine community and it seems rightfully so.Thank you very much!

Harald

Thanks very much Jamez0r!

mistermalte ha scritto
I could finally fix it - even though I don't understand the problem really - and I am pretty sure there is a Bug in there some where.

Are you or your artist using a version control system? Perhaps some files have been renamed but not committed, leading to the "Image Not Found" issue?

Anyway, glad that the issue could be resolved! 🙂