Epic Games documented its own virtual-production workflow in 2019

The image

The document is a downloadable PDF, not a still: The Virtual Production Field Guide, published by Epic Games on 25 July 2019 and described in the company's own announcement as "a foundational information document for anyone either interested in VP or already leveraging these techniques in production." Epic's post, written by Miles Perkins, states the guide explores LED-wall and real-time-engine workflows, includes case studies of productions that had already used them, and names its interview subjects directly: director and actor Sir Kenneth Branagh, visual-effects supervisor Ben Grossman, and cinematographer Bill Pope, ASC.

What the documents show

Epic's announcement documents its own guide's scope rather than a third party's assessment of it: real-time tools that can turn "the traditional linear pipeline into a parallel process," LED walls used for in-camera effects "instead of green screen," and department-by-department guidance for adapting traditional filmmaking roles to virtual production. A second Epic post, announcing Volume 2 in April 2021, documents that the project continued and expanded into "remote collaboration, visualization, in-camera VFX, and animation," evidence the first guide was treated internally as an ongoing reference rather than a one-off document. Neither post claims Epic's tools are the only virtual-production method in the industry; both describe what the company's own guide documents.

Production context

A field guide published by a real-time-engine maker functions, editorially, as both documentation and promotion for its own toolchain, and the two purposes are not separable from the text alone. The guide's stated aim, letting a director scout a virtual set in VR or light an LED-wall scene with accurate real-world reflections before a camera rolls, addresses a real production constraint: the cost and inflexibility of committing to a location or a final visual-effects look late in a schedule. The named interview subjects, drawn from production, effects and camera departments rather than only Epic's own staff, is consistent with a guide aimed at working crews rather than only software buyers, though the two blog posts are the company's own account of that intent.

Reference versus imitation

Citing this guide correctly means treating it as Epic Games' own documented workflow, not a neutral survey of virtual production, since a rival engine or LED-volume vendor documents its own version of similar techniques differently. The named interviewees' statements, as Epic describes them, belong to those individuals; reusing the guide's case studies without noting they describe productions that used Epic's specific toolchain would blur a vendor's documentation into a broader industry claim it does not make.

• Does a workflow guide published by a tool vendor say so plainly, or present itself as vendor-neutral?
• Are the named case studies and interviewees specific enough to check against other accounts?
• Did a later volume or update change what the original document claimed?

Two dated posts from the same publisher, almost two years apart, are enough to show a documented process changing over time; a single undated download would not carry that evidence.