Bring the HUD back from a blur while the 3D camera eases into its new position
Study the source, inspect the editable build, then adapt the treatment to your own content.
What the source does
The low-poly city plays with no interface for the first frames (master 524-528) while the camera drifts lower toward street level. At master 530 (local 6) the bottom toolbar shows up as a soft, semi-transparent blur; by local 8 the era timeline is also ghosting in, and both are crisp by local 12. The scene keeps moving slowly under the crisp HUD until the window ends at master 562. The reverse of the earlier drop-out: chrome returns from blur once the fly-through is over.
Chrome return: the interface resolves from a heavy blur to sharp over six frames while the camera decelerates, so UI and camera settle together.
Phase notes
- Frame 0 — Clean scene, camera still moving
- Frame 6 — Toolbar and timeline appear blurred and faint
- Frame 12 — HUD sharp and opaque
- Frame 37 — Camera nearly at rest, HUD idle
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.