wan2.2 FW Motion Enhancer

Show More

v3.0

I decided to drop the idea of a “merge” and instead just forced 10KE10.safetensors (wan2.1 LoRA) to fit into wan2.2’s structure. Here’s the rule I used:

• If a key exists in both → keep wan2.1’s version

• If a key only exists in wan2.1 → discard it

• If a key only exists in wan2.2 → keep it

So basically, it’s not really a merge, more like making wan2.1 conform to wan2.2.