• Runtimes
  • [Unity] Region not found in atlas error

Related Discussions
...

Hi,

I regularly get the following error when setting up the skeletons in Unity.

Error reading skeleton JSON file for skeleton data asset: [asset name]
Region not found in atlas: [region name] (region)
  at Spine.AtlasAttachmentLoader.NewAttachment (Spine.Skin skin, AttachmentType type, System.String name) [0x0002c] in [application path]/spine-csharp/Attachments/AtlasAttachmentLoader.cs:49 
  at Spine.SkeletonJson.ReadAttachment (Spine.Skin skin, System.String name, System.Collections.Generic.Dictionary`2 map) [0x0005a] in [application path]/spine-csharp/SkeletonJson.cs:202 
  at Spine.SkeletonJson.ReadSkeletonData (System.IO.TextReader reader) [0x003ae] in[application path]/spine-csharp/SkeletonJson.cs:160 
  at SkeletonDataAsset.GetSkeletonData (Boolean quiet) [0x000a9] in [application path]/spine-unity/SkeletonDataAsset.cs:82 
UnityEngine.Debug:Log(Object, Object)
SkeletonDataAsset:GetSkeletonData(Boolean) (at Assets/Spine/spine-unity/SkeletonDataAsset.cs:85)
SkeletonComponent:Update() (at Assets/Spine/spine-unity/SkeletonComponent.cs:120)

Is this something on my end (Unity) or something the artist may be doing ?

Thanks.

If you look in the .atlas file, do you see an entry for the region it says it can't find?

10 天 后

Hi, sorry for the delay.

No I don't. I suspect it's an issue with exporting, but we can't seem to reproduce it, it just happens.

20 天 后

Maybe it was a problem when an attachment has the path field set. The runtimes haven't yet been updated to use the path field, they only use the names. This would cause it to work in Spine but not in the runtimes. Recently a bug was fixed where the path was being set when it shouldn't.

5 年 后

FYI For future reference, we were running into this issue if we had "flatten paths" checked in Spine export options. This made the paths not get into Atlas properly.

2 年 后

+1 for unchecking 'flatten paths'.