How to Fit the Same Weapon to Small and Tall Rigged Characters

By GripForge editorial team · · updated · 5 min read

Use a repeatable scale-and-orientation acceptance checklist to fit one weapon to characters of different sizes without breaking grip alignment.

Reuse the weapon mesh, but fit it independently to each character. A larger character can have different hand proportions, bone axes and grip animation, so the final weapon scale, position and rotation may differ. A reusable workflow produces a reliable fit on both characters; it does not require identical offsets.

Separate three decisions: how large the character is in the game world, how large the equipment should appear, and where its handle sits relative to the hand. Changing one setting to compensate for another makes later animation checks harder to interpret.

Decide whether the weapon itself should change size

There are two reasonable design choices. A sword can represent the same physical object when a small or tall character picks it up. Alternatively, each character can receive a proportionally sized version of that sword. Establish which behavior the game needs before choosing an attachment ratio.

For a shared physical object, keep its intended world dimensions consistent and account for any scale inherited from the character hierarchy. For proportional equipment, choose a size appropriate to each character. Neither approach makes palm contact automatic: a plausible blade length can still leave a handle too thick for a particular hand.

GripForge supports character-relative equipment sizing and styles including melee, gun, shield and staff. Use those controls as a starting point, then inspect the actual result. The attachment API documentation describes the supported inputs and returned bind.

Establish the character's intended scale first

Import both characters into a small comparison scene with a common reference object, such as a doorway or a simple measured box. Set their intended world size before tuning equipment.

Check each character independently:

  • Is its root transform the one your game will use?
  • Does its apparent height agree with the scene's unit convention?
  • Is additional scale applied on an intermediate parent?
  • Does the animation still look appropriate at that size?

A root-scale value alone does not tell you a character's height. Two files with a scale of one can contain differently sized geometry. Record both the relevant transforms and the observed size so another developer can reproduce your setup.

Once these choices are stable, keep them fixed while evaluating the weapon. Do not resize a correctly sized character simply because its sword looks too small.

Reuse the source prop and fit each target

Keep an unchanged source weapon in your asset library. For each target character, create or record an attachment using that character's own rig, selected hand and equipment style. GripForge's gripforge_attach works with a separate prop and a rigged character, returning a bind transform and engine integration snippets.

Start with the chosen equipment scale. Look at the overall silhouette, the handle thickness and, where relevant, reach to the second hand. These are separate checks: enlarging a weapon to reach an off-hand can make its handle unusable for the primary hand. That situation may call for a different pose or a modified prop, rather than another scale adjustment.

Then adjust local placement so the grip sits appropriately in the palm. Inspect the handle from the side and front instead of relying on a single flattering camera angle. Check rotation as well as translation; a handle can occupy the correct position while the blade faces the wrong way.

Treat grip offset as specific to the rig

The bind supplied by GripForge is expressed relative to a bone. Its meaning depends on the actual target bone and its coordinate frame. Bone names, proportions and local axes can differ between characters, even when both are humanoid.

Copying an offset is a useful starting experiment when rigs are compatible. It is not a requirement for reuse. If the second character needs a different offset, save that difference with its attachment rather than forcing it to match the first character numerically.

Moving the weapon also does not articulate fingers. If a hand's pose does not suit the handle, inspect the rig and animation separately. The character may need a different pose or additional rig work. Do not use a large translation to hide an incompatible hand pose.

Test the pair in motion

Preview the clips the character will actually use with that equipment. An idle pose only establishes one frame of the relationship. Walking, turning, aiming or attacking can expose intersections that were not visible during fitting.

Use a simple per-character acceptance sheet:

CheckWhat to record
Intended sizeCharacter world size and the chosen equipment-sizing policy
Attachment targetActual bone name and selected hand
Local fitSaved weapon scale, position and rotation for this rig
Palm contactViews that show handle placement clearly
MotionClips inspected and any frames with visible intersections
GameplayCollision or reach checks performed separately in the game

This is a suggested review format. Passing a visual check does not establish that collision, damage or gameplay reach is correct; those depend on the game's own implementation.

Diagnose the setting that is responsible

The weapon follows the hand but floats beside it. Check the local grip position, the selected bone and the coordinate space used when applying the bind. Changing the entire character's scale is unlikely to address a local placement error.

The grip looks right but the weapon is too large. Revisit the equipment-sizing policy and inherited scale. After changing weapon size, check palm contact again because scaling can also change where the handle surface meets the hand.

The weapon looks correct until an animation plays. Confirm it follows the intended animated bone, then inspect the hand pose and any additional constraints. A correct static placement does not establish that every animation is compatible.

Only the second character fails. Compare its bone frame, proportions and hierarchy with the first. Refit that target instead of treating different local values as an error.

Save an attachment that can be reproduced

Keep the source prop identifier, target character identifier, intended scale and resulting bind together. Use the engine-specific snippet returned by GripForge instead of translating rotation conventions by guesswork. Then repeat the visual checks inside the target game, where parenting and animation are actually applied.

The MCP reference describes attaching and retrieving library assets. For the broader preparation sequence, see the character pipeline guide. The goal for equipment reuse is a repeatable, inspectable fit for each character, with the original weapon available for the next one.

Try it on your own prompt

GripForge turns a text prompt into rigged, animated, engine-ready game assets — from the browser, or from Claude Code and Cursor through MCP. The free plan includes Studio attaches and API trials every month.

Start free Browse 11,000+ community assets

More from the blog

How to Fit the Same Weapon to Small and Tall Rigged Characters · GripForge