You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When a slot with the same name is under another bone, even the timeline of the parent bone of that slot seems to be imported into another bone. Also, if the X/Y of translate or scale for that bone is separated, the separation state will be imported for the bone with the same name, however the actual separating key itself will be imported for the bone with the slot of the same name, even though the X/Y separation option is not enabled. This causes the problem that you can have a translate-X or translate-Y key even though you do not have the X/Y separation option enabled.
Expected behavior:
Keys held by slots are imported for slots of the same name, but keys held by bones are always expected to be imported for bones of the same name.
Make sure that the bone named A has animation in this project.
Open ProjectB.spine.
From the Spine menu, select Import Project..., specify ProjectA.spine in the Project file path, and import the animation.
If you switch to animate mode and play back the imported animation, you will see that the animation that should have been imported into bone A is imported into bone B.
You can also see that the Translate option in the Separate section is unchecked in the properties displayed in the tree view, even though the bone B timeline shows translate X and translate Y as separate:
Looking at the properties of bone A, the Translate option is checked:
If you change the slot's parent to bone A in setup mode and then import the animation again, you will see that all the keys are imported to bone A.
The version of Spine in which this issue was found:
4.2.36
Description:
When a slot with the same name is under another bone, even the timeline of the parent bone of that slot seems to be imported into another bone. Also, if the X/Y of translate or scale for that bone is separated, the separation state will be imported for the bone with the same name, however the actual separating key itself will be imported for the bone with the slot of the same name, even though the X/Y separation option is not enabled. This causes the problem that you can have a translate-X or translate-Y key even though you do not have the X/Y separation option enabled.
Expected behavior:
Keys held by slots are imported for slots of the same name, but keys held by bones are always expected to be imported for bones of the same name.
Steps to reproduce:
ProjectA.spine
using Spine 4.2.36.A
has animation in this project.ProjectB.spine
.Import Project...
, specifyProjectA.spine
in theProject file
path, and import the animation.A
is imported into boneB
.You can also see that the
Translate
option in theSeparate
section is unchecked in the properties displayed in the tree view, even though the boneB
timeline shows translate X and translate Y as separate:Looking at the properties of bone
A
, theTranslate
option is checked:If you change the slot's parent to bone
A
in setup mode and then import the animation again, you will see that all the keys are imported to boneA
.The version of Spine in which this issue was found:
4.2.36
This issue was reported in the following thread on the forum:
https://esotericsoftware.com/forum/d/26786-4236%E7%89%88%E6%9C%AC%E8%AE%BE%E7%BD%AE%E5%85%B3%E9%94%AE%E5%B8%A7%E5%87%BA%E9%94%99%E5%92%8C%E5%8A%A8%E7%94%BB%E5%AF%BC%E5%85%A5%E5%87%BA%E9%94%99
The text was updated successfully, but these errors were encountered: