Slow Motion Physics Test: Ceramic Vase Shatter

Failure mode: mid-action cut at second 2.5

The video above is the unedited Omni Flash output from this prompt (generated 2026-05-26 on Google Flow, 6s, requested 1:1 but model returned 16:9). It’s the clearest documented example we have of one of Omni’s hardest limits — and the reason this page leads with the failure rather than hiding it.

What you’re seeing:

• 0–2s — Ming-style 青花 (blue-and-white) vase tips off the wood cabinet shelf and falls toward the marble floor. Note that Omni interpreted “ceramic vase” through Chinese aesthetic context — a happy semantic accident.
• 2–2.5s — Vase touches the marble and does not shatter. It lands intact and lies on its side.
• ~2.5s — The model inserts an editorial cut. The next frame shows the vase upright again with a different camera angle. There is no continuous trajectory from the lying-on-side state to the upright state.
• 3–4.5s — Vase falls a second time.
• 5–6s — Shatter executes correctly. Fragment dynamics here are excellent: larger pieces tumble further than smaller ones (the prompt’s literal request), dust particles scatter realistically, ceramic shard outlines respect the original pattern.

Why this happens (our reading): Omni Flash cannot reliably sustain a single “fall + impact + shatter” chain across 6 continuous seconds when the impact physics are uncertain. Rather than render an implausible bounce or a soft landing, it inserts a scene cut to reset state and retries the destructive moment. The shatter when it executes is photoreal — the bug is in the continuity, not the physics.

Practical workaround for your generations:

• Prefer 4s slow-mo prompts that start at the impact moment, not before the fall.
• Or use frames mode (“帧” tab in Flow) with a key start frame already in the fall position to constrain the trajectory.
• Avoid asking for both a fall and a shatter in one 6s clip when the surface is hard (marble, concrete). Try sand, water, or fabric instead — Omni shatters cleanly when it has more deformation budget to allocate.

Why this prompt

Adapted directly from Medium’s Gemini Omni Prompt Playbook, which lists this as one of 10 verified-working examples. The playbook author tested it on Omni Flash and reported the output successfully rendered the fragment weight distribution and realistic angular momentum.

This prompt is a physics stress test — it showcases Gemini Omni’s strongest claim (per Google’s announcement):

“It combines an intuitive understanding of physics with Gemini’s knowledge of history, science and cultural context.”

Source tier: 🟡 Community playbook (medium confidence — author tested, output not public)

The physics trigger words

Per the Medium Playbook, these specific phrases activate Omni’s physics handling:

• “realistic momentum”
• “fragment weight distribution”
• “right angular momentum”
• “larger pieces tumbling further than smaller pieces”

Generic phrases like “looks real” or “physically accurate” are too vague — Omni responds better to explicit physical relationships.

Other physics-friendly subjects to try

The playbook documents these patterns working:

• Liquid: pouring, splashing, dripping (slow-mo coffee, wine, milk)
• Solid impact: shatter, crumble, compress (vase, bread crust, glass dome)
• Cloth/fabric: sweep, fold, billow (curtains, dress, flag)
• Particles: dust, smoke, embers (campfire, demolition, magic effect)

Avoid:

• Multi-body collisions (3+ objects interacting — Omni drifts)
• Long timescales (slow-mo + extended duration > 8s loses focus)

How to tweak

• Object: vase → crystal goblet / clay pot / glass dome / lightbulb
• Surface: marble → concrete / wood / sand (changes shatter behavior)
• Camera: locked 1:1 → 9:16 portrait / 16:9 wide
• Trigger moment: shatter on impact → mid-flight collision / vacuum pop / freeze-fracture

Alternative: slow-motion food (the popular but generic version)

Ultra-slow-motion video, 1000fps look. A barista's hand pours a steady stream of dark
espresso from a tilted portafilter into a small white ceramic cup. Rich golden crema
forms and swirls hypnotically. Tight close-up, shallow depth of field, warm morning
sunlight from the left.

— Coffee pour is the most overdone food-slowmo prompt in 2026; works but doesn’t showcase Omni’s differentiation. Use shatter for portfolio, coffee for client work.

Common failure modes

• Text rendering: any overlay text breaks at slow-mo speeds (per PixVerse review)
• Hand interactions: pouring shots involving fingers can morph badly — frame to crop hands
• Duration > 8s: slow-mo prompts past 8 seconds tend to slow further or distort time

Notes

• 6 seconds is the sweet spot for impact-moment slow-mo
• 1:1 aspect ratio works best for product / commerce Instagram use
• Specifying “1000fps look” gives Omni a frame-rate cue without needing post-processing

Sources

• Playbook source: Medium — Gemini Omni Prompt Playbook
• Google’s physics claim: Introducing Gemini Omni
• Text rendering limitations: PixVerse Gemini Omni Review