VRGDG_DisplayIndex

This is the rare ComfyUI node with zero mystery: VRGDG_DisplayIndex takes an integer and shows it to you as text. One input, one output, that's it. It's marked as an output node, which means it renders its result directly on the canvas so you can read it at a glance instead of hunting through node logs.

Why would you ever need that? Because in a big workflow - the kind VRGameDevGirl's video pipelines build - the interesting numbers are computed in the middle of the graph. Your current batch index, the frame number, the wrapped index coming out of a cycling picker. When something's picking the wrong image or the wrong scene, you want to see what value it's actually carrying before you start debugging the logic that produced it. That's exactly where a display node earns its keep.

How it works. You wire an INT into index and it echoes it as the index_display STRING output, rendered on the node. That's the entire mechanism - there's no math, no formatting options, nothing to configure. It's plumbing, and it knows it.

Where it sits in the wider pack. This is a companion to the pack's index-obsessed nodes: the cycling text pickers, VRGDG_GetIndexNumber, VRGDG_GetRunIndexFromJson, the image switches. All of those produce or consume indexes, and when you're chaining three of them together it's shockingly easy to lose track of which number is which. Drop a DisplayIndex after each one and the whole graph becomes readable.

Installing it. Same as the rest of the pack:

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

or search vrgamedev in ComfyUI Manager. Restart, and it'll be under utils.

There's not much to troubleshoot because there's not much to break. If the node shows nothing, check that the upstream node actually ran - a display node shows the value from the last execution, so a failed or skipped upstream leaves it stale. If you want the value inside a prompt, this isn't the node: it outputs a string, but the real use is visual. A plain ShowText-style node or the string output of whatever produced the number is the better wire for prompt injection. Use DisplayIndex for the human, not the prompt.

It won't change your life. But the first time a multi-scene workflow grabs the wrong frame and you can see the index it was handed, you'll be glad it's there.