🌀 BV Vector Edit Range Dropdown FLUX

The numeric range editor works, but computing 58-slot index spans in your head is exactly the kind of error-prone work that should be somebody else's problem. BV Vector Edit Range Dropdown FLUX is the range version with the training wheels on: both the start and end of the span are dropdowns of named FLUX layers - INPUT LAYER, MMDiT idx 0–18, DiT idx 0–37 - so "from MMDiT idx 3 through DiT idx 22" is a sentence, not arithmetic.

This is the node you reach for when the experiment is "what happens if I mute this whole region." Zero from MMDiT idx 0 to MMDiT idx 18 and you've silenced the entire double-stream half while keeping every single-stream block at full strength. That's a one-node change now, where it used to be a spreadsheet.

Inputs

• vector (required) - the FLUX-ordered list being edited.
• start_index / end_index - both dropdowns over the named FLUX layer map. "CHOOSE" is the unset placeholder on both.
• new_value (default 0, stepped 0.01) - the value written to every slot between the two named layers.

Output

• VECTOR (LIST) - the vector with the whole span overwritten, the rest preserved.

Same chaining behavior as the rest of the family: build with BV Vector of Length-n, run a range wipe here, spot-fix individual slots with the single-edit version, and the graph stays readable the whole way.

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 one thing to nail down

As with the numeric range node, check whether the span you pick matches the "everything between" behavior you expect - a span that's off by one layer is a silently wrong result. And remember both dropdowns are FLUX-specific: this node only makes sense for FLUX block-weight vectors, so keep it paired with length-58 vectors in FLUX order. Non-FLUX models get the plain numeric range editor.