Hello!
We're considering adding Spine to our production toolset/pipeline.
Doing some initial technical evaluation around spine-glfw example there was no success passing past json.readSkeletonDataFile(...). Apparently, it was not finding some 'region' data while executing RegionAttachment *AtlasAttachmentLoader::newRegionAttachment(...) in AtlasAttachmentLoader.cpp - exactly the 'crosshair' region.
Out of curiosity we tried other data files, like 'alien-ess.json', 'owl-pro.json' etc - but none worked ending with error string like 'Uneable to read skeleton file'.
Is the runtime example broken for the moment or maybe the sample data files provided are incompatible/obsolete?
Can I get any pointers, please?
Thanks in advance!
Best,
Val