Description:
Once a skeleton is exported in JSON format and then re-imported, keys that were originally placed in integer frames are placed at slightly off-timings. For example, as seen in the screenshot below, a key that was originally placed at frame 5 is placed at timing 5.001:
Expected behavior:
After importing the JSON data, the keys are placed at the same timing as the original skeleton.
Steps to reproduce:
Create a new project with Spine 4.2.56-beta.
Switch to animate mode and add the rotation and scale keys of the root bone at frame 0, 5, 10, and 15, with random values in the animation:
Export the skeleton data of this project in JSON format.
Import the exported JSON file via Spine menu -> Import Data... as a new skeleton.
If you you select some keys for the animation of the imported skeleton, you will see that some of the keys that would have been on integer frames in the original skeleton have been moved to a halfway frame, such as 5.001 or 9.999.
The version of Spine in which this bug was found:
Spine 4.2.56-beta
NathanSweet
commented
3 months ago
Description: Once a skeleton is exported in JSON format and then re-imported, keys that were originally placed in integer frames are placed at slightly off-timings. For example, as seen in the screenshot below, a key that was originally placed at frame
5is placed at timing5.001:Expected behavior: After importing the JSON data, the keys are placed at the same timing as the original skeleton.
Steps to reproduce:
Create a new project with Spine 4.2.56-beta.
Switch to animate mode and add the rotation and scale keys of the root bone at frame
0,5,10, and15, with random values in the animation:Export the skeleton data of this project in JSON format.
Import the exported JSON file via
Spine menu -> Import Data...as a new skeleton.If you you select some keys for the animation of the imported skeleton, you will see that some of the keys that would have been on integer frames in the original skeleton have been moved to a halfway frame, such as
5.001or9.999.The version of Spine in which this bug was found: Spine 4.2.56-beta
This issue was reported on the following thread: https://ja.esotericsoftware.com/forum/d/25863-%E6%9B%B8%E3%81%8D%E5%87%BA%E3%81%97%E3%81%9Fjson%E3%82%92%E3%82%A4%E3%83%B3%E3%83%9D%E3%83%BC%E3%83%88%E3%81%99%E3%82%8B%E3%81%A8%E3%82%AD%E3%83%BC%E3%81%8C%E3%81%9A%E3%82%8C%E3%81%BE%E3%81%99