
Write a shot, not a shopping list
Atlas method
Describe the result you need: a locked-off interview with a replaceable background, a short tracked move, or a reflective product against a changing environment. State the camera, intended output, and the part that is uncertain. That gives the test a boundary.
The breadth of virtual production described in Epic’s field-guide material is a useful reminder that an LED volume is not the only starting point. For a modest compositing test, a live preview can already help the crew evaluate the shot. The appropriate method depends on the question, not the prestige of the equipment.
Source: Volume 2 of The Virtual Production Field Guide now available! · Real-Time Compositing with Composure
Control the variables
Atlas method
Use one camera position, a short move if needed, and a simple environment. Record a baseline before adjusting anything. Change one relevant variable, such as camera motion or the foreground lighting, and compare the captured result. If several things change together, a better-looking frame may teach you very little.
Do not turn an early test into a fake production bid. It is reasonable to discover that a method needs more preparation or different expertise. Record that finding before expanding the equipment list.
Make the result portable
Atlas checklist
Save a brief describing the test, a representative recording, the configuration, and the unresolved problem. Ask someone who did not build it to reproduce the result from those notes. Difficulty here is useful evidence about the eventual handoff.
Stop when the agreed question is answered. If the test reveals another question, name it as the next experiment. This keeps learning visible and prevents a “small proof of concept” from quietly consuming a production schedule.
- Define one decision and a visible pass condition.
- Capture a baseline before changing the setup.
- Write down what worked, what failed, and what to test next.
Spend the first test on reducing uncertainty, not demonstrating the largest system.
Sources & evidence
Primary documentation establishes tool behavior or a reported production. Checklists and illustrative examples are Atlas editorial guidance, not results of independent testing. Match documentation to your installed version.
Source published: 6 April 2021 · Retrieved 16 September 2026
Source published: Not established · Retrieved 16 September 2026