Atlas Export Relief Mesh (OBJ) 🗻

AtlasExportReliefMesh is where the 2.5D projection stops being a viewport trick and becomes an actual geometry file you can hand to another tool: it writes the depth-following relief mesh as an OBJ or GLB (or both), with the plate's projection baked into the UVs. This is the "give the projection to anyone" export - Blender, Maya, game engines, a texture bake - and it's also the mesh that feeds the Nuke and Maya exporters when you want real derived geometry in those scenes instead of a flat card.

The "relief" part is the whole idea: instead of a flat plane, the mesh follows the monocular depth estimate (fed by the solved focal length, which matters - depth seen through the wrong lens is depth in the wrong place). From the recovered camera's viewpoint the plate reassembles exactly; from anywhere else you get parallax, which is precisely the illusion you're buying.

How it works

Give it the solve, the image (the plate to project), and an output_dir. It writes obj_path and glb_path (with format defaulting to both). The critical default is use_solve_mesh - on, it exports the relief mesh already on the solve (from AtlasInput or the derive nodes) so all of its edge tuning carries over. Turn it off to re-derive the mesh here instead, which unlocks the re-derive-only tuning inputs (max_edge_factor, normal_edge_deg).

A few genuinely useful options:

• fill_interior_holes (default off) - an export-only fan-fill of small interior tear holes so the mesh retopologizes and renders cleanly, scoped by max_hole_edges and the fill_depth_near_m/fill_depth_far_m band bounds. The live viewport projection mesh is never touched.
• retopo_method - export-only retopology (off, quad, decimate, voxel_remesh) with a vertex budget, for when the derived mesh is too messy to hand to a real DCC.
• grid_long_edge (default 128) and depth_edge_rel - mesh density and the relative depth jump that tears the mesh.

Outputs: obj_path, glb_path, a preview_solve, and report.

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. The exporter itself is lightweight, but the mesh comes from depth: the default Depth Anything V2 backend is transformers-only (no extra install) - the heavier neural/GeoCalib path is only needed if you're re-deriving without an existing solve mesh.

Gotchas: output_dir is relative to ComfyUI's working directory, and the Nuke exporter resolves your obj_path to absolute precisely so the generated scripts stay portable - keep that convention in mind. If the exported mesh comes out "combed" or shredded on deep or interior scenes, that's the world-space edge tear threshold (max_edge_factor) tripping on grazing surfaces; raise it to 40–80, or better, tune it upstream on AtlasInput and let use_solve_mesh carry it through. And remember the OBJ is projected but not textured-on-disk - the plate rides in the UVs and the projection is applied live in the consuming tool. That's the intended pipeline, not a bug.