Wiki · Autograph / OpenUSD / 3D workflow
Autograph OpenUSD scene handoff checklist
A practical checklist for testing whether a USD scene is usable in Autograph before relying on it for motion-design, comp, or VFX layout work.
Why this page exists
Autograph is positioned as a 2D/3D motion graphics and VFX application with a 3D environment based on Pixar's OpenUSD. That makes USD a useful bridge format, but it does not remove the need to test the exact scene structure, assets, animation, materials, cameras, and render expectations used by a project.
Minimum scene to test
- One hero asset: a representative model with real hierarchy depth, transforms, pivots, UVs, materials, and texture paths.
- One animated asset: frame range, time samples, transform animation, deformation if used, and the intended frames-per-second convention.
- One camera: focal length, aperture or sensor assumptions, clipping, filmback, target framing, and animated camera moves.
- One light setup: imported lights if they are expected to survive, plus a simple fallback if the look will be rebuilt in Autograph.
- One comp target: a 2D plate or background layer, so scale, alpha, depth order, and render framing can be judged in the same composition.
Structure checks
- Record whether the file is
.usd,.usda,.usdc, or.usdz, and keep a copy of the exact tested file. - Open the scene in at least one second USD-aware tool before blaming Autograph. The first question is whether the USD package itself resolves correctly.
- Check references, payloads, sublayers, texture paths, and any external asset paths. A scene can look complete on the exporting workstation but fail on another machine.
- Confirm the scene units and up-axis. Camera framing and apparent scale problems often come from convention mismatches, not broken geometry.
- Make a note of unsupported or ignored items rather than silently rebuilding them. That list becomes the project handoff rule.
Material and render checks
- Assume that material translation is a risk surface. Compare albedo, opacity, roughness, metallic, normals, texture color spaces, and any emissive surfaces.
- Check whether texture paths remain portable after the USD is moved to a clean test folder.
- Compare viewport preview, Autograph render, and a second host render. Do not judge only one viewer.
- If the project depends on renderer-specific shaders, bake or simplify a representative test before approving the handoff.
Animation checks
- Confirm frame range, frame rate, interpolation, looping, stepped keys, and sub-frame motion if motion blur is expected downstream.
- Test an animated camera and an animated object separately, then together.
- Render a short range and compare against the exporting host. A still frame match does not prove animation handoff is stable.
Practical rule
Treat OpenUSD support as a scene-specific workflow surface, not a blanket promise. USD can carry complex composition arcs, references, payloads, layers, cameras, materials, animation, and asset relationships; the production question is which parts of the current scene are visible, editable, renderable, and repeatable inside the current Autograph build.
Useful next pages
- Autograph first verification project checklist
- Autograph EXR channel and data-pass checklist
- Autograph OpenFX plugin compatibility note
Sources checked
- Maxon Autograph product page — checked 2026-07-03. Used for Autograph feature context: OpenUSD-based 3D environment, 2D/3D combination, Filament rendering, OpenFX, EXR, ACES, OCIO, and plugin positioning.
- OpenUSD Introduction — checked 2026-07-03. Used for the general USD context and links into concepts such as stages, layers, references, animation, transformations, materials, cameras, and rendering.
- OpenUSD Terms and Concepts — checked 2026-07-03. Used for USD terminology around scene description concepts and asset-structure vocabulary.