🌀 BV Vector Edit

Once you have a block-weight vector - say a 58-long all-ones list from BV Vector of Length-n - the next thing you'll want is a surgical way to change a single entry. That's BV Vector Edit: pick the slot by index, type a new value, get the whole vector back with just that one entry changed.

Block-weight tuning is where this shines. The classic move is turning off one family of blocks to see what a LoRA actually contributes - drop the single-stream DiT blocks to near zero and suddenly the LoRA's texture-sculpting stops, or kill the input layer and watch the prompt-following change. Doing that with raw lists is miserable; doing it with one node per block you want to touch is a clean, legible chain.

Inputs

• vector (required) - the list of floats you're editing. Comes from a constructor like BV Vector of Length-n, another edit node, or anything else that produces a LIST.
• entry_index (default 0) - the slot to change. Zero-indexed, so 0 is the first entry. If you're mapping this onto FLUX's layout, you'll be counting: input layer at 0, then MMDiT blocks, then the DiT blocks.
• new_value (default 0, stepped 0.01) - the value to write into that slot. 0.0 to kill a block, 1.0 for full strength, anywhere between for partial.

Output

• VECTOR (LIST) - the full vector, exactly as it came in except for the one edited entry.

You can chain these - edit slot 5, feed the output into another BV Vector Edit for slot 12, and so on. Each link in the chain is one deliberate change, which makes the final vector auditable: you can read down the graph and see exactly which blocks you touched.

Why not the numeric route forever

Counting indices across 58 FLUX slots gets old fast, which is why the pack also ships BV Vector Edit Dropdown FLUX - same operation, but entry_index becomes a dropdown of layer names. For quick experiments the numeric version is fine; for anything nontrivial on FLUX, the named version is the one you'll reach for.

Install

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

or ComfyUI Manager → "BV Nodes", then restart.

The off-by-one trap

entry_index is zero-based and there's no bounds feedback - ask for entry 58 on a 58-long vector and you're past the end. If a downstream node starts complaining, count your indices before you blame it. Also: no output node needed; the VECTOR output just feeds the next node in the chain.