Show a tooltip, then blur and fade the whole HUD as the 3D camera starts flying
Study the source, inspect the editable build, then adapt the treatment to your own content.
What the source does
A low-poly aerial city scene fills the frame with a view-mode toolbar and an era timeline along the bottom and a small picture-in-picture inset top right (master 200-210). At master 206 (local 6) a dark tooltip pops in under the timeline. At local 11-14 the toolbar and timeline blur and fade out together while the whole scene motion-blurs; by local 14 the view has changed to a dense riverside town and by local 16 it is sharp again. The inset stays put throughout.
Chrome drop-out: UI overlays blur and fade as one unit at the instant the camera begins a fast move, so the fly-through plays clean while a persistent inset survives.
Phase notes
- Frame 0 — Idle: scene, toolbar, timeline, inset
- Frame 6 — Tooltip pops in under the timeline
- Frame 11 — HUD blurs and fades; scene motion blur begins
- Frame 14 — New view under the blur
- Frame 17 — Scene sharp, HUD gone, inset remains
Use this example
- Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
- Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
- Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
- Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.
The source and remake are different assets. The original code-based illustration remains editable; source footage is a research reference. Read the retained findings below before using the choreography.
Recorded limits
- Visual fidelity is an authored draft judgement from sampled source frames; no independent blind review or native Resolve execution.