Nodes/Atlas Camera/Atlas Export Nuke Layers 🎞
ComfyUI Node

Atlas Export Nuke Layers 🎞

Export the whole depth-band stack to Nuke, layer by layer

By mikejamesvfxΒ·Created 3 months agoΒ·Updated a day agoΒ· 1
Atlas Export Nuke Layers 🎞
  • solve
  • output_profile
  • project
  • nk_path
  • summary
β—„output_diratlas_exports/nuke_layersβ–Ί
β—„retopo_methodoffβ–Ί
β—„retopo_target_vertex_count2000β–Ί
β—„retopo_smooth_iterations0β–Ί
β—„retopo_crease_angle30β–Ί
β—„retopo_pure_quadfalseβ–Ί

AtlasExportNukeLayers is the Nuke export for the 2.5D matte-painting case: it writes the entire depth-band layer stack - every clean-plate layer, its mesh, and its projection - to a Nuke scene, not just a single camera card. Where AtlasExportNuke exports one projection graph, this one fans out to per-layer Nuke scenes for the multi-band clean-plate setup you build with the pack's layers machinery: sky dome, depth-band clean plates, all as separate layers that comp can manipulate independently.

That's the difference that matters for real matte painting. A single flat card projection is fine for a subtle dolly; a foreground building, a mid band, and a sky dome each need to be their own layer if you're going to move the camera meaningfully or fix one band without touching the others. This node is how the layered stack leaves ComfyUI in one piece.

How it works

You feed it the solve and an output_dir, and it writes the layer meshes (OBJs) and the Nuke scene that assembles them, returning the nk_path and a summary. The optional retopo_method applies an export-only retopology pass to every layer mesh before Nuke writes its OBJs - same options as the mesh exporter (off, quad, decimate, voxel_remesh) - with retopo_target_vertex_count, retopo_smooth_iterations, retopo_crease_angle, and retopo_pure_quad to tune it. Retopologizing before export is a genuinely useful move: clean quads on the layer meshes make them far more pleasant to work with in Nuke's 3D viewport and to hand to a texture pass.

An optional output_profile carries OCIO-style annotations, and project routes the export into the project tree's nuke/ lane.

The inputs

solve and output_dir (default atlas_exports/nuke_layers) are required. Then the retopo block and output_profile/project. Outputs are nk_path and summary.

Install and gotchas

Part of the pack - ComfyUI Manager β†’ search atlas-camera, or git clone https://github.com/mikejamesvfx/atlas-camera.git into custom_nodes, restart. Pure Python exporter, no extra dependencies, no GPU.

Two gotchas. First, the layers have to exist upstream: this node exports the layer stack on the solve, so if your graph hasn't actually built the multi-band layers (the layers path on AtlasInput or the staged layer nodes), there's nothing to fan out - you'll get a thin export and a summary that says so. Second, retopology is export-only here, which is the good kind of behaviour: your live viewport projection mesh is never touched, only the files Nuke reads. If you were hoping a layer export would give you painterly-quality topology straight off, set retopo_method to quad and budget some time for it. For the layered clean-plate stack - the actual matte-painting workflow this pack exists for - this is the handoff to Nuke.

CategoryAtlas/10 Β· Export

Inputs (9)

NameTypeDefaultDescription
solveATLAS_SOLVEβ€”
output_dirSTRINGatlas_exports/nuke_layersβ€”
output_profileoptATLAS_OUTPUT_PROFILEOptional OCIO-style output/profile metadata for annotations.
retopo_methodoptCOMBOoffExport-only retopology applied to EVERY layer mesh before Nuke writes its OBJs.
retopo_target_vertex_countoptINT2000100–100000β€”
retopo_smooth_iterationsoptINT00–20β€”
retopo_crease_angleoptFLOAT300–180β€”
retopo_pure_quadoptBOOLEANfalseβ€”
projectoptATLAS_PROJECTOptional delivery project from AtlasProject β€” routes this export into the project tree's nuke/ lane and supersedes output_dir.

Outputs (2)

NameTypeDescription
nk_pathSTRINGβ€”
summarySTRINGβ€”