Diagnose and repair a complex shot | Academy

The opening take asks one camera move to carry a war cry, an army emergence, a hero reveal, and a final wide composition. Watch the first four results as evidence, not as four verdicts. A failure that repeats points to the brief or its references. A one-off defect after the movement works points to another roll.

Exact source brief

Scene 66, sequence 1 — the opening shot. One continuous FPV drone take, 15 seconds, no cuts. @monster's war cry at the tree, pull straight back as the @samurais army bursts out of the snow, pass @roko on the way, and end deep in the field with the whole army revealed. Both characters keep their feet planted.

This is one of five short source requests shown going into Claude or the source skill. It is not the expanded Cinema Studio generation prompt. Because the linked resource does not expose that expanded text while signed out, this course preserves the readable request and does not reconstruct what is missing.

Separate the locks from the variables

The recorded request and the surrounding source breakdown expose three stable layers. Named character references establish who is present. The environment holds snow, fog, ground, and lighting. The camera instruction sends an FPV drone straight backward rather than asking for a merely “dynamic” shot.

Those locks make the batch readable. If identity, weather, and direction remain stable, do not rewrite them when something else fails.

First generated batch result with repetitive warrior silhouettes surrounding Roko

The emergence looks like a motion artifact, the army repeats the same silhouette, and the level pullback reduces the figures to dots in fog. These are structural failures: they recur in what the shot asks the model to stage.

Make the smallest justified correction

The source makes three different repairs, each tied to a visible cause. Only after the generic army repeats as cloned silhouettes does the source create separate heavy and light warrior references.

Observed failure	Diagnosis	Controlled change
Warriors emerge as a broken motion smear	The action lacks a convincing visual progression	Clarify the emergence instead of replacing the whole scene
The army reads as identical clones	A generic crowd has no silhouette classes	Add heavy brute and light scout references
The pullback stays flat and loses the subjects	The path holds one height and one framing idea	Begin on the monster and finish in a raised heroic wide

The next result fixes the rise and gives the army texture, but the monster's right arm is wrong. The reference says the bone grows from the elbow into a blade; the generation still invents a hand holding a sword. Repeating bans about hands and handles does not solve the source attempt. The useful correction is positive and visible: raise the arm so its construction is exposed to the camera.

That final change lands, and the take enters the film.

Do not reward a bad result with a total rewrite. First mark what already works. Then ask whether the defect repeats across the batch, names a missing reference, or appears only in one roll.

You understand the iteration when you can point to one failure, name its level—asset, action, camera, or roll—and change only that level.