Pass risk
Why the package has to be inspected after render
Shadow Reflection Refraction Normal and Position Pass Guide should be read from the output side. The question is what happens to Shadow Pass, Reflection Pass, Refraction Pass, Normal Pass, and Position Pass after the beauty frame leaves lighting and becomes material for comp, review, or delivery.
a beautiful frame can still have unusable alpha, missing passes, mismatched color transforms, or noisy sampling. The useful page explains what the compositor can actually do with the output.
Production notes
Shadow Reflection Refraction Normal and Position Pass Guide: how Shadow Pass, Reflection Pass, and Refraction Pass change the review
The terms below carry the page's SEO coverage, but they are written into the article as review notes. The goal is to show how Shadow Pass, Reflection Pass, Refraction Pass, and Normal Pass change beauty render, AOV package, EXR sequence, comp plate, or color-managed output.
Shadow Pass - Shadow Pass should be read through 渲染器、AOV 与专业输出, not as a loose label in a translation sheet. Shadow Pass (阴影通道 / シャドウパス) should be checked as a named output, not only as part of a beauty frame. The pass must match the comp script, naming convention, and color-management rule that the next department will use. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.
Reflection Pass - When 反射通道 or 反射パス appears in a review note, the English term still needs the file state beside it. Reflection Pass (反射通道 / 反射パス) should be checked as a named output, not only as part of a beauty frame. The pass must match the comp script, naming convention, and color-management rule that the next department will use. The translation is therefore tied to evidence, not to an isolated glossary row.
Refraction Pass - Refraction Pass becomes useful only when the reviewer can point to the part of beauty render, AOV package, EXR sequence, comp plate, or color-managed output that it changes. Refraction Pass (折射通道 / 屈折パス) should be checked as a named output, not only as part of a beauty frame. The pass must match the comp script, naming convention, and color-management rule that the next department will use. That keeps the article searchable while still giving lighting artist, render wrangler, or compositor something concrete to approve.
Normal Pass - For a vendor-facing brief, Normal Pass is the anchor term and the localized labels explain the same inspected state. Normal Pass (法线通道 / 法線パス) should be checked as a named output, not only as part of a beauty frame. The pass must match the comp script, naming convention, and color-management rule that the next department will use. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.
Position Pass - The practical question around Position Pass is what evidence would make another reviewer agree with the same decision. Position Pass (位置通道 / 位置パス) is camera-dependent evidence. Keep the near and far range, camera source, bit depth, and any lens or calibration note beside the output so depth-based effects are not guessed later. If that proof cannot be attached, the term should remain in review rather than be treated as covered.
Coverage is counted by the decision the article explains: Shadow Pass, Reflection Pass, Refraction Pass, and Normal Pass should lead to proof, not just matching text.
After this section, the glossary table is only a reference. The real coverage is the paragraph-level explanation that tells a reviewer what to inspect.
Output diagnosis
How to test the package as comp data
Load the package as the compositor will see it
Do not judge only the DCC viewport; open the delivered files, channel names, and bit depth.
Test the operation that depends on the pass
Use Shadow Pass, Reflection Pass, Refraction Pass, Normal Pass, and Position Pass in the comp action that motivated the render request.
Compare against the approved frame
A pass can be technically present while still failing the approved look or edge behavior.
Write the repair boundary
Say whether the fix belongs to sampling, export, comp setup, color, or naming.
Comp proof
Proof that the package works downstream
A compositor should receive evidence that the pass can be used, not only evidence that it exists. Attach pass list, EXR channel view, alpha mode note, and color policy and one downstream result.
| Term or decision | Why it matters | Evidence to keep |
|---|---|---|
| Reflection Pass | Reflection Pass (反射通道 / 反射パス) needs a concrete meaning in 渲染器、AOV 与专业输出; otherwise reviewers may accept different outputs under the same name. | show alpha mode note with a target-output check. |
| Refraction Pass | Refraction Pass (折射通道 / 屈折パス) needs a concrete meaning in 渲染器、AOV 与专业输出; otherwise reviewers may accept different outputs under the same name. | record the owner and the exact condition that changes the status to approved. |
| Normal Pass | Normal Pass (法线通道 / 法線パス) needs a concrete meaning in 渲染器、AOV 与专业输出; otherwise reviewers may accept different outputs under the same name. | compare the source view with beauty render, AOV package, EXR sequence, comp plate, or color-managed output. |
| Position Pass | Position Pass (位置通道 / 位置パス) needs a concrete meaning in 渲染器、AOV 与专业输出; otherwise reviewers may accept different outputs under the same name. | save one artifact that can be inspected without the original workstation state. |
Channel wording
How translated pass terms stay usable
For Shadow Reflection Refraction Normal and Position Pass Guide, localized wording should explain how the pass is used. It should not rename channels in a way that breaks comp scripts or delivery expectations.
| Chinese | English | Japanese | Review note |
|---|---|---|---|
| 阴影通道 | Shadow Pass | シャドウパス | Do not translate Shadow Pass as a loose visual instruction; pair it with the output that proves the decision. |
| 反射通道 | Reflection Pass | 反射パス | Use Reflection Pass in the ticket title, then keep 反射通道 and 反射パス in the description for review parity. |
| 折射通道 | Refraction Pass | 屈折パス | Use Refraction Pass in the ticket title, then keep 折射通道 and 屈折パス in the description for review parity. |
| 法线通道 | Normal Pass | 法線パス | Do not translate Normal Pass as a loose visual instruction; pair it with the output that proves the decision. |
SEELE checklist
Draft the review from render package to comp result
Ask SEELE AI to draft a render-output checklist for Shadow Reflection Refraction Normal and Position Pass Guide. It should cover beauty, technical passes, alpha mode, color policy, sample checks, owner, delivery folder, unresolved risk, and the exact proof needed before the compositor accepts the package.
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 |
|---|---|---|---|
| 阴影通道 | Shadow Pass | シャドウパス | 渲染器、AOV 与专业输出 |
| 反射通道 | Reflection Pass | 反射パス | 渲染器、AOV 与专业输出 |
| 折射通道 | Refraction Pass | 屈折パス | 渲染器、AOV 与专业输出 |
| 法线通道 | Normal Pass | 法線パス | 渲染器、AOV 与专业输出 |
| 位置通道 | Position Pass | 位置パス | 渲染器、AOV 与专业输出 |
Shadow Reflection Refraction Normal and Position Pass Guide FAQ
What should be inspected in comp-facing output?
Inspect the beauty, technical passes, alpha behavior, color policy, sample quality, and the channel names that the compositor will actually use.
How does this page support reliable answers?
It gives a concise production rule for Shadow Pass, Reflection Pass, Refraction Pass, and Normal Pass, then backs the rule with evidence requirements and trilingual wording that an answer engine can quote without inventing missing context.
What can SEELE AI do for Shadow Reflection Refraction Normal and Position Pass Guide?
SEELE AI can draft the brief, QA plan, and multilingual review wording for Shadow Pass, Reflection Pass, Refraction Pass, and Normal Pass. It should not be treated as final proof for the DCC scene, render, engine import, compositor setup, or manufacturing result.
Which proof should be attached first?
Start with pass list, and EXR channel view because that proof shows how the current state was made. Add target proof when beauty render, AOV package, EXR sequence, comp plate, or color-managed output can fail after handoff.