3D production · Project breakdown · 6 minute read
A cinematic sequence begins with a reason for each shot. Raptor Flight moves from machinery and ground preparation to takeoff and open sky.
This companion breaks down our 68-second fictional aviation film: 60 seconds of native 3D footage followed by an eight-second branded outro. It explains the shot structure and review process rather than presenting the film as real aircraft footage.
What was made, and with which tools?
The film uses an existing Fighter Squadron OpenUSD scene with animated aircraft, an airbase, and ground-support elements. GPT 6 Astra helped plan the edit and write the capture script. NVIDIA Omniverse Kit rendered the native 3D frames. Titles, project audio, synthetic pilot calls, original synthesized music, and the final outro were assembled into the finished video.
The AI-assisted work here was shot selection, structure, and capture scripting. The aircraft model and existing project assets were not newly generated by the language model.
Build a visual story before rendering
The engine detail gives the opening a strong subject. Short ground inserts establish preparation and scale. The airframe portrait identifies the aircraft, then the power build-up makes the departure feel earned. Longer flight shots provide a release after the tighter early cuts.
| Film time | Shot | Purpose |
|---|---|---|
| 0–4s | Engine detail | Immediate visual hook |
| 4–8s | Ground crew | Human scale and preparation |
| 8–12s | Service apron | Establish the environment |
| 12–16s | Airframe portrait | Make the main subject readable |
| 16–22s | Engine power | Build anticipation |
| 22–34s | Two departures | Move from ground to sky |
| 34–42s | Paired flight | Expand the visual scale |
| 42–47s | Bank detail | Change angle and motion |
| 47–60s | Valley finale | Give the closing image room |
| 60–68s | Branded outro | Close the film |
Separate edit timing from scene timing
A shot beginning at 22 seconds in the film may come from a later moment in the scene animation. Record both the output interval and the source animation interval. This avoids rendering the right camera at the wrong moment.
Our capture plan pairs each interval with a named camera, such as an engine close-up or a following camera. That makes a render pass reproducible within the same project. It also makes it easier to replace one shot without rebuilding the whole edit.
Preview the frames that reveal problems
Before committing to a full capture, inspect the start, middle, and end of each moving shot. A camera that works in the first frame can crop an aircraft a few seconds later. Check the subject silhouette, horizon, background distractions, and whether the action remains readable on a phone.
In this film, closer aircraft views replaced overly wide framing in the flight sequence. Nonessential aircraft and combat effects were excluded from the capture session so the published film stayed focused on a fictional flight demonstration.
Finish with consistent picture and sound
The final export is 1920 × 1080 at 30 frames per second. At that rate, the 60-second native sequence contains 1,800 frames. Use the planned duration and frame count as a sanity check, then watch the export all the way through for missing frames, awkward cuts, unreadable text, or audio jumps.
Try a smaller version
Use a scene you own or have permission to use. Make a 15-second sequence with detail, context, motion, and a closing view. Keep the same scene and change only the camera plan to see how much the story changes.
Download the shot worksheet (.txt)Aircraft credit
“F22 Raptor FREE” by NLM, licensed under Creative Commons Attribution 4.0. The model was converted to OpenUSD; static pose, orientation, and scale were adjusted; it was animated and rendered in this cinematic. No endorsement by the model creator is implied.
The downloadable worksheet is a planning resource; it does not include the Fighter Squadron scene or aircraft assets.