Atlas Export Maya Review Scene

AtlasExportMayaReviewScene builds a native Maya .ma review scene around the solved camera, so you can open the solve in Maya without reconstructing it by hand. It's the Maya member of the pack's DCC export family, and its job is narrower and more honest than a full production export: it gives you a scene you can actually review - camera in place, plate and (optionally) the real relief mesh loaded, ready to look through and move around.

The killer detail is the relief_mesh_obj_path input. Wire the obj_path output from AtlasExportReliefMesh into it and the derived relief mesh gets imported into the Maya scene instead of being omitted - you see the real projection geometry, not just a camera floating in space. Without it you get the camera and plate, which is the "camera only" review; with it, you get the whole 2.5D scene.

How it works

Give it the solve and an output_dir; it writes a Maya scene file and returns the path to the open-scene file as a string. Like every export node in the pack it's terminal (writes even with nothing downstream) and honors the project input - wire one from AtlasProject and the scene lands in the project tree's maya/ lane instead of output_dir. An optional output_profile embeds OCIO-style output/profile metadata into the review package, which matters once the plate is colour-managed.

The inputs

solve and output_dir (default review_packages) are required. Then:

• relief_mesh_obj_path - the obj_path output from AtlasExportReliefMesh; set it to see real derived geometry in Maya.
• output_profile - optional OCIO-style metadata to embed.
• project - optional project-tree routing.

The single output is a string with the path to the .ma file.

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 export is pure Python (the README's dependency-free tier covers the DCC exporters), no GPU, no models. Maya itself is on you - this node writes the file; opening it is still a Maya task.

Gotchas: output_dir is relative to ComfyUI's working directory unless absolute. And there's a naming trap to watch - the default output dir is review_packages, same as AtlasExportReviewPackage, so if you export both into the same place give one of them an explicit directory or you'll be sorting files by timestamp. Beyond that it's about as frictionless as a Maya handoff gets: solve, export, open, look.