New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sth about spine anim. #19154

Open
zcgit opened this Issue Nov 9, 2018 · 2 comments

Comments

Projects
None yet
4 participants
@zcgit
Copy link
Contributor

zcgit commented Nov 9, 2018

As I read the latest version code, I found the cocos always read and decode the skeletonJsonFile & atlasFile when load the spine animation. so if an animation is very complex , it will take a lot of IO and decoding time.
In fact, it always do 3 things when using a spine anim: 1.read skeletonJsonFile; 2.read atlasFile; 3.read the imageFile.
I wonder if we can separate the 3 things? just loading the config file(skeletonJsonFile & atlasFile) when we need, and then loading a png when we really want to use the spine anim.
In my real working situations I could load 30-50 and more spines' config files before we really use the spine anim. so it will make a good experience when you really want to use the spine which config file was loaded, because you just need to load a png file any more, and then you can also release the png and config files separately.

@zcgit zcgit changed the title sth about spine anim. sth. about spine anim. Nov 9, 2018

@zcgit zcgit changed the title sth. about spine anim. sth about spine anim. Nov 9, 2018

@zcgit

This comment has been minimized.

Copy link
Contributor

zcgit commented Nov 12, 2018

anyone check it out ? #19163

@drelaptop drelaptop added this to the next milestone Nov 12, 2018

@gestern

This comment has been minimized.

Copy link
Contributor

gestern commented Nov 12, 2018

If you keep all animations in a single atlas, then this is not a problem at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment