MAJORFailure Reference

Vidu Motion Failure — Pre-Generation Risk Reference

Technical Classification

Temporal Motion Coherence Failure

Temporal Motion Coherence Failure on Vidu occurs when the model fails to produce continuous motion across the clip's timeline. Subjects freeze mid-action for 1-2 seconds, frames near-duplicate, or motion stutters in non-uniform timing. Most severe on long clips with sustained motion (running, dancing, vehicle motion).

How to identify this failure

✕Subject freezes mid-stride for 1-2 seconds in Vidu output
✕Frame-to-frame duplication detectable on slow playback
✕Motion stutters in non-uniform timing
✕Vehicle/animal motion stops despite continuous-action prompt
✕Dance/sports motion loses fluidity at clip midpoint

Real generation examples

Prompt used

"Runner sprinting through a park, slow motion, late afternoon light"

Failure observed @ 2.1s

Runner froze mid-stride at 2.1s for 1.3s; motion resumed at 3.4s but with visible frame jump

Prompt used

"Sedan driving down an empty highway, side-tracking shot, sunset"

Failure observed @ 3.8s

Sedan motion stalled at 3.8s; remained stationary for remainder of 6s clip while environment continued moving

Documentation strength

If you need to escalate

HIGH — Vidu motion stalls are recognized refund cases with timestamp evidence.

AVA is a pre-purchase prevention tool, not a post-purchase recovery tool. Platforms generally do not guarantee credit refunds for output-quality failures; goodwill credits are at each platform's discretion. The strength rating reflects how well-formed your support ticket can be, not a promised outcome.

Prevention + documentation steps

01
Score your prompt before you generate
Run your prompt through AVA's pre-flight scoring against the Temporal Motion Coherence Failure pattern. Green light = generate. Yellow/red = rewrite using the suggested fix before you commit credits.
02
Capture Generation ID + timestamp if it failed anyway
Find the Generation ID in the URL or share link. Note the exact time when the Temporal Motion Coherence Failure first appears (e.g. "failure first visible at 1.2s"). Timestamped evidence is significantly stronger than a general complaint.
03
Use the correct technical term in your support ticket
Describe this failure as "Temporal Motion Coherence Failure". This term maps to a recognised internal workflow in the support system and routes the ticket to the right team.
04
Submit via the correct support channel
Runway has no direct email intake. Pro+ plan: open the in-app AI Assistant (help widget bottom-right of app.runwayml.com), describe the failure with the technical term, attach evidence. Free/Standard plan: human support isn't available — your channel is Discord #community-help with @On Call - Moderators.

Frequently asked questions

Why does Vidu motion stall on long clips?

Temporal attention degrades past the model's effective horizon (typically 4-5s). The diffusion sampler can produce near-duplicate frames when motion vector prediction collapses.

How do I document a motion failure?

Provide the Generation ID, timestamps of the stall, and a frame-by-frame breakdown. AVA generates this motion-vector analysis automatically.

Should I use shorter clips on Vidu to avoid this?

For motion-heavy prompts (sports, vehicles, dance), keep clips ≤4s. AVA L1 scanner flags long-clip motion risk before generation.

Score your prompt

Score your prompt against this failure mode in 30 seconds

Paste your prompt and the platform you intend to use. AVA returns a red/yellow/green score against this specific failure mode plus a concrete rewrite if the risk is high.

Install free All 105 failure modes

AVA Pro · founders' round

$50 for 6 months of unlimited scoring across all failure modes + personal failure-history dashboard. Locks in $13/mo grandfathered after.

Claim $50 founders