Timesteps Conditioning 🎭🅐🅓

Displayed as Timesteps Conditioning, this node's entire job is small: take a start and end percentage of the sampling process and package them as a single reusable TIMESTEPS_RANGE object.

Why a node this small exists

"What portion of sampling should this be active for" is a pattern that recurs constantly throughout this pack - Apply nodes schedule when a motion model kicks in with start_percent/end_percent, CFG Extras and keyframe nodes use the same two numbers, and ControlNet-style conditioning elsewhere in ComfyUI does too. Most of those nodes just declare their own pair of percent widgets inline. This node factors that same pattern out into its own standalone, typed object instead - useful anywhere a graph wants to define a timing window once and reuse it, rather than re-entering the same two numbers on every node that needs to respect it.

Being straightforward about a real gap here: unlike most of this pack's utility nodes, our sources - the README, the schema, and this knowledge base - don't pin down exactly which downstream node or nodes actually accept a TIMESTEPS_RANGE input specifically, as distinct from the majority of nodes in this pack that just have their own built-in start_percent/end_percent widgets and never touch this type at all. The category placement (conditioning) points toward scoping some conditioning-side effect to a window, but confirm what accepts TIMESTEPS_RANGE in your own installed version before building a workflow around an assumed consumer.

Inputs and output

Both required:

• start_percent (default 0, range 0–1, step 0.001) - where the window begins.
• end_percent (default 1, range 0–1, step 0.001) - where it ends. Defaults span the entire sampling process.

Output is a single TIMESTEPS_RANGE - wire it into whichever node in your graph is typed to accept it.

How to install it

ComfyUI Manager: search AnimateDiff Evolved, confirm the author is Kosinkadink, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Kosinkadink/ComfyUI-AnimateDiff-Evolved

No model download for this node - it's a pure scheduling utility, unrelated to motion modules or checkpoints.

Common issues & troubleshooting

Not sure what this actually plugs into. See the gap noted above - check your node browser or graph for inputs specifically typed TIMESTEPS_RANGE rather than assuming a particular consumer. Most start/end-percent scheduling in this pack is handled by widgets built directly into the node that needs it, so a standalone TIMESTEPS_RANGE input is the exception, not the rule.

Confusing this with a Multival or a LoRA Hook Keyframe. Those control strength - how much of an effect applies, possibly ramping or masked. This node controls only an on/off window - when something is active at all - with no strength value involved.

Left at default and nothing seems windowed. Defaults (0 to 1) span the entire sampling process, which is functionally "always active" - narrow the range if you actually want the window to exclude part of the timeline.

KB gap worth flagging directly: this is the one node in this batch where we genuinely don't have a documented downstream consumer to point to. Worth a dedicated look - reading the pack's own node-usage docs directly, not just the top-level README - the next time this node comes up.