Hello,
We've been working on character animations using the Spine software, incorporating various expressions such as joy, sadness, winning, and losing for each character. However, we've been facing challenges when transferring these animations to Unity, and despite extensive research, we haven't found a comprehensive solution.
Our approach involves using at least two different poses and rigs for each character. Each rig contains multiple assets like hands and mouth in distinct poses. While working within a single project file poses no issues, attempting to create separate project files for different poses and then merging them into a unified project results in rig and animation errors.
Our ultimate aim is to have two animators collaborate on the same character in different project files and seamlessly combine these projects. We've meticulously prepared both poses in a single file, and both animators have contributed to this file. However, upon using the "Import Project - Skeletons" option and merging the files, we observed the generation of multiple JSON files and different atlases. Despite setting a single image folder as the source, Unity fails to consolidate them into a single, coherent skeleton.
We've also explored the "Import Project - Animations" option, ensuring that the animation rig aligns between projects. Unfortunately, this resulted in distortions in both the rig and animation. Even though we made sure that all bone names were distinct, keyframes affected the other rig.
Despite our attempts and the information gathered from forums and other sources, we haven't found a solution. Your assistance would be greatly appreciated.
Best regards.
Two different animators working on the same project
aykin I'm sorry to hear that you're having trouble. You mean you animated the exact same rigged skeleton in two different Spine projects and then something went wrong when you tried to merge the animations into one skeleton, right? That is really weird. I know it's a lot of work, but I think you should narrow down the range of possible causes, so start with a simple skeleton to see if it works. Could you make sure that the versions of Spine used by the two animators are exactly the same, and then try to get them to animate a very simple skeleton and see if the animation integration works? If it doesn't work, then there may be a bug in the Spine editor. If it works, then the skeleton you originally tried to merge could still be something different between these two Spine projects. Could you please confirm this?
Hello,
I appreciate your response. We've experimented with the solutions you recommended, but unfortunately, we couldn't achieve the desired outcome. Despite having identical setup poses in the project files, we encountered distortions in the animations upon importing. We are open to hearing alternative suggestions on this issue.
Subsequently, we endeavored to merge two projects, both rigged and containing multiple animations, from different project files. While we managed to import them seamlessly, this approach resulted in the creation of two distinct skeletons within the project file. Upon transitioning to the animation screen, animations from both projects played concurrently. We attempted to export for Unity, but this process generated separate JSON files for each skeleton, which is not our intended outcome.
Our goal is to export these two skeletons as a unified JSON file and a single atlas. It seems that we need to find a way to merge these two skeletons. Unfortunately, we haven't discovered a method for this. Is there a viable approach to amalgamate two different skeletons within the same project without compromising animations, constraints, and other attributes?
If merging proves unfeasible, exporting as a single atlas and a solitary JSON file for Unity would suffice for our needs. Your guidance on this matter would be immensely appreciated.
Best regards.
