Call preview.capture for the current revision and snapshot. Require camera/front/side/top PNGs;
animation also needs first/middle/last frames. Verify file existence and SHA-256 before display.
Never reuse images from an older revision. Describe visible strengths and defects, and bind user
approval to the exact sceneRevision + snapshotId.
When to Use
Use when each modeling, material, lighting, camera, or animation milestone requires visual review, or when composition and geometry defects need to be located.
Prerequisites
- Current
sceneRevision + snapshotId, delivery camera, and approved preview output directory. - Specify the required views, resolution, frame numbers, and review focus; for animation, include at least the first, middle, and last frames.
Workflow
Step 1. Verify that the revision and snapshot are still current. Step 2. Capture camera, front, side, and top views; for animation, add keyframes. Step 3. Verify file existence, size, and SHA-256, then display by view. Step 4. Describe visible strengths, defects, and occlusions, and bind confirmation to that revision and snapshot.
Validation and Delivery Evidence
Provide the view, frame number, revision, snapshot, path, dimensions, and hash for each PNG; do not reuse images from an old revision.
Rules and Capability Boundaries (Not Applicable Scenarios)
Previews are visual evidence, not final renders, geometry measurements, or format deliveries; do not assert that all surfaces are correct based on a single view.
Gotchas (Common Issues and Recovery)
- Image is empty or all black: check camera clipping, lighting, and object visibility, then recapture.
- Revision has changed: discard old images and generate a new preview.
- View occlusion: add local or orthographic views; do not guess hidden structures from text.