Skip to content
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

Loading spine assets from atlas #45

Open
lukz opened this issue Mar 27, 2017 · 3 comments
Open

Loading spine assets from atlas #45

lukz opened this issue Mar 27, 2017 · 3 comments
Labels

Comments

@lukz
Copy link

lukz commented Mar 27, 2017

Hi!

Is there any way to point to other atlas as source of assets for skeleton while loading skeleton?

@AleBles
Copy link
Member

AleBles commented Mar 30, 2017

At the moment, no. It'll only (dynamicly) include the image files defined in the .atlas.

Any suggestion in a different set of loading? I assume you'd prefer to have the spine included in atlas file that has more sprite available than just the spine ones?

@lukz
Copy link
Author

lukz commented Mar 30, 2017

Yup you're right. It can help reducing load time and with optimization (less texture bindings). Also current way is problematic for webpack as by default it changes filenames to hashes and currently plugin is trying to load png and atlas files of the same filename.

I would like to be able to specify atlas key containing those images (and other) while loading skeleton json file.

@AleBles AleBles added this to To Do in Implement Spine-TS Aug 18, 2017
@AleBles AleBles removed this from To Do in Implement Spine-TS Aug 21, 2017
@AleBles AleBles added the v3 label Aug 21, 2017
@KidScripty
Copy link

Has this ability been implemented yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants