Disclosure: This draft was generated with AI and checked against the cited primary sources, with a separate AI editorial review. It was prepared for the FrameSprite team, which has a commercial interest in FrameSprite. Proposed examples are not executed tests unless explicitly identified as recorded fixture results.
A rotated weapon can exceed its old layer boundary even when the original weapon fitted perfectly. Check the transform's clipping policy, then check the image canvas separately. Preserving a larger transformed layer does not automatically enlarge the delivered sprite frame.
Key Takeaways
- Transform clipping can discard pixels during rotation.
- Pixels preserved outside the image canvas may still be absent from the exported image.
- An animation set needs a deliberate common canvas, not a different crop for every pose.
Separate three different rectangles
Before rotating, identify the equipment layer's bounds, the full image canvas and the final game frame. They can have different dimensions. A thin spear may fit diagonally within the canvas but extend beyond the original equipment layer when rotated around the hand.
The common Transform options document clipping choices, including Adjust and Clip. In a working copy, choose a policy that retains the pixels you need rather than cropping them to the old bounds. Do this before committing the transformation; enlarging the canvas afterward does not recover pixels that were already discarded.
Rotate around the intended attachment
Use the Rotate tool and inspect its pivot. For an attached weapon, the hand or grip is often the useful reference. A rotation around the layer's center may move the entire weapon away from the hand, creating a placement error alongside the clipping problem.
Save the original equipment layer and perform the trial on a duplicate. After applying the rotation, reveal the layer boundary and inspect the tip, guard and trailing decoration. If those pixels exist outside the visible canvas, the remaining issue is output framing. If the tip ends abruptly at the old layer boundary, return to the original and repeat with the appropriate transform policy.
Preserve the animation canvas deliberately
GIMP's Canvas Size documentation distinguishes resizing the visible canvas from scaling image pixels. Use that distinction when extending a shared character frame. Enlarging the frame can preserve a longer weapon without reducing the character, but the origin relationship must stay consistent throughout the action set.
| Symptom | Likely boundary to inspect |
|---|---|
| Tip disappears immediately after rotation | Transform clipping or selection |
| Tip exists outside the visible image | Canvas/export bounds |
| Tip survives but the hand connection moves | Rotation pivot and placement |
| Each action imports at a different size | Inconsistent frame canvas or trimming policy |
Here is a proposed example, not an executed edit: an eight-frame sword action shares a 128-pixel square canvas. One raised pose extends beyond that contract. Decide whether to enlarge all frames with a preserved body anchor, shorten the pose's envelope, or deliver explicit placement metadata. Expanding only the exceptional frame silently changes the handoff format.
Reopen the actual PNG
Export the repaired frame, reopen it independently and compare it against a neighboring pose over the same registration guide. Inspect the full tip rather than merely the bounding dimensions. A larger image can still contain a cropped weapon if the destructive clipping happened earlier.
For related issues, read painting outside a GIMP layer boundary, portable PNG layer offsets and cropped flying-character extremities. Accept the repair only when pixel preservation, attachment alignment and the common frame contract all hold in the delivery files.
Written by the FrameSprite Workflow Team. Send a correction.
Top comments (0)