Simplify accumulator variant collection

This commit is contained in:
2026-06-24 23:11:37 +02:00
parent 04c4c0d37c
commit ed6c7b8dc0
2 changed files with 46 additions and 17 deletions
+14 -3
View File
@@ -120,9 +120,20 @@ you want to update each iteration. They are separate from the collector and grow
dynamically in the UI as you connect them.
`SxCP Accumulator` stores outputs across executions under a `store_key` or the
node id. Put it after an image-producing step inside or after a loop, connect the
generated `image`, and connect `For Loop Start.index` to `entry_id` when you want
reruns to replace the same row instead of appending duplicates. Its outputs are:
node id. Put it after an image-producing step inside or after a loop and connect
the generated `image`.
For camera/pose tuning, leave `action=append_variant`. Every rerun is kept as a
new variant, so you can regenerate row 1 several times without managing ids. If
you connect `For Loop Start.index` to `entry_id`, variants are labelled by row
internally; they still append instead of replacing.
For deterministic loop resume/dedupe, set `action=replace_by_entry_id` and
connect `For Loop Start.index` to `entry_id`. Optional `entry_tag` lets multiple
branches share the same row index without overwriting each other, such as
`soft`, `hard`, or `upscale`.
Its outputs are:
- `collection`: all stored values, or images when no explicit `value` is wired.
- `image_batch`: all stored images as one ComfyUI image batch when they share