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

Merge two project into one with skin reserved

linch47

Hi there, I'm facing a scenario where I need to merge two Spine projects into one. I’ve made several attempts, but it's not working. When I use the Import Data feature, everything works fine if I select "Create a new skeleton", but my goal is to merge two skeletons into one. So, I have to select "Import into an existing skeleton" and check the "Replace Existing Attachments" option. However, while importing into the existing skeleton, things go wrong—some of the meshes shrink into a point and break the project.

I’m working with several horses that have N skins and several riders with M skins. The main reason I want to merge them into one project is to avoid reworking the skins for the rider or the horse every time I combine them or when an extra skin is added to either the rider or the horse.

Did I miss anything? Please help... thank you!

Misaki

linch47 Perhaps the reason some meshes shrink is because they originally had skin bones in the bones bound to them, but the skin bones were not automatically set after import. (If the skin bone settings are incorrect, a warning icon will appear in the tree view.)

Unfortunately, merging skeletons is not very easy to do, especially when using skins. We are aware of this problem and have several issues on our roadmap for improvement:
EsotericSoftware/spine-editor524
EsotericSoftware/spine-editor582

Merging exported JSON files, as introduced by Spinebot, is one way to do this, but it is probably easiest to import once as a separate skeleton via Import Project, then drag and drop items in the tree view to the skeleton you want to merge, and then import the animations the Import Project.

Spinebot

To merge two Spine projects into one while preserving skins, you can follow these steps:

Export to JSON: Export both projects to JSON files. This will allow you to manually edit and merge the data.
Merge JSON Files: Manually merge the JSON files. Ensure that the bones, slots, and attachments have unique names to avoid conflicts. You may need to write a custom tool or script to help with this process.
Import Merged JSON: Import the merged JSON back into Spine. This should combine the skeletons and preserve the skins.

Here are some additional tips to help you with the process:

Unique Naming: Ensure that all bones, slots, and attachments have unique names across both projects to avoid conflicts during the merge.
Check Dependencies: Make sure that all dependencies (e.g., attachments, meshes) are correctly referenced in the merged JSON file.
Use Skins: Utilize the skins feature to manage different looks for the rider and horse. This will help you avoid reworking the skins every time you add a new one.

For more detailed guidance, you can refer to the following resources:

If you encounter issues with meshes shrinking or breaking, double-check the JSON data for any inconsistencies or missing references.