Unreal and Unity Component Handoff Guide

Blueprint - For a vendor-facing brief, Blueprint is the anchor term and the localized labels explain the same inspected state. Blueprint (蓝图 / ブループリント) becomes meaningful only after target-engine proof. Keep import settings, runtime capture, packaging or cook notes, and ownership separate from the source DCC approval. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.

Reflection Probe - The practical question around Reflection Probe is what evidence would make another reviewer agree with the same decision. Reflection Probe (反射探针 / リフレクションプローブ) 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. The translation is therefore tied to evidence, not to an isolated glossary row.

Lumen - Treat Lumen as a production checkpoint: it should narrow the review, not decorate the page with another synonym. Lumen (流明 / Lumen) becomes meaningful only after target-engine proof. Keep import settings, runtime capture, packaging or cook notes, and ownership separate from the source DCC approval. That keeps the article searchable while still giving technical artist or engine integrator something concrete to approve.

Deferred Rendering - Deferred Rendering should be read through 引擎, not as a loose label in a translation sheet. Deferred Rendering (延迟渲染 / ディファードレンダリング) 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. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.

Forward Rendering - When 前向渲染 or フォワードレンダリング appears in a review note, the English term still needs the file state beside it. Forward Rendering (前向渲染 / フォワードレンダリング) 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. If that proof cannot be attached, the term should remain in review rather than be treated as covered.

Temporal Anti-Aliasing - Temporal Anti-Aliasing becomes useful only when the reviewer can point to the part of runtime asset, prefab, blueprint, component setup, or cooked content path that it changes. Temporal Anti-Aliasing (时间抗锯齿 / テンポラルアンチエイリアス) 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. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.

Character Blueprint - For a vendor-facing brief, Character Blueprint is the anchor term and the localized labels explain the same inspected state. Character Blueprint (角色蓝图 / キャラクターブループリント) becomes meaningful only after target-engine proof. Keep import settings, runtime capture, packaging or cook notes, and ownership separate from the source DCC approval. The translation is therefore tied to evidence, not to an isolated glossary row.

Component Blueprint - The practical question around Component Blueprint is what evidence would make another reviewer agree with the same decision. Component Blueprint (组件蓝图 / コンポーネントブループリント) becomes meaningful only after target-engine proof. Keep import settings, runtime capture, packaging or cook notes, and ownership separate from the source DCC approval. That keeps the article searchable while still giving technical artist or engine integrator something concrete to approve.