Rotation Value in .json

Math

I have commented on this subject here
http://en.esotericsoftware.com/forum/Spine-rotation-not-same-in-editor-runtime-6775?p=31212&hilit=rotation+cocos#p31212

If you type -90 as an angle in the editor, Spine will correct it for 270.
But the number that will be exported in the json will be -90.
This brakes some animations when importing in Cocos.

BinaryCats

what if you do -190? Spine (c# c++) works with angles -180 to 180, rather than 0 to 360

Math

I don't know how it works behind the interface.
What's displayed on the UI, in the transformation panel's entry box for rotation are values from 0 to 359.

-190 would display 170.
-400 would be 320.

But the exported number in the json is the one typed and not the corrected one.

BinaryCats

I know it would display 170, but in the json it too would show 170(because its -180 to 180) what I'm saying is that the json showing -90 is correct, its more likely the codebase is bugged rather than json

Math

What ever value is entered, it will be the one found in the json.

Although -412 is displayed as 308 in Spine.
The exported json has -412 as its value.

BinaryCats

but the runtime shouldwrap that angle

Math

It should but software like Cocos don't use rotations like that.

A value like 720 is viewed as 2 complete turns if the previous position was 0.
If position A is -170 and B 170: Spine sees a 20 degree rotation and Cocos a 340 one.
If position A is 190 and B 170: Spine sees a 20 degree rotation and so does Cocos.

I guess this is more an importation problem for those kind of platform.
Either that or the Spine team could come up with an export that works with that kind of logic.

Nate

Interesting find, thanks. We've fixed the editor in 3.6.06-beta so it doesn't write bone rotations outside the -180 to 180 range.