🌀 BV Vector Edit Range

Editing one block weight at a time is fine until you want to wipe out a whole family. BV Vector Edit Range is the blunt instrument: set a start index, an end index, and a value, and every entry in between becomes that value in one shot. It's the fastest way to experiment with "what does this LoRA do if I turn off the entire second half of the model?"

That's the killer use case. On FLUX the transformer is split into the MMDiT double-stream blocks first, then the single-stream DiT blocks. Zeroing the whole DiT span is a single operation here, and the difference in output tells you instantly what that half of the network was doing. For comparing "full LoRA" versus "MMDiT only" versus "DiT only," this node is basically three drags on sliders away.

Inputs

• vector (required) - the list you're editing.
• start_index (default 0) / end_index (default 1) - the two bounds of the span, zero-indexed.
• new_value (default 0) - what to write into every slot in that span. 0.0 to mute a region, 1.0 to restore it.

Output

• VECTOR (LIST) - the vector with the span overwritten, everything else untouched.

Since both edit nodes operate on a LIST, you can mix them freely - a range wipe followed by a couple of surgical single edits, or vice versa. The graph reads as a sequence of deliberate changes.

Install

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

or ComfyUI Manager → "BV Nodes", then restart. No dependencies, no models.

The two things to check

First, confirm whether the bounds are inclusive before you trust a result - the classic failure is a span that's one block off from what you intended, and the only symptom is an output that's subtly wrong. Second, mind the zero-indexing when you compute the span for a 58-slot FLUX vector; entry 57 is the last one. If the result looks like nothing happened, you probably asked for a span that doesn't exist or grabbed the wrong end of the model.