Production memo
The note that prevents a second clarification round
For Idle Attack State Machine Blend Tree and Montage Guide, a useful handoff starts before the file is sent. It names Idle Animation, Attack Animation, and State Machine, identifies the output being judged, and explains what the receiver should open first instead of asking for another screenshot.
Animation review works best when timing, intent, and runtime state are documented together. Treat the local DCC preview as a clue, not as final validation. The memo should mention animator, cinematic editor, or gameplay animation owner, the target state, and the artifact that settles the question.
Term reading
Idle Attack State Machine Blend Tree and Montage Guide: production notes for Idle Animation
This article keeps the keywords in the prose because a production lead will not approve a DCC file from a detached card list. Each term gets tied back to a source state, a target output, or a proof artifact.
Idle Animation - When 待机动作 or アイドルモーション appears in a review note, the English term still needs the file state beside it. Idle Animation (待机动作 / アイドルモーション) needs a before-and-after note when it changes the asset. The accepted evidence should be small enough for another reviewer to reopen without rebuilding the whole scene. The translation is therefore tied to evidence, not to an isolated glossary row.
Attack Animation - Attack Animation becomes useful only when the reviewer can point to the part of clip, curve, retimed sequence, state-machine transition, montage, or review cut that it changes. Attack Animation (攻击动作 / 攻撃モーション) is useful in a brief only when it points to an inspectable source state. Put the term beside the file, target output, and owner who can verify it. That keeps the article searchable while still giving animator, cinematic editor, or gameplay animation owner something concrete to approve.
State Machine - For a vendor-facing brief, State Machine is the anchor term and the localized labels explain the same inspected state. State Machine (状态机 / ステートマシン) can be translated safely only after the production meaning is known. Keep the English label visible when it is also a UI label, plug-in name, or channel name. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.
Blend Tree - The practical question around Blend Tree is what evidence would make another reviewer agree with the same decision. Blend Tree (混合树 / ブレンドツリー) should be reviewed at the graph level. A screenshot of the final viewport is secondary; the important evidence is the node group, exposed parameters, and the output that proves the graph behaves as intended. If that proof cannot be attached, the term should remain in review rather than be treated as covered.
Animation Montage - Treat Animation Montage as a production checkpoint: it should narrow the review, not decorate the page with another synonym. Animation Montage (动画蒙太奇 / アニメーションモンタージュ) is useful in a brief only when it points to an inspectable source state. Put the term beside the file, target output, and owner who can verify it. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.
A useful DCC keyword page earns its ranking by helping a real handoff become less ambiguous.
If the review moves to an outsourcing ticket, copy the relevant paragraph rather than sending only the term row.
Receiver check
Clarifications to close inside the note
- What did the artist actually change before sending this review?
- Does the receiver need source evidence, target evidence, or both?
- Which of Idle Animation, Attack Animation, State Machine, Blend Tree, and Animation Montage belongs in the task title, and which belongs in acceptance criteria?
- Can animator, cinematic editor, or gameplay animation owner reproduce the same state from frame range, curve screenshot, and playblast?
- What should stay blocked until the downstream check is attached?
A clean sentence here saves a messy follow-up thread later.
Ticket copy
Short wording for the production thread
For Idle Attack State Machine Blend Tree and Montage Guide, inspect Idle Animation, Attack Animation, and State Machine against clip, curve, retimed sequence, state-machine transition, montage, or review cut. The receiver should see frame range, curve screenshot, and playblast, the owner, and the exact state being accepted before the ticket leaves review.
The copy is short because the evidence should carry the argument. The text only names what the reviewer is meant to inspect.
Evidence pass
A matrix for the final scan
The matrix below is a second pass over the article, not the article itself. It is there for reviewers who need a quick acceptance check.
| Term or decision | Why it matters | Evidence to keep |
|---|---|---|
| Attack Animation | Attack Animation (攻击动作 / 攻撃モーション) needs a concrete meaning in 动画、动作与镜头; otherwise reviewers may accept different outputs under the same name. | compare the source view with clip, curve, retimed sequence, state-machine transition, montage, or review cut. |
| State Machine | State Machine (状态机 / ステートマシン) needs a concrete meaning in 动画、动作与镜头; otherwise reviewers may accept different outputs under the same name. | save one artifact that can be inspected without the original workstation state. |
| Blend Tree | Blend Tree (混合树 / ブレンドツリー) needs a concrete meaning in 动画、动作与镜头; otherwise reviewers may accept different outputs under the same name. | write the unresolved risk in the task before asking for sign-off. |
| Animation Montage | Animation Montage (动画蒙太奇 / アニメーションモンタージュ) needs a concrete meaning in 动画、动作与镜头; otherwise reviewers may accept different outputs under the same name. | attach frame range and curve screenshot. |
Trilingual note
Keeping CN/EN/JA tied to the same state
Keep the localized terms close to the decision they support. A vendor can act on Idle Animation, Attack Animation, and State Machine only when the note also includes owner, target, and evidence.
| Chinese | English | Japanese | Review note |
|---|---|---|---|
| 待机动作 | Idle Animation | アイドルモーション | Use Idle Animation in the ticket title, then keep 待机动作 and アイドルモーション in the description for review parity. |
| 攻击动作 | Attack Animation | 攻撃モーション | When a vendor uses 攻击动作, confirm whether they mean authoring state, exported data, or final target behavior. |
| 状态机 | State Machine | ステートマシン | If State Machine is a literal tool label, keep the English beside the translated term so reviewers can find it in the UI. |
| 混合树 | Blend Tree | ブレンドツリー | Do not translate Blend Tree as a loose visual instruction; pair it with the output that proves the decision. |
Terminology reference
Chinese, English, and Japanese terms used by this article
This table is kept as a reference for SEO coverage, outsourcing review, and localization alignment. Treat the article sections above as the decision guide; treat this table as the vocabulary index.
| Chinese | English | Japanese | Workflow context |
|---|---|---|---|
| 待机动作 | Idle Animation | アイドルモーション | 动画、动作与镜头 |
| 攻击动作 | Attack Animation | 攻撃モーション | 动画、动作与镜头 |
| 状态机 | State Machine | ステートマシン | 动画、动作与镜头 |
| 混合树 | Blend Tree | ブレンドツリー | 动画、动作与镜头 |
| 动画蒙太奇 | Animation Montage | アニメーションモンタージュ | 动画、动作与镜头 |
Idle Attack State Machine Blend Tree and Montage Guide FAQ
What should a handoff note include?
It should include source, target, owner, frame range, curve screenshot, and playblast, the terms under review, and a clear approval or revision status.
Which proof should be attached first?
Start with frame range, and curve screenshot because that proof shows how the current state was made. Add target proof when clip, curve, retimed sequence, state-machine transition, montage, or review cut can fail after handoff.
What should be copied into a production ticket?
Copy the term, the source state, the expected clip, curve, retimed sequence, state-machine transition, montage, or review cut, the owner, and the proof artifact. Leave out broad glossary wording unless it helps a vendor or reviewer find the exact control.
Can Idle Animation, Attack Animation, State Machine, and Blend Tree be covered together?
Yes, if they share one production decision around clip, curve, retimed sequence, state-machine transition, montage, or review cut. If the owner, evidence, or target output changes, split the work into a narrower leaf guide or review ticket.