Spine Muzzle Flash in the Wrong Place After a Skin Swap

The firing animation works with the rifle, but the flash floats beyond the barrel on the compact weapon. Freeze both skins at the same firing frame. If the flash already happens at the right time, capture the resolved spawn position before touching the event timeline.

Give the two skins the same lookup contract

The official Spine guide describes points as positions with orientation that can be supplied by skins. Place a muzzle point for each weapon. Agree on the slot and placeholder that the receiving code should look up, and log the attachment it actually resolves. A new gun image can appear correctly even when the spawn code is still using a fallback location.

Point attachment position and rotation are authored on the attachment. For movement through an animation, key the bone that carries the point. Include a frame with a raised weapon as well as the firing frame so the test covers motion and the rest pose.

Capture position and direction separately

With the same animation and frame, capture the weapon image, resolved point, and effect position for each skin. Confirm that the point follows its bone and that the receiving code converts coordinates for the scene. A test facing the opposite direction can expose a direction conversion issue even when the spawn position looks correct.

Remove one point in a test copy and check the agreed fallback. The project can skip the effect or use a documented bone origin, depending on its requirements. Record the result explicitly so a previous skin’s point cannot silently pass as the fallback.

Hand off an effect test the team can replay

Use the Spine Workbench to inspect compatible exported assets for pose and weapon alignment. Verify point lookup and effect spawning in the receiving runtime. If the effect fires early or late while its location is correct, keep the position evidence and continue with the related diagnostic guide.