Vidu Prompt Adherence Failure — Pre-Generation Risk Reference
Technical Classification
Prompt-to-Generation Adherence Failure
Prompt-to-Generation Adherence Failure on Vidu occurs when the output substantially diverges from the prompt specification. The subject is wrong, the action described isn't performed, key elements are missing, or the setting is different. Vidu is generally strong on prompt adherence but failure rates climb on multi-clause prompts (>3 explicit specifications) and on prompts requiring counterintuitive scene composition.
How to identify this failure
- ✕Vidu output uses a different subject than the prompt specified
- ✕Requested action not performed (e.g., "running" → subject is walking)
- ✕Specified elements missing from the scene (e.g., "with a red umbrella" — no umbrella appears)
- ✕Setting/location ignored — beach prompt produces indoor scene
- ✕Color, time-of-day, or weather specifications ignored
Real generation examples
Prompt used
"A black labrador puppy chasing a yellow tennis ball on green grass, sunny day"
Failure observed
Output showed a golden retriever (not black lab) on snow (not grass), no ball visible
Prompt used
"Two people shaking hands at a business meeting, conference room, daylight"
Failure observed
Output showed a single person waving, no second character, outdoor setting
Documentation strength
If you need to escalate
HIGH — Vidu support has approved refunds for prompts where the divergence is documented with side-by-side comparison.
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 Prompt-to-Generation Adherence 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 Prompt-to-Generation Adherence 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 "Prompt-to-Generation Adherence 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
How adherent is Vidu compared to other models?
On simple 1-2 clause prompts, Vidu is competitive with Sora and Veo. On multi-clause prompts (4+ specifications), adherence drops significantly — comparable to early Runway Gen-3.
How do I document prompt adherence failure?
Send the exact prompt, the output, and a per-clause breakdown of what was honored vs ignored. AVA generates this checklist automatically.
Are negative prompts honored on Vidu?
Inconsistently. "Without text", "no people", "no animals" — these are followed maybe 60% of the time. Best practice: avoid relying on negative prompts for refund-critical generations.
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.
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.
Related failures across models
If you’re seeing this failure, you may also encounter these on other models:
Semantic
Sora output ignores or contradicts explicit prompt instructions — wron…
Text
Runway output ignores the prompt entirely, producing generic motion un…
Camera-Conditioning
Veo output uses a static camera or generic camera motion instead of th…
Text
Luma output partially or completely ignores the prompt — wrong subject…
Cross-Attention
ByteDance Seedance produces output that ignores significant parts of t…
Anatomical
Extra limbs, fused joints, interpenetrating geometry, impossible artic…
Pick a different tool for Vidu failures
Some prompt shapes will keep failing on Vidu. Routing those shots to a different vendor is the cheapest fix.
Alternatives
Vidu alternatives
Ranked substitutes by shot type — character, motion, lighting, audio, brand product.
Head-to-head
Vidu vs Luma
Vidu 2.0 (ShengShu) · Luma Dream Machine Ray-2
Head-to-head
Vidu vs Runway
Vidu 2.0 (ShengShu) · Runway Gen-4
Head-to-head
Vidu vs Veo
Vidu 2.0 (ShengShu) · Google Veo 3