Ohai. Long time. Damn vacation :p
Alright...Yea I sat down a bit and tried to manually flip the bodies, read up about how stuff is usually flipped but then gave up after a while. No need to re-invent the wheel. The two aren't ideal. I'm not yet sure wether I'm gonna destroy and recreate the body or just keep two in memory. For that I'd have to know how resource intensive the game ends up being But thanks for the advice.

So I'm working with LibGDX and don't know how Corona handles stuff. But the fact that there is also a stage and it's a 2D gaming framework tells me that things can't be too different :p

My current setup is this:

LibGDX Screen

LibGDX Stage

LibGDX actor

Spine Skeleton

So the screen has a stage, to that stage I add actors and inside the actor I will import all the neccesary resources and do all the skeleton logic. When I'm done with a character I can simply call actor.dispose(); in my screen and get rid of it.
The only thing you should look out for that if you do remove the character from your stage to also dispose of all resources inside the character object that need disposition.

Hope this helped somewhat,
Kate

Alright, yea. The big "box" as a dynamic object with a certain mass so that light things won't knock it away as the kind of "carrier", and then take the coordinates of that box for the skeleton to which the collision boxes are being attached. Sounds doable.

Oh, another thing. Nate mentioned that I could just stop updating the attachment positions to let the physics take over. I tried to do that...
 Loading Image

Something tells me that I didn't do it right :p :c

About the flip....theoretically it's not difficult. Though I wouldn't know how to do it mathematically...

1. How do I flip the body in the world? And would I have to flip each attachment or does Box2D handle the entire thing as one object somewhere?

2. Well I'd already be content with simple gravity without a ragdoll effect: letting the character fall down statically when going over an edge. (If it's clear what I mean) Sort of let the entire skeleton be one object that gets affected by gravity.
   Jumps could be implemented by creating an animation that lets the character move in place (in Spine) and then apply a force in Box2D into a certain direction? Maybe, idk. I'm just thinking out loud here :p

Okay, I'll just edit this post because I hate double posting stuff :p I had some issues with getting Spine and Libgdx to work. The latest nightly has a bug that fails to read files. Had to take an old nightly and manually add the ObjectFloatMap class from the libgdx repository.

Now I reverse engineered the spine example into my own code and got it do work. Got the lovely boxes falling from the sky. However I'm getting a nullpointer when trying to read the animation (The animation feature was changed several times since the workshop. I lost my own animation files so I just wanted to use the Spineboy.

animation = skeletonData.findAnimation("walk");

seems to return null. So I just disabled the animation for now.

The guy just slithers across the floor, which is all nice and all but what I'd actually be interested in is how to make the skeleton interact with the boxes and gravity. You know, letting boxes bounce off his head and letting him fall down when not on the ground etc.

Is that even possible? :/ Because that'd be the thing I'm interested in. Also, if it is, I'd be interested how I would have to adjust my animation moves to not screw everything up with the gravity :o

Hmmm…I can't seem to have TextureAtlasAttachmentLoader or BoxAttachmentLoader
Can you maybe share your code? :o

//Edit:

Okay, so I updated to the latest Spine and LibGDX runtimes (and nightly builds) and now it includes all the methods I need, however the drawing gives me an out of bounds exception when creating the skeletonbinary O.o

What versions of libgdx and spine did you use? Also when I imported all the source files from spine into my project I had to fix quite a few errors (some of the variables didn't have public modifiers and demanded getters/ setters)

Wow, thanks. How did I not find that via google yet? O.o Well thanks :p

I'll be looking at the code, trying to fiddle the thing into my existing infrastructure. Maybe this can become kind of a discussion thread about the whole thing :p In case you have problems or (more likely) I have problems :')

Hey everybody,

after a rather long pause of not programming at all I've picked up my game again. I bought Spine a while ago and have experimented around with it for a bit. Now I started working with Box2D in LibGDX and saw that Spine also had a Box2D integration (according to the Kickstarter).

I'm kinda interested on how to get started (essentially how to tell Box2D about my character, letting gravity affect the attachments, etc.) and was searching for a documentation about it. But I couldn't find anything.

Is there anything I missed? Does somebody know a tutorial how to get started with Spine and Box2D or is there a documentation somewhere that I didn't find? Any help is highly appreciated

Thanks.

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!

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:
 Loading Image

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?

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 :/

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.

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