Scheduler Selector (Efficient+Impact)

If you've got both Efficient Nodes and Impact Pack installed, you've got two packs that each want to own the scheduler input - and neither list matches vanilla's exactly. Scheduler Selector (Efficient+Impact) is the crossover version: one dropdown for the Efficient list (nine vanilla + the three AYS presets), one for the Impact list (the same nine + AYS + GITS[coeff=1.2], OSS FLUX, OSS Wan, simple_test), and two outputs, efficient and impact. Set both, feed both samplers, done.

How it works

Pure pass-through - two combos in, two combos out, no logic in between. The efficient output echoes scheduler_efficient (12 choices), the impact output echoes scheduler_impact (16 choices). It's the same idea as the ComfyUI+Efficient and ComfyUI+Impact selectors in the same pack, but scoped to the two third-party lists, which makes sense when your base pass runs on an Efficient KSampler and your detailer sub-pass runs on an Impact sampler.

When you'd actually use this

Honestly? This is the niche of a niche. It earns its keep only in a workflow that mixes Efficient's KSampler for the main pass with Impact's sampler for refinement - and you want both to share a scheduler without double-checking two dropdowns. If your graph is vanilla-only or single-pack, you don't need it; the plain Scheduler Switch or vanilla widgets cover you.

Deprecated

The DEPRECATED category and the pack's README both say it: unmaintained, superseded by ComfyUI_Eclipse. It works fine as frozen plumbing, but don't expect updates and don't build a new workflow around it when a single Scheduler Switch [RvTools] will do the same job with any list.

Installing it

ComfyUI Manager → search ComfyUI-RvTools_v2, install, restart; or git clone https://github.com/r-vage/ComfyUI-RvTools_v2 into ComfyUI/custom_nodes. Neither Efficient Nodes nor Impact Pack is installed by this - add those separately if you don't have them. No model downloads.

Gotchas

The usual v2 rename trap applies: legacy ComfyUI-RvTools v1 workflows won't match these class names, so Manager flags them missing. And remember both dropdowns are independent - the node doesn't force them equal, it just puts the choice in one place. Forcing the same scheduler in both is on you, which is fine: that's also how you deliberately run different schedules on the two passes.