Wan Continuity Guide

Long WAN video work lives or dies on continuity settings, and the settings are everywhere: how many latent slots to lock to the start image, how many frames of motion tail to carry, whether to overshoot the end frame, how many slots to skip. Do that by hand on every segment of a 30-chunk sequence and you'll go numb. IAMCCS_WanContinuityGuide ("Wan Continuity Guide") exists to turn that pile of fiddly knobs into one dropdown.

It's a calculator, not an executor. You give it a continuity_profile and a segment_index, and it spits out a set of ready-to-wire integers - motion_latent_count, use_prev_samples, end_overshoot_slots_out, end_lock_slots, lock_start_slots, prev_skip_last_slots, latent_refresh_pct - that you can feed straight into WanImageMotion, WanImageMotionPro, or WanLongPlanner. Think of it as the "sane defaults for this kind of segment" node.

The profiles

There are four to start from:

• demo1_stronger - the original demo defaults, but with more aggressive motion carry and end overshoot. Good for scenes that need to actually move.
• soft_transition - gentler joins between segments, fewer locked slots, so cuts feel less like hard cuts.
• identity_first - biases toward holding the subject's identity on the first chunk, before the loop gets going.
• demo1_default - the baseline everyone compares against.

You can also ignore the profile and set every field by hand; the widgets are all right there. The profile just fills them.

The inputs beyond the profile are the raw numbers the guide combines: first_motion_count and continuation_motion_count (how many tail slots count as motion on the first segment vs. later ones), end_overshoot_slots (how far past the visible end to render so the end frame converges instead of freezing), and separate start/end lock-slot counts for the first segment and the continuations. Different budgets for the opening shot versus every shot after it - which is exactly how these pipelines actually behave.

How it fits

Wire segment_index from your loop counter, and the guide stays in sync as the loop advances. Feed its outputs into the matching inputs on a motion node and you get consistent continuity without copying widget values across twenty nodes. That's the whole pitch: one node computes, the others consume.

Install and the usual caveats

Same pack, same install:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

or search "IAMCCS" in ComfyUI Manager, then restart. No model files, no new dependencies - it's pure arithmetic over INTs. The pack floor applies: ComfyUI ≥ 0.3.0, Python ≥ 3.12, Torch ≥ 2.8.

One honest note: for a single short clip this node is overkill. It earns its place in loops and in shotboard pipelines where you want the same continuity recipe applied everywhere. And because it only emits numbers, a wrong output is easy to debug - check the report string, which tells you exactly what each output resolved to for the current segment.