PIPE // DOCS
USD-NATIVE VFX PIPELINE // GUIDES, REFERENCE AND LIMITS
PIPE takes a show from an empty database to a delivered shot. One launcher starts Houdini, Nuke and OpenRV in the right context; every publish is a versioned record; assets are baked to USD that shots load with a single node; overrides are layers you author from a graph; renders run on a scheduled farm. These pages say how to do each of those things, tab by tab.
START_HERE // THE SHORTEST PATH
Twelve steps from nothing to a rendered shot. Each opens the guide that explains it.
THE_LAUNCHER // FOUR OF NINE TABS
THE_GUIDES // BY JOB
[BASIS_OF_EACH_GUIDE]
Every guide ends with its basis. RUN means the flow was exercised while the code was being developed. CODE means it was written from the source: the steps and field names are real, but nobody re-ran the flow for this document, so expect small differences in wording on screen. The feature list marks each feature VERIFIED EXISTS or GAP, and 06_LIMITS lists what does not work.
LAUNCHER_TABS // WHAT EACH TAB IS FOR
The launcher has nine tabs. The SHOW selector over the banner row decides which show every tab displays.
DCC_TOOLS // INSIDE HOUDINI, NUKE AND OPENRV
The shelf tools, HDAs and panels that come with the pipe.
CONCEPTS // HOW THE PIPE THINKS
The few ideas the rest of the documentation relies on.
GLOSSARY
FEATURES // EVERYTHING THE PIPE DOES
LIMITS // WHEN SOMETHING DOES NOT WORK
Symptoms first. Each entry says why it happens and what to do. Several of these are limits of the current pipe, not mistakes.
ROADMAP // WHAT IS NOT BUILT
Nothing on the right is available today.