BV Detailer Loop Result (internal)

The BV Detailer Loop ends when you wire your Save node to BV Detailer Loop End's final_image output. But that final_image doesn't materialize out of thin air - it comes from this node. BV Detailer Loop Result (internal) is the hidden node that unwraps the accumulated image from the loop state and hands it to the public End node. Category __hidden__, created during graph expansion, never placed by hand. The unglamorous last line of a clever loop.

How it works

It's almost insultingly simple. One input:

• loop_state (BV_DETAILER_LOOP_STATE) - the state as it stands when the loop exits.

One output:

• final_image (IMAGE) - the value at the loop state's current_image slot.

Remember how the internal Loop Advance node keeps replacing current_image with each iteration's processed image? By the time the While End gate decides the job list is exhausted, that slot holds the image after the last detail pass. Result just extracts it. The accumulation happened everywhere else; this node is the read at the end of the pipeline.

That's the whole mechanism: the loop state's current image is the running result, so "the final image" is just "the current image when the loop stops." No merging, no stitching - the compositing was done by your Impact detailer paste step each iteration.

Where it sits

BV Detailer Loop End expands into this node (alongside Advance and While End) at queue time, and wires its output through as final_image. You'll only ever see it if you're watching a graph mid-execution or inspecting an expanded workflow, and in both cases the right reaction is "yes, that's the machinery, moving on."

What's useful about knowing this

Two small debugging wins. First, if final_image looks like the last job's output and nothing else, that's correct behavior - the final image is the image after the last job, which already contains every earlier job's fixes. Second, if the loop ends early, the result is simply the state at the job index where it stopped; the readable diagnosis is upstream in the plan's plan_summary (job count) rather than anything in this node.

Installation is the pack, same as all the others:

cd ComfyUI/custom_nodes
git clone https://github.com/BlackVortexAI/bv_nodepack.git

or ComfyUI Manager → BV Node Pack, then restart and hard-refresh the browser. And then never think about this node again - it's the exit ramp, not the road.