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

Transform inheritance clarification

tony

I'm using spine-c version 2.1, because the QML integration was written using version 2.1, and 2.5 looks like it's changed too much to easily start using 2.5.

In the Spine editor I have unticked the boxes marked "Scale" under "Inherit" for all bones, and I can see when I export, that all the bones have a property: "transform" : "noScale". However, when I programatically change one bone's scale by manipulating the member variable scaleY, the transform is inherited. Also I can see a separate member variable of each bone called inheritScale, which is 1. Furthermore I can't see where the "transform" : "noScale" json propery ends up in spBone datastructure.

Is this an old bug that's been fixed, or am I misunderstanding something?

tony

Nate

If you are using 2.1 runtimes, you should use the 2.1 editor. Scale works differently than it used to.

Mario

Hi Tony. A LOT has happened since Spine 2.1. We are currently at version 3.6, and the runtimes (and bug fixes) have evolved accordingly.

I'm assuming you are using Spine Editor version 2.1.x as well? Are you using our official spine-c runtime or a fork for QML (we aren't involved in the QML integration, so lack knowledge there)? Could you give me a code sample of what you are trying to do? We generally don't support such super old versions anymore, but maybe I can take a look and nudge you in the right direction.

tony

I'm using Spine Editor 3.6 and it all seems to work ok, except for that one thing. It sounds like the .json file format has changed in that one regard, which would explain everything. I think the quickest fix looks like programatically setting inheritScale on all bones to be 0.

I actually tried integrating the 3.6 code with the QML plugin, and it looked like a bit of work (I thought it was 2.5 because the header in the source files states "Spine Runtimes Software License v2.5", so I guess it's the license that's 2.5 not the runtime? The zip from git file says version 3.6) I'm not sure which version of the spine-c library the QML plugin uses. At the top of the files it says "Spine Runtimes Software License Version 2.1", but is that a license version or a runtime version?

I think for now I'll stick with what I've got. But if I wanted to update the QML integration to the latest version, could I post a bunch of things I can't figure out? When I checked it out, there were around 100 compile errors, but a lot of it was repeated stuff, and some I could figure out by myself.

Nate

Those are license versions.

We try not to change the JSON or how things work, but sometimes we have to. You may be able to get away with using 3.6 with an older runtime, but it isn't supported and you will run into problems when you try using features that didn't exist back in 2.1 (paths, shear, etc).

Certainly, feel free to ask all the questions you like. 🙂