Range Split Override (Legacy)

The node itself is blunt about its status: its own description calls it a "legacy percentage-based split override" and tells you new workflows should use Step Split Override instead. That's refreshingly honest, so let me be honest back - you probably don't want this one unless you're maintaining an older graph.

What it does

It's an in-chain override on a Wan 2.2 sampling plan. You feed it a plan and a high_range_percent (default 50, min 1, max 99), and it rebuilds the whole plan - including both sigma slices and the step split - so that high_range_percent of the denoising range goes to the high-noise expert. The name says "range," and that's the key difference from the newer node: it expresses the split as a percentage of the sigma range, not as an exact count of sampling transitions.

Everything is recomputed and validated on the way out, so you're not just nudging a number - the curve, the split sigma, and the step counts all get rebuilt from your forced value. The plan output is type-identical to what went in, so you can drop this node anywhere in the plan chain.

Why it's legacy

The percentage framing is fuzzy by design. A range percentage doesn't map cleanly to "how many transitions the high-noise expert actually runs" - that depends on your scheduler's curve, and a 50% range is not necessarily half the steps. Step Split Override (the replacement) takes the exact number of high-noise transitions instead, which is what people actually mean when they say "I want the high stage to do N steps." It's a strictly more precise knob.

There's also a subtle interaction the planner tracks: if an exact high-step override is active elsewhere in the chain, the legacy percentage is silently ignored (the plan emits a warning about it). So mixing both in one workflow gets you the exact override winning and the percentage doing nothing but confusing you.

When you'd actually use it

Honestly? Only if you have an old Sampling Planner workflow built around the percentage and you don't want to re-tune the numbers. The semantics are close enough that switching to Step Split Override means picking one integer - the high transition count - instead of reasoning about range percentages. If you're starting fresh, skip this node entirely and grab Step Split Override.

Install

Same as the rest of the pack - ComfyUI Manager (search Sampling Planner) or:

cd ComfyUI/custom_nodes
git clone https://github.com/boobkake22/ComfyUI-SamplingPlanner

restart, and it's under sampling / Sampling Planner / Wan 2.2. No dependencies.

The takeaway: this node isn't broken, it's just superseded. Read it as documentation of how the pack used to work, use Step Split Override for anything new, and only reach for the legacy node when you're staring at an old graph that already has it in-chain and you don't want to re-derive the numbers.