VRGDG_ImageIndex0HUMOEDIT

Every workflow has a special case hiding in its logic. In the pack's HUMO multi-scene editing pipelines, the special case is zero: when the scene index says 0, the node downstream expects a blank image to start from - not one of the reference frames. VRGDG_ImageIndex0HUMOEDIT is that special case, packaged. Per the author's own one-line description, it "returns an EmptyImage-style image when the comma-separated index string contains 0."

How it works. You feed it image_index - a string, which is the giveaway that it's checking a comma-separated list rather than a single number. If that string contains a 0, the node produces a blank image at your requested width × height (512×512 by default). If the index string doesn't contain 0, it returns nothing - which, in ComfyUI terms, means the output is effectively absent and whatever's downstream has to handle that gracefully. That's the whole logic: "if this scene is index 0, the edit starts from a clean slate."

Why it exists. Image-edit and multi-scene pipelines often need to say "no source image for the first shot." You could build this with an empty-image node plus a switch, but that's three nodes and a conditional you have to keep straight. This collapses it into one widget that checks the exact condition the workflow needs. The "0 means blank" convention also tells you the rest of the pack follows a consistent numbering story - 0 is the sentinel, 1+ are real images.

The inputs. image_index (a string like "0" or "1,0,3"), width, height. The last two just control the blank canvas size; match them to whatever resolution your sampler expects or the empty image will be resized on the way in.

The output. One IMAGE. Either the blank canvas (when 0 is present) or nothing.

Installing. Same pack:

cd ComfyUI/custom_nodes
git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl

or install vrgamedev via ComfyUI Manager and restart.

Troubleshooting. Two things bite. First, remember the check is a substring check on a string - "10" contains "0", so an index string that includes 10 will also produce a blank image. If your scene indices go past 9, this node can surprise you; that's a genuine footgun with this design, so keep it in mind before wiring scene 10 through it. Second, "returns nothing" isn't an error - it's the intended behavior when 0 isn't in the string, so don't go hunting for a bug when the output is empty for non-zero indices. If you need the opposite (blank unless 0), this is the wrong node; the pack's regular image switches handle that case.