MAJORFailure Reference

Google Veo Camera Motion Ignored — Refund Guide

Technical Classification

Camera-Conditioning Embedding Failure

Camera-Conditioning Embedding Failure on Veo occurs when the camera-motion instructions in the prompt fail to influence the trajectory of the rendered virtual camera. Veo markets cinematographic camera control as a headline feature — dolly-ins, crane shots, tracking shots, push-pulls. When the model ignores these and falls back to a static or generic motion, paid output is a clear feature defect.

How to identify this failure

✕Camera stays static despite explicit dolly / pan / crane request
✕Camera motion direction is wrong (left when right was requested)
✕Camera motion magnitude is far smaller than specified
✕Camera motion happens but applied to wrong subject framing
✕Tracking shot loses the subject within 1 second

Real generation examples

Prompt used

"Slow dolly-in toward a chess piece on a wooden board, cinematic"

Failure observed @ 0:00 → 0:05

Camera stays completely static for the full duration; no dolly motion

Prompt used

"Tracking shot following a runner left-to-right through a forest path"

Failure observed @ 0:00 → 0:03

Camera stays static and the runner exits frame at 0:02

Documentation strength

If you need to escalate

HIGH — Camera control is a marketed Veo capability. Refund tickets citing camera-conditioning failure on a paid generation are honoured.

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 Camera-Conditioning Embedding 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 Camera-Conditioning Embedding 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 "Camera-Conditioning Embedding 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

Does Google refund Veo camera motion failures?

Yes — Veo support recognises camera-conditioning failures on paid output as a defect. Cite "Camera-Conditioning Embedding Failure" with the prompt and a still showing static framing.

Why does Veo ignore camera motion sometimes?

Veo encodes camera instructions through a dedicated conditioning channel separate from the subject prompt. Under specific subject + motion combinations (especially close-up macro shots and abstract subjects), the camera channel can be down-weighted, producing static output.

How do I phrase camera motion to maximise Veo compliance?

State the camera motion FIRST, before subject. Use canonical cinematography vocabulary (dolly-in, dolly-out, crane up, push, pull, orbit). Avoid metaphorical motion verbs ("the camera dances"). AVA pre-flights camera-motion prompts.

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