Sign In

WAN 2.2 I2V Faster Motions 6-step Lightx2v Workflow

102

1.9k

48

Updated: Aug 21, 2025

tool

Type

Workflows

Stats

1,870

0

Reviews

Published

Aug 13, 2025

Base Model

Wan Video 2.2 I2V-A14B

Hash

AutoV2
CF49363321

Credit to 3DBicioo for the 3-stage idea!

NOTE: I am taking a break from Civitai and I will not respond to any messages.

This workflow mitigates the current slow-motion issue with Lightx2v. Once that is fixed, this workflow is not necessary!

Lightx2v reduces WAN 2.2 generation time but makes the motions sluggish. This 3 stage workflow generates faster motions, and runs under 5 minutes on my 3090.

3 stages:

1) CFG 3.5, high model, 2 steps, euler beta

2) CFG 1, high model + Seko v1 high lora, 2 steps, euler beta

3) CFG 1, low model + seko v1 low lora, 2 steps, euler beta

I learned about the 3 stage approach from the lightx2v community posts:

https://huggingface.co/lightx2v/Wan2.2-Lightning/discussions/26

I hope by sharing this approach, more people can be excited about WAN2.2 right now, and we can have more WAN2.2 loras!

Description

This workflow supports:

  • Upscaling, 60fps interpolation

  • GGUF model

  • Lightx2v Lora

  • SageAttention

You can install SageAttention using this:
https://www.reddit.com/r/StableDiffusion/comments/1mdcjyw/finally_an_easy_installation_of_sage_attention_on/

Please upgrade to the latest ComfyUI. I used the following versions:

  • ComfyUI 0.3.49

  • ComfyUI_frontend v1.24.4

Download the models and place in the correct directory.

This workflow uses a 3 stage approach. The first stage uses the original WAN2.2 model, without Lightx2v lora. This allows for faster motions to be generated. The 2nd and 3rd stage uses the High and Low Lightx2v loras like normal.

Known issues

This approach still produces some artifacts such as flashing lights and "overbaked" colors sometimes. If this happens, try to increase to 12 steps and try again.

The interpolation model RIFE49 produces some motion artifacts (wavering background) especially with fast moving arms. I don't have a good workaround for this problem.

There are VRAM issues for some people, you can try deleting the ‘Patch Model Patcher Order’ Nodes.