images breaking export

BinaryCats

I suspect you will need the project file for this, but I will do my best to explain what happens and what I have done.

We have a problem with spine export and unity, although I suspect the issue is todo with the spine editor.

we are running spine 3.5.36

When we export a character, there is no error messages. however. when we open unity we get this message

Error reading skeleton JSON file for SkeletonData asset: Zombie_SkeletonData
Error reading attachment: torso_damage, skin: wakeup
  at Spine.SkeletonJson.ReadSkeletonData (System.IO.TextReader reader) [0x00b4d] in C:\Projects\unityproject\Unity\Assets\spine-csharp\SkeletonJson.cs:256 
  at Spine.Unity.SkeletonDataAsset.ReadSkeletonData (System.String text, AttachmentLoader attachmentLoader, Single scale) [0x00017] in C:\Projects\unityproject\Unity\Assets\Spine\spine-unity\SkeletonDataAsset.cs:195 
  at Spine.Unity.SkeletonDataAsset.GetSkeletonData (Boolean quiet) [0x000e6] in C:\Projects\unityproject\Unity\Assets\Spine\spine-unity\SkeletonDataAsset.cs:150 
UnityEngine.Debug:LogError(Object, Object)
Spine.Unity.SkeletonDataAsset:GetSkeletonData(Boolean) (at Assets/Spine/spine-unity/SkeletonDataAsset.cs:154)
Spine.Unity.SkeletonRenderer:Initialize(Boolean) (at Assets/Spine/spine-unity/SkeletonRenderer.cs:204)
Spine.Unity.SkeletonRenderer:Awake() (at Assets/Spine/spine-unity/SkeletonRenderer.cs:160)

diffing the old json and newly exported json it shows that the attachment does not exist in the new json. it just didn't export it.

Our higherarchy in spine looks like this (up until the problem attachment)
Loading Image

Changing the path of this attachment to another skin exports correctly . i.e. changing it from wakeup/torso_damage to other/torsodamage

Deleting the attachment exports correctly (not an option) (errors on a different attachment)

however:

Deleting the attachement, dragging the same image into the skeleton from the images node, does not export correctly - regardless to where this image is dragged to in the hierarchy of the skeleton.

Changing it from a mesh to an image does not export correctly.

changing the filename of the source image and dragging a new one in, does not export correctly,

duplicating a working image, then replacing it (copy paste broken image in photoshop) then saving it to a new filename, dragging into the hierarchy does not export correctly. (we where thinking it was some strange png setting or something)

any thoughts?

we might be able to send some form of project to you if you think it will help??

Nate

It seems there may be some inconsistency in your project. Eg, an attachment has the wrong parent or skeleton or is somehow orphaned. Some related bugs have been fixed in 3.6. If you can send your project, we can investigate. If it is inconsistency, hopefully we can add code in future version to fix up the problem and send you back a fixed project for the current version you are using.

BinaryCats

Ill send the file over to you now via pm, would be good to know what is causing this or how to resolve it on our end if its possible. it has happened a few times now, luckily in the past it has happened on images that where no longer used so we could just delete them, but now its spead to used images 🙁

hi, was there any updates with this issue?

Nate

Oh, sorry, I don't check PMs. Normally it's not even possible to PM me, but you have mod permissions. contact@esotericsoftware.com is always best.

I opened with 3.6.28-beta and I don't see Spine doing any clean up on project load, plus when it does that it should display a warning. I checked every attachment in the project (using code, so would find any that might somehow be orphaned) and none have the name "torso_damage". Is this the right project?

I exported the project with 3.6.28-beta without warnings and loaded it in Skeleton Viewer just fine. Is there a way for me to see the problem in SV?

Your exception looks odd. If ReadAttachment threw an exception, why is it not shown in the log? Please don't tell me Unity doesn't show the parent exceptions! :bang: Also, the project you sent is "WakeupZombie" while your log says "Zombie_SkeletonData". Sure it's the right one?

BinaryCats

Oh, sorry, I don't check PMs. Normally it's not even possible to PM me, but you have mod permissions. contact@esotericsoftware.com is always best.[/quote]
Noted

Nate escribió
name "torso_damage". Is this the right project?

Oh sorry, some of my tests to get this working seemed to have slipped in. I renamed the placeholder to torso_damageaaa and the attachment to wakeup/torsoWork
Loading Image This is one of the attachments that breaks

Nate escribió
I exported the project with 3.6.28-beta without warnings and loaded it in Skeleton Viewer just fine. Is there a way for me to see the problem in SV?

We foundout that our artist decided to update spine to 3.5.44 without telling us :headbang: . I have exported the spine file on this version, and it still does not work in unity. Skeletonviewer on the otherhand works just fine. Dare i say it Could this be pharans fault, and the unity importer can get broken?

Nate escribió
Your exception looks odd. If ReadAttachment threw an exception, why is it not shown in the log? Please don't tell me Unity doesn't show the parent exceptions

Im not sure about this

Nate escribió
Also, the project you sent is "WakeupZombie" while your log says "Zombie_SkeletonData". Sure it's the right one?

I was omitting some data (filenames and such) from the log, it is the correct file

:tmi:

ok... Im not sure how this has started happening. but it seems to be working again :tmi: :sweat: :sweat: . yesterday I exported the json on 3.5.44, and it wasn't working... honest.

This morning I re-export. But I look at the _skeletonData object. It was linked to the wrong atlas file. this was strange, so I exported again, ensuring I waited for the packing. Clicked unity and it was now linked to the correct atlas file. (our atlas files will be VERY similar, because its from duplicated skeletons)

This is an issue that keeps happening, where the linked atlas changes for no reason. we look at the commit and it will be a 3d artist who has no concept of spine or unity, but the log will say that he changed the linked atlas - I.e. something in unity is doing it.

atleast it is sorted, for now.

Thanks for your time

Mantic

I think I just experienced this with 3.7.24-beta-cpp with UE4 4.20.1. Every time I tried loading the -data file in the SpineSkeletonAnimation component, it kept saying "Error reading attachment: attack". Same as with OP, I would delete that attachment and the error would continue to the next one. I realized I had "flatten paths" enabled on the Texture Packer Settings. Turning that off solved the problem for me.