🌀 BV Vector Edit Selector FLUX

If the dropdown editors still feel indirect, the BV Vector Edit Selector FLUX goes fully visual: instead of typing one index or picking two ends of a range, you get a checkbox for every FLUX block. Tick the ones you want, set one value, and every checked block gets rewritten to that value in a single pass. The unchecked ones stay exactly as they were.

The checkbox list is the complete FLUX map: INPUT LAYER, then MMDiT idx 0 through 18, then DiT idx 0 through 37 - 58 toggles in all. It's the block-weight vector expressed as a form, which makes it the natural pick when you want to do something messy like "bump the input layer and every fourth MMDiT block to 0.7, leave everything else alone." Picking a scattered handful of blocks with the single-edit node would mean a chain of six or seven nodes; here it's six or seven checkboxes.

Inputs

• vector (required) - the FLUX-ordered list.
• new_value (default 0, stepped 0.01) - the value applied to every checked slot.
• One boolean per block: INPUT LAYER, MMDiT idx 0–18, DiT idx 0–37 (all default off).

Output

• VECTOR (LIST) - the vector, with each checked slot set to new_value.

This node is where the "set all selected to a value" workflow lives, and it's a genuinely different editing model from the range nodes: you're not defining a span, you're curating an arbitrary selection. The cost is that it's verbose on the canvas - 58 toggles is a tall node - so it's best for final tweaks, not as the spine of a long chain.

Install

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

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

Notes

Two habits keep you out of trouble. First, leave new_value at a deliberate strength - with everything defaulting to off, an accidental all-checked with new_value 0.0 quietly zeros the entire vector, which is a confusing result to debug downstream. Second, same architecture caveat as the other FLUX variants: the toggle list is FLUX's layout, so feed it length-58 vectors in FLUX block order. And it's not a filter - unchecked slots keep their current values, which is usually exactly what you want.