Looking great! I was wondering if Spine skeletons will be supporting IK in realtime as well, where IK targets can be positioned dynamically? As it is done in the Spine editor, I'm sure this could also be done inside a runtime?

The background was done by a freelance artist, the rest was done by myself. I'm not an artist really, but I think it turned out pretty decent.

Hi Nate,

thanks for your reply. The 1.2 version is available now, which should fix this issue!

[Promo 1]
http://www.youtube.com/watch?v=qTdPtJconx0

[Promo 2]
https://www.facebook.com/photo.php?v=62 ... =2&theater

Clear the path for a gnome on the run! How far can you go?

 Loading Image

[Android]
https://play.google.com/store/apps/deta ... wd.ohgnome

[iOS]
Currently in review status

[Facebook]
https://www.facebook.com/OhGnomePlayers

Spine and Box2d with some ragdoll physics!

Started with the SpineBoy example, deleted the jump and head animations, leaving only the walk animation. When exporting to binary and trying to setup the skeleton in libGDX, it fails with the following error

Exception in thread "LWJGL Application" java.lang.IndexOutOfBoundsException: index can't be >= size: 3 >= 1
at com.badlogic.gdx.utils.Array.get(Array.java:127)
at com.esotericsoftware.spine.SkeletonBinary.readAnimation(SkeletonBinary.java:311)
at com.esotericsoftware.spine.SkeletonBinary.readSkeletonData(SkeletonBinary.java:157)
at com.x.y.Main.init(Main.java:541)
at com.x.y.Main.render(Main.java:161)
at com.badlogic.gdx.backends.lwjgl.LwjglApplication.mainLoop(LwjglApplication.java:208)
at com.badlogic.gdx.backends.lwjgl.LwjglApplication$1.run(LwjglApplication.java:115)

Seems like the number of animations isn't properly updated. Using JSON, it works like expected.

Something goes wrong in the JSON export when scaling bones.

With XY scale 1.0 on the pelvis bone, it outputs

"bones": [
{ "name": "root" },
{ "name": "hip", "parent": "root", "x": 15.57, "y": 115.73 },
{ "name": "left upper leg", "parent": "hip", "length": 50.39, "x": 9.8, "y": 1.12, "rotation": -89.09 },
{ "name": "pelvis", "parent": "hip", "x": 1.41, "y": -6.57 },

With XY scale != 1.0 on the pelvis bone (.92 in this case, [edit: also for 2.5]), it outputs

"bones": [
{ "name": "root" },
{ "name": "hip", "parent": "root", "x": 15.57, "y": 115.73 },
{ "name": "left upper leg", "parent": "hip", "length": 50.39, "x": 9.8, "y": 1.12, "rotation": -89.09 },
{ "name": "pelvis", "parent": "hip", "x": 1.41, "y": -6.57, "scaleX": 1.412, "scaleY": -6.579 },

It seems like it's writing the x, y values to the scaleX, scaleY values

[EDIT]
Sorry, just found this topic on the same bug
viewtopic.php?f=9&t=2179