Game asset processing4 min read

A Spine Linked Mesh Misses Deform Keys? Check Inherit Timelines

Shared mesh structure and inherited source deform keys are separate checks. Identify the real source, attachment and animation before changing inheritance.

A Spine Linked Mesh Misses Deform Keys? Check Inherit Timelines
Concept art of one character in teal, orange and purple looks
AI-generated appearance concept art, not a shared-mesh or deform-inheritance test.

A replacement appearance displays, yet one source deformation does not follow it. Identify deform keys, weighted bone movement or image positioning before assuming that a link inherits every kind of animation data.

Structure and key inheritance are separate

The current Mesh guide describes shared source structure and weights. With Inherit timelines enabled, source deform keys affect the linked mesh; without it, the linked mesh can have separate deform keys.

That documented scope concerns deformation keys, not every bone, slot or gameplay event. Verify the installed editor and runtime rather than assigning all animation behavior to the label.

Create a reliable control

  1. Record the actual source mesh, linked attachment, skin and project revision.
  2. Confirm that the source animation contains the intended deform keys, rather than only bone-driven movement.
  3. Compare the source and current linked appearance at the same animation time.
  4. In a project copy, record the setting and observed result without overwriting the only working revision.

Inheritance does not create deformation missing from the source. If another attachment or skin is displayed, correct the comparison target first.

Independent keys do not remove every shared relationship

Shared geometry, weights and mapping still need review. Before structural edits, list affected variants using the linked mesh and replacement-image checklist. Disabling deform inheritance is not a complete unlink operation.

For independent deformation, have the owner inspect the linked mesh's own keys. For source-following motion, verify its actual inheritance configuration and data. Do not switch repeatedly between the paths without a preserved baseline.

Accept the full motion

Inspect transitions, maximum bending and return, recording actual keys and appearance before checking the other linked variants. Similar still images do not establish identical motion.

Retain resources and export batches through Spine Workbench and its guide. Image calibration and Warp are not an external Spine project's inheritance editor. No project experiment was run here, and the cover is not a mesh-sharing or deformation measurement.

Ready to try "A Spine Linked Mesh Misses Deform Keys? Check Inherit Timelines"?

Use our online tools to apply this tutorial to your indie game project right away.