Notes from the workbench

Production questions, unpacked

Useful answers begin by separating the performance problem from the pipeline problem. Often, both need attention.

How many clips should we plan?

Start from player actions and state transitions, not an arbitrary total. Include starts, stops, interruptions and equipment variants, then validate a small playable slice. A coverage map usually exposes missing transitions more effectively than a long spreadsheet of attractive actions. See performance foundations.

Is motion capture always faster?

No. Capture can accelerate suitable performances, but preparation, solving, cleanup, retargeting and integration remain part of the schedule. Highly stylized movement or unusual anatomy may need substantial keyframe work. Evaluate the entire route from reference to playable result, not only the time spent recording.

When should the rig be approved?

After representative stress poses, equipment interactions and an engine export test succeed, before animation production expands. Keep a known-good test scene and state the rig’s limits. Approval is a production checkpoint, not a promise that no future change will ever be necessary. Read the rigging guide.

Should we use root motion or in-place clips?

Choose per action according to movement ownership, collision and responsiveness needs. A hybrid can work if its rules are explicit. Test wall contact, direction changes and interruption behavior; neither approach is inherently free of foot sliding or timing compromises.

Why do good clips still feel unresponsive?

The cause may be input handling, transition conditions, blending, acceleration or cancellation rules. Test with input and state information visible. Shortening an animation may hide one symptom while leaving the underlying rule unchanged. The gameplay integration guide explains how to separate these causes.

Can one skeleton support different body types?

Often, but retargeting does not automatically preserve reach, contact or silhouette. Test representative proportions early. Equipment interactions and close hand contacts are particularly revealing because small differences in limb length can create obvious errors.

What should an animation delivery include?

Agreed exports and source, a manifest, skeleton dependencies, import settings, root and event policies, review evidence and known issues. Scope source delivery and third-party dependencies in advance. Use the handoff checklist as a starting point, then adapt it to the receiving team.

How should a producer evaluate a milestone?

Separate artistic approval from technical acceptance and evaluate a playable test against explicit criteria. Record the tested build and asset version. A concise list of reproducible issues is more useful than a general request for additional polish.

Does this website provide commissioned animation?

No. Bravocosmichexagon is an independent field guide. Its images and diagrams are editorial examples, not client portfolio work. We publish practical explanations of production decisions and welcome relevant corrections or editorial questions.

Does the motion-brief form send my project details?

No. It constructs an editable text preview locally. Copy and download are user-triggered; sending an email is a separate action. Do not include confidential project information unless you have permission to share it. Open the motion-brief tool.