raaan127

Hello, I'd like to report a bug.
If you rename a bone which having a slot with same name, with option Rename slot checked, to a name that a slot with that name are already exist, you will succesfully rename them and end up getting 2 slots with same name (which, I guess, should not be done)
slotname1.jpg

slotname2.jpg

slotname3.jpg


With the same step as above, having more than 2 slots that share the same name is also doable
I found it in spine 3.8.99, the same result when I use latest spine (4.0.33)
Yet, I don't know if this cause any problem (I've just found it, never tested if there is problem).
이 게시글에 첨부된 파일을 보기위한 권한을 요청할 수 없습니다.
사용자 아바타
raaan127
  • 전체글: 21

Nate

It does cause problems! Thanks for letting us know, we'll get it fixed ASAP!
사용자 아바타
Nate

Nate
  • 전체글: 11386

raaan127

Nate 작성:It does cause problems! Thanks for letting us know, we'll get it fixed ASAP!
Hello, I just found another bug in editor.
We've been discussed about orange key when import animation to a skeleton with slot in a different bone (which reported on this thread).

I found a kind of similar bug with constraint: when using pencil icon to change target bone in a transform constraint, if there is constraint key, it won't be remove or transfer to the new target bone but kept in the former bone, which result a behavior similar to a weird orange key.
사용자 아바타
raaan127
  • 전체글: 21

Nate

Good find! We've fixed it in 4.0.39. It's really nice to get data integrity problems like this fixed. :sogood:
사용자 아바타
Nate

Nate
  • 전체글: 11386


다시 돌아감: Bugs