- Modifié
Import Data does not import path constraint spacing mode.
Version 3.4.01
Importing data in either json or binary formats to spine results in the default spacing mode being used for all path constraints.
Create a spine project with a path + bone(s).
Add a path constraint, set spacing mode to percent.
Export the project in either json or binary format. (settings used: no atlas, nonessential, pretty print for json)
Import the skeleton into a new project. (Default scale, new project, tested with both binary and json)
The spacing mode will be set to length.
The exported json file does state the correct spacing mode, so it looks like this issue related to importing.
What runtime?
badlogic a écritWhat runtime?
This issue occurs in the editor, sorry if I was unclear.
Fixed in 3.4.02, thanks!
I think there's a similar problem with importing Offset information for a Transform constraint.
I'm still running 3.2.01 Professional, but I noticed this the other day. When importing from a JSON, all of the Mix values from my Transform constraints were imported correctly, but all of the Offset values were 0 in the new project.
Also fixed in 3.4.02.
I think I just ran into a similar problem.
In the 3.4.02 editor I created a skeleton with a path constraint (Spacing 12.5 percent, chain scale - I basically copied the setup from the stretchy guy that comes with spine), but when I import the project (not import data) into a new project it's set to 1.0 length, tangent. Took me forever to figure out what was going on... :bang:
If I export stretchyman, then import the JSON into a new project, then path constraints have 12.5, percent, chain scale. Are you sure you're using 3.4.02? If so, can you provide exact reproduction steps?
Thanks for looking into this! I did import the (spine editor) project not import from a JSON... maybe that makes a difference.
I am off this week and don't have access to the file, but I can make a screen capture next week.
I really appreciate the quick support!