Inspirations

FPV into the Fjord

Real-time FPV chase at sunrise in a Norwegian fjord: a 5-inch quad dives off the lip of a 168 m waterfall through its mist and rainbow, skims the mirror-calm fjord into the sun glitter and punches up into the low sun.

Made in Claude Code (Claude subscription) with claude-opus-5.5. The agent wrote code, looked at the preview and fixed it over several iterations. This is not a single-shot result: comparisons on this site show models in one attempt.

Starting prompt

Build "FPV into the Fjord": a real-time 3D flight that must look like real FPV footage shot on an action camera at sunrise in a Norwegian fjord. A cinematic FPV drone chases another FPV racing quad through one continuous, seamlessly looping flight. Realism is the whole point: if something cannot be made to look real, leave it out rather than show a toy. No people and no boats anywhere. Single self-contained HTML file; Three.js r170 and its addons from a CDN via an import map are fine; build everything procedurally (canvas and data textures are fine), no external models or image files.

The place (metres, y up, water at 0; the fjord runs east, towards the rising sun about 10° above the horizon):
- The inner end of a fjord: sheer granite walls 230–300 m high, about 270 m apart at the head and widening eastwards for kilometres between headlands that fade into haze, with snow-patched mountains of 900–1,300 m behind.
- In the head wall a river leaves a hanging valley 168 m up and plunges in one free fall into the fjord: a curtain of white water about 20 m wide at the lip, clear and green at the edge, breaking into streaky curtains and fine, translucent drifting spray that fall at the real, accelerating speed, wet black rock and an alcove behind it, a churning foam pool and a billowing mist cloud at the base. The spray carries a rainbow placed physically, 42° around the antisolar point (with the fainter secondary bow), so it shows only where sunlit spray is.
- A rocky island with pines in the bay, and behind it, in the narrow channel under the north wall, two rock pillars about 63 and 72 m tall, pines on top, with a gap of about 17 m between them.
- Terrain that holds up close: banded, jointed granite with straight cracks, water streaks and lichen, dark wet rock around the falls, a black tidal band at the waterline, moss, grass and heather on ledges, glacier-polished slabs, boulders and a meandering river in the hanging valley; birch, Scots pine and Norway spruce on the slopes and ledges, built as real trees (trunks, branching limbs, drooping spruce tiers, needle and leaf clusters), never cones or blobs; snow patches on the high ridges.
- Deep green-blue water with true mirror reflections broken by ripples and calm patches, sun glitter towards the sun, foam around the falls and a ruffled propwash trail under the quad when it skims low.
- Thin morning mist on the far walls, aerial haze that layers the ridges, the low sun with a lens flare.

The quads: 5-inch freestyle quads, about 22 cm motor to motor: a carbon-fibre X frame with visible weave, aluminium standoffs, four brushless motors with motion-blurred tri-blade prop discs, a battery strapped on top, an action camera, antennas and a tiny glowing LED, with a faint propwash shimmer under the props. No logos or brand names.

Real FPV flight physics for both quads (the lead flies the line, the camera follows 2–3 m behind on the same line and reacts a fraction later, so the lead is large in frame):
- Thrust points along the body's up axis and equals path acceleration minus gravity plus quadratic drag, so the quads pitch forward to fly fast (about 35° at 30 m/s), bank into turns and punch out with throttle; with little thrust in a dive the pilot points the camera at the lead. The camera sits on the frame tilted up 30°, so the horizon pitches and rolls with every move. Speeds up to about 38 m/s in the dive, a slight propwash shake.
- Short-shutter camera motion blur, a wide action-camera lens with slight barrel distortion, chromatic fringing at the edges and a light vignette.

The flight, one loop of 17 seconds:
1. 0 s: at the lip of the falls, looking out over the fjord towards the low sun.
2. 0–6 s: both quads pitch over and dive straight down beside the falls, the camera looking down past vertical at the water streaming into the mist and the rainbow in the spray.
3. About 7 s: pull out a couple of metres above the water through the mist. At 8 s, the strongest frame: skimming the fjord at full speed into the sun glitter, the lead large in frame with its reflection under it.
4. 8–15 s: keep skimming straight down the fjord into the sun; after the dive the camera never comes within about 40 m of bare rock.
5. About 15–16.5 s: the quad punches up steeply into the low sun, the sun floods the lens and the frame washes out to white for about half a second (a classic FPV edit), and the loop restarts at the lip out of that white frame.

Interface: the canvas fills the frame and the first frame is already the shot (no loader, title card or fade). Only a small, elegant OSD-style caption in one corner: the title, altitude above the water and speed. Everything moves on its own from the first frame and loops forever, driven by wall-clock time; it works on a phone.

Rendering: physically based lighting from a low warm sun with cool sky fill, terrain self-shadowing plus cast shadows from ledges, trees and the sea stacks, ACES filmic tone mapping and correct sRGB output, subtle bloom only on the sun, glitter and spray. Dramatic but readable, never muddy or washed out. Keep it near 60 fps on a laptop: instance the trees with levels of detail, merge static geometry, cap the pixel ratio and lower it under load.

Engineering rules (the page must work on the first load, with no fixes):
- Use Three.js r170 and only methods that exist on each of its classes. Give every custom ShaderMaterial `fog: false`, and declare every uniform, constant and varying its shaders use.
- Declare each identifier once. Inside one calculation, never reuse a shared scratch vector for two values that are both still needed; use local vectors.
- Guard every animated value against NaN.
- Answer with the complete file exactly once, in a single ```html code block: no drafts, partial snippets or notes.

Keep planning brief and write the code. Aim for roughly 1,200 to 1,700 lines, compact and well structured.