MoGe-2 Model (CRT AutoDL)

Every monocular 3D pipeline has the same camera problem: a single 2D photo doesn't tell you the focal length, and without it the reconstructed 3D comes out at the wrong scale. In the SAM3D Body pipeline, MoGe-2 is the piece that solves that - it reads the photo, estimates depth and the camera's field of view, and gives the body reconstruction a correct frame of reference so the person's proportions aren't distorted.

So yes: this is the same model as CRTAutoDLPixal3DMoGeModel, in a different category. The pack defines one shared moge_model entry and points both nodes at it. If you've run either one already, the file is on disk and there's literally nothing to download.

The one output

moge_model - a MOGE_MODEL socket. In the SAM3D Body workflow it feeds the native MoGeGeometryToFOV node, and the resulting FOV goes into SAM3DBody_Predict's fov input. The predict node's tooltip is clear about why you'd bother: the FOV "affects predicted depth and absolute scale." Leave it at 0 and it falls back to a ~53° default guess; wire MoGe in and the mesh matches the actual photo geometry. If you care about the result looking like the person in the frame, wire it in.

Install

The pack install, same as always:

cd ComfyUI/custom_nodes
git clone https://github.com/PGCRT/CRT-Nodes
pip install -r requirements.txt

Restart ComfyUI (or install via Manager, search CRT-Nodes). Recent ComfyUI required - the node delegates to core comfy_extras.nodes_moge.

Gotchas

• No double download. The moge_2_vitl_normal_fp16.safetensors file is shared with the Pixal3D family, and the node checks disk before fetching. One download total across both pipelines.
• The FOV is scale, not style. Getting this wrong won't break the render - the body will still reconstruct - but the proportions will be off, and a wrong-looking body defeats the purpose of a body model. Treat the MoGe→FOV wire as part of the standard assembly, not an optimization.
• Updates. Red node or NaN after a pack update means sockets changed; right-click → Fix node (recreate).

This is the quietest node in the SAM3DBody family - no parameters, one shared download, a single socket - and that's exactly why it's worth knowing about. When you assemble the workflow (RT-DETR for person boxes, SAM 3.1 for masks, this for camera, SAM3DBody_Predict for the mesh), the pieces that never get blog posts are the ones that keep the result honest. This is one of them.