Sampler Switch

Sampler Switch sits in the DEPRECATED section of the RvTools menu, and that label is doing real work. It's a two-input switch that outputs a sampler name, the same pattern as every other switch in this pack - Input picks input1 or input2, and the result comes out typed as a sampler string, ready to feed a KSampler's sampler_name port.

Why it exists and why it's deprecated

Back when this pack was being built, people wired sampler names around as values - you'd switch between euler and dpmpp_2m the way you'd switch between two images. The switch made that swap dynamic. But ComfyUI already ships a native "KSampler Selector"-style widget, and the RvTools author later built dedicated selector nodes (the Scheduler Selectors in this same pack) that do the job more cleanly: instead of routing a signal through a switch, a selector is just a dropdown whose value is the output. A switch routes; a selector declares. The switch remained for backwards compatibility, marked DEPRECATED, and every new workflow should prefer the selector.

The inputs that matter

• Input - 1 or 2, which side to pass through.
• input1, input2 - both are * (any-type) connections with a default of [], so they're wire-only inputs. Connect two nodes that output sampler names (a scheduler/sampler selector, or another switch) and pick.

The output is typed against ComfyUI's full sampler list - everything from euler, heun, dpmpp_2m, lcm to uni_pc and the _cfg_pp and res_ variants - so a KSampler will accept it directly.

Installing

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI-RvTools_v2

Restart ComfyUI or use ComfyUI Manager (search "ComfyUI-RvTools_v2"). No models, no special deps beyond the pack's standard set.

Real-world notes

Two honest warnings. First, the whole pack is deprecated in favor of ComfyUI_Eclipse, and this node is deprecated within the pack - it's the most redundant node in this whole set. Second, don't treat this as an excuse to go sampler-swapping blindly. The sampler choice and the scheduler choice are two separate axes, and "DPM++ 2M Karras" style fused thinking has bitten people on flow-matching models like Flux, where aggressive schedules actively break generations. If you're switching samplers at runtime for a reason (A/B testing, model family swaps), fine - just know why before you wire it. And if you run into a "missing node" error from an old workflow, remember v1 RvTools had its own differently-named versions of these nodes, and that repo is gone; you're looking at the v2 names here.