Layering spine2d animation
#Layering spine2d animation manual
The triangulation of the mesh from when it had manual edges is preserved. If Nonessential data is not checked when the mesh is exported and that exported data is imported back into the Spine editor, the mesh will not have any manual edges. If that exported data is imported back into the Spine editor, the bounding box will have a default color.įor mesh attachments, the manual (orange) edges inside the mesh hull are nonessential data. If JSON or binary data is exported without Nonessential data being checked and is later imported back into the Spine editor, then the import will succeed but some information may be lost.įor example, the color of a bounding box is not normally needed at runtime, so it is only exported when Nonessential data is checked. If the data is later imported back into the Spine editor, that extra information is used to configure the imported skeleton. When JSON or binary data is exported and the Nonessential data setting is checked, extra information is exported which is not normally used at runtime.
If the skeleton already contains an item from the data: When checked, the data is imported into the chosen skeleton in the current project. When checked, the data is imported into the current project as a new skeleton. When unchecked, the data will be imported into the current project and more options appear. Unfortunately, this needs to be done manually, cause as said this feature isn't. Or you can manually recreate them, depends on what is faster. When checked, the data will be imported into a new project. In case it fails you can import a project, have a copy of that skeleton, and move the bones in question by dragging and dropping them from one skeleton to another. The new project would then use images with a different size. If a Spine project was created with images that are the wrong size, the project can be exported to JSON with Nonessential checked and then imported again using Scale to change the size of the skeleton. All the data is scaled: the position and length of bones, attachment offsets, bounding boxes, meshes, animations, etc.
The import data Scale changes the size of the skeleton without changing the scale of any bones. The images used for the new project should be 25% the size of the original images. For example, if a Spine project is created with images that are 4 times larger than necessary, it can be exported to JSON with Nonessential checked, then imported to a new project with a scale of 0.25.