Anyone know of issues with using CCObject::copy on CCSkeletonAnimation?
I am testing — right now my biggest slowdown is loading the same spine objects over and over!
Anyone know of issues with using CCObject::copy on CCSkeletonAnimation?
I am testing — right now my biggest slowdown is loading the same spine objects over and over!
Or — is there a way to tell the Spine extension to cache the JSON and Atlas?
Yes — you make SkeletonData and Atlas and you keep them around in an std::map.
It is easy. Just watch your destructors!
Huge performance gain for me