Этот сайт лучше всего просматривать в современном браузере с включённым JavaScript.

export problem

wariel23

Hello, good morning. I'm having a problem exporting the JSON. It doesn't detect physics or some skeleton movements and constraints. I need to fix this quickly because I have a project to deliver. I'm using version 4.3.18.

Nate

4.3 is in beta, which means it is being actively developed, it may have bugs, and runtime support may not be complete for every runtime:
http://esotericsoftware.com/spine-versioning#Beta-releases

Likely you will need to use 4.2 until 4.3 is out of beta, or at least is near the end of the beta.

You can export JSON and choose 4.2, then run 4.2 and use Import Data. Let us know if you have trouble doing this.

JustHitIt

Nate
I made Animation in 4.3, and export it to 4.2, have trouble to reopen it in spine 4.2

And the Log

Nate

Please post here or email your .spine file and we can take a look at why it is not creating valid 4.2 JSON. contact@esotericsoftware.com

JustHitIt

Nate I've found it would be this problem when using Path Contraint in a project. Using path contraint in 4.3 and export to 4.2 JSON, and it fail.

Nate

Thanks, we've fixed it in 4.3.19-beta!

JustHitIt

Nate Thanks, now it can be imported to 4.2. But I lose all the Offset Value in Transform Constraint when open it in Spine 4.2

Nate

I don't see offsets being lost, but the constraint order and timelines are wrong. We've fixed this in 4.3.20-beta. Sorry for the trouble!

JustHitIt

Nate
I mean the Rotate Value in offset, it is still missing.
I build a simple case as below,
Set Value in 4.3

Output:

reimport to 4.2

Nate

Ah I see now, thanks. Fixed in 4.3.21-beta!

JustHitIt

Nate
Physics contraints Bug,
when build in 4.3,

And reimport to 4.2,

JustHitIt

Mix Value is missing In Path Contraint:

Misaki

JustHitIt Thanks for your report! Unfortunately, based on only two screenshots, it is unclear what the relationship is between the two skeletons. Are you saying that when you export the skeleton created in version 4.3.21 and import it into version 4.2, the Translate Y mix value changes?

When reporting a problem, it is always helpful to include the steps to reproduce it, as this allows us to quickly investigate the issue.

JustHitIt

Misaki Yeah, the Translate Y mix Value will change

seki

Misaki The earlier issue with physical constraints and the one below are two separate problems. The second issue seems to occur only when using chain scale.

Misaki

seki Thank you for sending us the Spine project files! I believe I was able to reproduce the issue.
By the way, please note that the project you send us can always be simplified. In fact, I was able to understand the issue sufficiently even after deleting about 60% of the project you sent us.
Also, in cases like this where the bone movement itself is incorrect, you do not need to send us any images. It is sufficient to send only the .spine file.
We are currently investigating the issue and will respond to this thread as soon as we have more information.

Nate

It is difficult to do anything with these reports. We have to try to recreate a project like what you have, export with 4.3, import with 4.2, then find the problem. When we try that and don't find a problem, we have to ask you for more information.

If you have a project that shows a problem, please just post the .spine with instructions on how to see the problem.

4.3 (left) when exported to 4.2 (right) doesn't show Y mix being lost. 4.3.21-beta
Loading Image

Nate

Fixed in 4.3.24-beta! 🍻

seki

The setup seems to be almost consistent, but there are still issues with the keyframes in the animation.

seki

seki The text in Image 1 is incorrect; it should be 4.3.24

Misaki

seki Thank you for reporting the issue. Using the project you provided earlier, I was able to reproduce the issue you mentioned, but I have not yet found a consistent way to reproduce it (i.e., a way to reproduce the issue when starting from a new project). I was unable to reproduce the issue by creating a new project, adding two bones, setting an IK constraint, adding a few constraint keys during animation, and exporting in 4.2 format. Therefore, I believe there may be another underlying factor, which I am currently investigating. I will let you know as soon as we find out something.

Misaki

seki After completing some research, I have created an issue ticket here to fix this problem:
EsotericSoftware/spine-editor891
We apologize for the inconvenience, but please wait until we have resolved this issue.

Следующая страница »