- Đã chỉnh sửa
My path constraints are breaking at export
Like the title says, my path constraints break when I export my project.
They work in animate and setup mode, correctly warping the meshes weighted to the bones along the path constraint. As soon as I hit export, they break, and can only be fixed by closed without saving, or deleting and remaking new path constrains. See the attached movie
.
This is pretty time sensitive, any help is great!
I'm not able to reproduce the bug.
I had a project with bones on paths that deform meshes. Opened in Spine 3.4.02.
Switched to Animate mode. Played the animation. Exported while it was playing. It didn't break.
Did the same in the Spine 3.5 beta. Nothing wrong either.
Is there anything else that you think makes your setup unusual?
You may have to send your project to us so we can take a look at it. contact@esotericsoftware.com
Thanks for the reply, I sent the file to your team to take a look.
The only other thing I can think of is that everything is already being moved via another path constraint, so this is a path constraint on top of a path constraint. That seemed to also mess up IK based on a bone that was constrained to that original path. I gave up IK in favor of manually animating my paths. That at least has the appearance of working until this export problem.
edit: I just confirmed that changing the parent of the bones that I am moving with the path fixes the mesh issue. The problem is that now I have to manually animate them instead of getting the position of the bone they should be attached to.
I believe this to be a bug though, unless thee is reason not to be able to have a path constraint based on a bone that is already being moved via a different path constraint.
Could try to reproduce the problem with 3.5-beta?
I have to keep the file version at what it is, to make sure that it is compatible with the runtime the devs are using.
Thanks for sending the project via e-mail. I could not reproduce the issue in Spine 3.5-beta, but I was able to reproduce it in Spine 3.4.02.
What runtime are your customers using? All runtimes except for spine-c are up-to-date with all the latest 3.5 changes now.
badlogic đã viếtAll runtimes except for spine-c are up-to-date with all the latest 3.5 changes now.
I had a look on GitHub but it still says "spine-ts works with data exported from Spine 3.4.02." "spine-unity works with data exported from Spine 3.4.02."
spine-runtimes/spine-unity at master spine-runtimes/spine-ts at master
If you confirm both are up to date I'm switching to the newest version too! 8)
Non-beta versions (currently 3.4.02) work with the master branch on GitHub. We prepare runtimes for the beta version (currently 3.5.04-beta) in a different branch (right now that is in dev, in the future it will be in 3.5-beta, 3.6-beta, etc). Once ALL the runtimes are finished they will be merged into master and 3.5.x will be released without the "-beta" tag. Currently all the runtimes in the dev branch have been updated to 3.5 except for spine-c, which is in progress.
The devs on my team use libgdx, but only upgrade at stable releases, not beta versions, so we are always a bit behind, and are on 3.4.02 of Spine.
I found a more manual workaround for now, but it would be great to be able to have an IK joint/group of bones with a path constraint as a child of a bone that is in a separate path constraint. Is that officially supported functionality?
Yep, should work fine in 3.5.