Python · Render Setup · Deadline
QC render and turntables
Problems with assets and caches are cheapest to fix before they reach a shot. This system rendered every published asset and cache under a standard light rig automatically, and gave artists a turntable tool for looking at their work in context, so supervisors could approve what they had actually seen.
How it fits together
PublishAn asset or cache is published
Scene buildBase scene, shaders, light rig and caches
Render layersPer-renderer layers and outputs
Farm and reviewSubmitted, rendered and published back
What I built
Renderer-agnostic core
- A base class that defines every step of a QC render, with renderer-specific subclasses for Arnold and V-Ray.
- The renderer chosen from configuration, so a show could switch without code changes.
- Render layers, collections and overrides built through Render Setup.
Scene assembly
- Automatic discovery of the right caches, with scoring to pick the best match.
- Lookup of published shaders and the light rig for the asset or shot.
- USD references brought in as renderer standins.
- Cameras found through tags rather than naming conventions.
Farm and tracking
- Render farm jobs built and submitted with their plug-in settings.
- Versions and tasks created in production tracking for every render.
- Render elements and EXR metadata written for compositing and review.
- An option to submit QC renders automatically as part of publishing.
Turntable tool
- HDRI lighting, backdrop and camera setup in one click.
- Shading modes for wireframe, UV checker, ambient occlusion and displacement.
- AOV selection and a camera keyframe editor.
- Settings saved and loaded so turntables matched across a team.
Scale
2 renderersbehind one interface
Automatictriggered on publish
Turntablesfor look development and modelling review
Farm readysubmitted and tracked end to end
This was studio work, so the code stays with the studio. This page describes what the system did, not how it was written.