Integer limit on JSON

Xeep

Hi, I was using the new paths feature. I made an animation that use a huge path and took me many hours. When I exported it to json, I noticed that the animation was wrong when I imported it to Unity. The problem is that the object that moves in the path takes bad positions when the path is very low. I inspected the JSON file and noticed that the vertices position information relative to y-axis was always "-21474.836" in the lower parts of the path.
According to this https://en.wikipedia.org/wiki/Integer_(computer_science). The min value of a signed integer is -2147483648.
So I think that the problem is that Spine exports the value numbers as integers, and this is not enough.

How can I resolve this?

Xeep

Xelnath

Wow, what kind of animation was this??

Xeep

Is not so huge. I don't know why but all values are really huge:

"To the Happiness": {
  "To the Happiness": {
    "type": "path",
    "constantSpeed": false,
    "lengths": [
      2510.09,
      3381.88,
      5450.05,
      6126.67,
      6740.72,
      7638.55,
      8609.54,
      9262.8,
      11618.92,
      14205.55
    ],
    "vertexCount": 30,
    "vertices": [
      187.4,
      -5495.71,
      162.97,
      -161.39,
      173.89,
      5403.2104,
      12627.26,
      21474.836,
      14233.71,
      10691.21,
      14254.59,
      10518.84,
      11086.9,
      18345.14,
      8225,
      12998.701,
      5731.37,
      8306.66,
      7799.67,
      -3653.8098,
      7953.9595,
      -7513.71,
      8108.26,
      -11373.61,
      10479.75,
      -12595.49,
      11814.231,
      -11682.66,
      13571.11,
      -10444.47,
      11870.539,
      -6651.99,
      14140.389,
      -6336.13,
      15919.311,
      -6085.1,
      15623.311,
      -10139.02,
      15681.999,
      -14689.579,
      15710.37,
      -16864.12,
      15708.72,
      -21474.836,
      15663.121,
      -21474.836,
      15594.32,
      -21474.836,
      14593.2,
      -21474.836,
      11449.84,
      -21474.836,
      6331.85,
      -21474.836,
      -10677.95,
      -21474.836,
      -12063.67,
      -21474.836,
      -15965.57,
      -21474.836
    ]
  }
},

Maybe due to the size of the images? I work with all skeletons scaled at 10%. You can see in the attached image the complete path.

Erika

Excuse me if it's off topic but I can't help but ask: What is that poopy doing jumping on the sink? XD and with such a smiley face too!

Xeep

Just doing some 'crap' games 😃 The poopy is looking for the path to the Happiness as Tangle told him:

Erika

When this one is out please post a link in the Showcase section. This is something I need to try, Lol.
end of off topic and sorry XD

Xeep

Sure! 🙂 I sent you a PM.

Mario

Could you supply us with the Spine project so we can reproduce the issue? The values are OK and shouldn't trigger and overflow issues, they are well within the double range used in JSON. The only problem I could imagine is the JSON/binary parser doing something dumb.

Xeep

Ok, I sent you the project in a PM.

Pharan

Seems like the numbers are capped on export as you described.
I've opened an issue here: Exported json float values capped, causes wrong values on large projects. · Issue #114 · EsotericSoftware/spine-editor · GitHub

I've tested exporting it as a binary (.skel.bytes) and the path seems to retain the correct shape.
So, temporarily, you may want to use binary for now.

Xeep

Ok, I will manage with that for now. Thanks

Nate

Fixed in 3.5.02-beta. Cheers!