Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Json Bone ID

BinaryCats

Hi,

How are bone ID's worked out. I understand that they are the order they appear in the JSON file, but how are they ordered from export. Will it always be ordered as it appears in spine?

by that I mean

root: 0
_Parenta: 1
__Childa: 2
_parentb: 3
__Childb: 4
____ChildChildb:5
_parentc: 6
_parentd: 7

Pharan

What's a bone ID?

I don't see it in Spine-libGDX, Spine-C or Spine-C#.

Are you sure that's not something you added yourself?

BinaryCats

apologies, bone id isn't bone id isn't official terminology. it is also the position in the ** bone list.

it is used in meshes, Verts are tied to an ID instead of a name in the json file. the format is "vertices": [ numbones, currentboneid, vertx, verty, weight...]

Pharan

Oh, you're talking about the bone indexes in Skeleton.bones array.
And you mean they're used in SkinnedMeshAttachments.

BinaryCats

Yes and yes

Nate

Bones are sorted so that parents always come before children and so constraint targets (IK and (in v3) transform constraints) always come before constrained bones. You can't rely on the order. To get a bone index, find it by name to get the bone, then find the index in the bone list. The bone list order will never change (the same is true for slots).

BinaryCats

Thanks, that's all I needed.

(We are dynamically blowing up skeletons, which create skeletons and needed to get the top level "locator bone" for an explosion to activate it, fun stuff! 🙂 )

Pharan

In case it's useful for anyone else:

Each Bone also has a Bone.parent.
Traversing that successively will eventually point to the root bone, where its .parent == null.