Probe devices before selecting Cycles GPU. Honor an explicit CPU fallback; never claim GPU rendering from engine selection alone. Configure resolution, samples, transparency, view transform/look, exposure and required view-layer passes before rendering.
Use reusable shader node groups and semantic texture connections. Bake only meshes with an active UV layer and approved output root, then pack required image dependencies and make paths relative before standalone delivery. Reopen the packed .blend in an independent directory.
Build the named compositor chain without deleting unrelated nodes; inspect links after configuration. Use the version-2 extended receipt for EXR, USD and Alembic so the legacy export receipt remains compatible. Verify each artifact exists, is non-empty and reopens or imports within the format's supported scope. Device, pass and format availability are runtime facts, not Add-on metadata assumptions.
For long animation delivery, prefer RENDER_ANIMATION_FRAMES over direct MP4 export. It binds PNG or multilayer EXR frames to the submitted .blend snapshot, records every frame hash, and supports explicit missing-frame recovery. Configure a File Output node only inside the approved output root. Reusable VSE looks belong in a compositor node group consumed by a COMPOSITOR strip modifier. Final MP4 composition is a separate COMPOSE_VIDEO job so encoding changes do not rerender 3D frames.
When to Use
Use when configuring Eevee/Cycles, render passes, color management, material baking, dependency packaging, compositing nodes, or extended format delivery.
Prerequisites
- Specify the engine, device fallback, resolution, samples, color settings, passes, frame range, and output root directory.
- Baked objects must have active UVs; use immutable snapshots and background frame sequences for long animations.
Workflow
Step 1. Probe device and format capabilities, select the engine, and record the actual device; do not claim GPU based on configuration alone. Step 2. Set resolution, samples, transparency, view transform, exposure, and view-layer passes. Step 3. Build or reuse named material/compositing node groups and check all semantic links. Step 4. Bake or render to the approved directory; for long animations, output frame by frame and then composite the video separately. Step 5. Package dependencies, relativize paths, and reopen or reimport in a separate directory.
Validation
Submit device probing, engine, passes, color settings, node links, frame hashes, media probing, dependency manifest, and independent reopen results.
Rules and Capability Boundaries (Inapplicable Scenarios)
Engine selection does not prove that the GPU actually works; a simple fixture does not represent cinematic quality. Video encoding changes must not be triggered as a full 3D re-render.
Gotchas
- GPU unavailable: fall back to CPU according to the approved policy and disclose the performance impact.
- Black frames or missing passes: check the view layer, camera, output nodes, and frame manifest.
- Missing textures when opened externally: recheck packaging and relative paths, then reopen independently.