Atlas Export USD
The solved camera as a USD file for your USD pipeline
- solve
- project
- usd_path
AtlasExportUSD writes the recovered camera as a USD camera asset (camera.usda) into the directory you choose. It's the USD lane of the pack's export fan-out: where the Nuke and Maya exporters build whole projection scenes, this one does exactly one thing - put a real USD camera where your USD-based pipeline can read it. If your studio standardizes on USD (and a growing chunk of the VFX world does), this is the node that moves the solve out of ComfyUI and into the shot.
The .usda (ASCII USD) format is worth calling out specifically: it's a text format, which means the exported camera is diffable, reviewable, and recoverable - you can see the focal length and orientation right in the file. It's the same philosophy as AtlasExportSolveJSON, but speaking the language your USD tooling already speaks.
How it works
You feed it the solve and an output_dir, and it serializes the solved camera through the pack's USD exporter to camera.usda in that directory. Wire a project in and it routes into the project tree's usd/ lane instead, superseding output_dir - the same routing convention every export node follows. It's a terminal node, so the export fires and writes the file even with nothing connected downstream, and it returns the usd_path as a string so you can hand it to the next step in the graph (or just read it off).
The inputs
solve and output_dir (default atlas_exports) are required. project is optional. The single output is usd_path.
Install and gotchas
Part of the pack: install once via ComfyUI Manager (search atlas-camera) or git clone https://github.com/mikejamesvfx/atlas-camera.git into custom_nodes, then restart. The node is a pure-Python serializer - no extra dependencies, no GPU, no model downloads. (If you're on the optional [usd] extra path it pulls the USD tooling; the core solve export itself stays light.)
The gotchas are what you'd expect from a minimal export: it writes the camera only - no geometry, no plate, no projection. If your pipeline needs the derived relief mesh in the same stage, export it separately via AtlasExportReliefMesh and reference it in. And remember output_dir is relative to ComfyUI's working directory unless you give it an absolute path. Beyond that there's little to trip over - which is the point. A solved camera that a USD pipeline can load without ceremony is exactly what this node promises.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| solve | ATLAS_SOLVE | — | |
| output_dir | STRING | atlas_exports | — |
| projectopt | ATLAS_PROJECT | Optional delivery project from AtlasProject — routes this export into the project tree's usd/ lane and supersedes output_dir. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| usd_path | STRING | — |