• Editor

  • Properly exporting data

    inglés

Hey,

I just started experimenting around in spine and I have two questions about exporting data. I made a very simple skeleton, added some pictures to it and made a "walk" animation. Just to test Spine. Now when I export the binary it creates a .skel file but not the .anim files. Do I need to select something in Spine itself?
(Same goes if I want to export the .json files. The model itself gets exported but not the animations as shown in Nates example here: https://github.com/EsotericSoftware/spi ... n.java#L36

The second question is about the TextureAtlas. Is it enough if I just throw all the texture-parts I used for my model into the texture packer and let it do it's magic? Will LibGDX know what texture belongs to what bone?

Thanks in advance 🙂

Related Discussions
...

The attachments are mapped by the filename (without the extension). Loading is deferred to an attachmentloader and the atlasattachmentloader looks in the atlas for a region named 'filename'.

I wrote an attachment loader for my own engine that looks in an atlas (if one exists) and then searches the FileSystem for the attachment name + an extension {png, jpg, psd, etc..}

Okay so the assets names are the same in the atlas as in the skeleton file.
What about the animation exports?

When I export my project as .json it only creates a "skeleton.json" file and completely ignores my three animations I have.

Spine used to have separate skeleton and animation files. Now the single file exported has both.

Nate escribió

Spine used to have separate skeleton and animation files. Now the single file exported has both.

oh...okay. I assume that this documentation: http://software-workshop.eu/content/spi ... et-started is out of date then. Can you maybe point me to an example to get my started in libgdx then? The documentation on the spine website is only about how to get stuff done in spine itself, not how to go from there :/

Aye, sorry there aren't docs yet. That article is slightly outdated, but everything is pretty much the same except there is just one file. Use skeleton findAnimation to get an animation instance. Your best bet is to go through the examples in spine-libgdx.

Nate escribió

Aye, sorry there aren't docs yet. That article is slightly outdated, but everything is pretty much the same except there is just one file. Use skeleton findAnimation to get an animation instance. Your best bet is to go through the examples in spine-libgdx.

Good morning 😉
Yea I just did that. The examples are actually pretty straight forward. I now have my poorly drawn character and an even worsely (if thats a word) done walking animation on loop in the game 😛 However I have a problem:

		Bone root = skel.getRootBone();
		root.setX(400);
		root.setY(400);
		root.setScaleX(1f);
		root.setScaleY(1f);

Is supposde to set up the skeleton on the screen and scale. The scale takes effect, the positioning is however being ignored. The character just ends up in the bottom left corner all the time:

The same goes for your code snipped from the example:

		Bone root = skeleton.getRootBone();
		float x = root.getX() + 160 * Gdx.graphics.getDeltaTime() * (skeleton.getFlipX() ? -1 : 1);
		if (x > Gdx.graphics.getWidth()) skeleton.setFlipX(true);
		if (x < 0) skeleton.setFlipX(false);
		root.setX(x);

This should move the character and bounce him around when he hits the end of the screen, right? Well that doesn't do anything either 🙁 The character just stays in the bottom left corner for some reason.

Do you know what could be going wrong here? is this a known issue?

Likely you have keyed the root bone. This means the animation will set the root bone position when you apply it. I will be making some changes to have the skeleton is positioned, but for now you can just avoid keying the root bone if you use it for placement, or position the root bone after applying an animation.

Ah, thank you! I keyed the root bone to make the robot bounce up and down a little as he was walking and also used it to make him jump. Changed the animations a little and now it works like a charm 🙂 Thanks!