Points To Image (DEBUG)

This one's a drawer of spare parts. Points To Image advance (DEBUG) is the pack author's test node that escaped into the release: it combines the orthographic and projection renderers into a single node, adds a camera switch to pick between them, keeps the hole-filling controls, and then throws in a toggle called panda that does... something. Let's talk about that.

The name is the honest one. "DEBUG" is in the title because this is where the author experiments, and it shows. It's not that the node is broken - it renders fine - it's that it's a superset of things you can get more cleanly from the two dedicated "advance" renderers, with a couple of quirks that are worth knowing before you build a workflow around it.

How it works

Under the hood it's the exact same render_points_fast machinery as the other renderers: perspective or orthographic projection, depth-as-brightness, nearest-point-wins sorting. Two things set it apart.

The camera dropdown (Orthographic / Projection) is genuinely handy if you're A/B-ing the two looks - flip it and re-run, no node swap needed. Everything else, the fov, correct, ksize, threshold controls, behave exactly like their counterparts in the advance renderer nodes.

And then there's panda. Despite the name, nothing panda-related happens. It's a toggle for which deduplication method sorts out overlapping points during render - OFF uses pandas (drop_duplicates), ON uses numpy's structured unique, which skips the pandas import path and can be a bit faster on big clouds. It's an implementation detail with an animal for a label. Leave it OFF unless you're chasing render speed on a huge cloud.

The inputs, briefly

• images - size template for the output.
• points - the Points3D cloud.
• color - RGB vs depth-as-grayscale.
• fov (1–2000, default 35) - perspective field of view.
• correct / ksize / threshold - the hole-fill pass (see the advance renderer articles).
• camera - Orthographic or Projection. The one real convenience here.
• panda - dedupe implementation choice. See above.

Output: IMAGE - a normal image tensor.

Install

Same as the pack: Manager → "ComfyUI_depthMapOperation", or:

cd ComfyUI/custom_nodes
git clone https://github.com/chri002/ComfyUI_depthMapOperation

Restart. No models, no keys; deps are stock ComfyUI ones (torch, numpy, opencv-python, scipy, pandas).

Where people get burned

Mostly by overthinking it. Don't treat this as the "real" version of the renderers - the two advance nodes are cleaner to reason about, and the author's README only documents the stable ones. Grab this one when you want to flip between projection modes in one place, or when you're debugging why a render looks wrong and want the camera and correction controls side by side. And given this is an explicit debug/experimental node in a small one-maintainer pack, treat any odd output as "that's the test build for you" before assuming you mis-set something. Single frame only, as always.