Feature Library

Lightspeed and shockwave

5.56 GPU · 0.14 CPU ms
A still of the Lightspeed and shockwave demo
Still
The live demo starts when it’s in view.Click or press Enter to replay · arrow keys to scrub

A title moment for a stage or a launch: the camera races in at lightspeed behind falling lights, the stars streaking past, brakes hard into their trails and…

What it costs a frame

5.56 ms
0.14 ms
GPU
5.56 ms
CPU, median
0.14 ms
CPU, 95th pct
0.24 ms
Draw calls
0
Weight
Heavy

Measured 11 November 2026 on 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 157, 1920×1080 at 1×. 600 frames × 3 rounds, median kept. What ran: The whole 16 s sequence played over and over at medium quality (12k stars, 2 × 2,600 trail particles, 2 × 700 sparks): one full-screen ray-traced pass (world, barrier cells, shockwaves, word), the stars as streaks and the particles additive, one composite pass; timed with its own timestamp queries. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
unknown GPU · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring tool5.560.140.24
apple · Apple A19 Proin a browser tab · 16 November 20266.520.280.40
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 20261.770.320.51

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
WebGPUNeeds WebGPU: current Chrome and Edge, Safari 26+, Firefox 141+ on Windows.
Your browser
Checking…Looking for WebGPU
Depends on
NothingNo other packages

What it’s for

  1. Opening a talk, a keynote or a live stream
  2. Intro and title sequences
  3. Splash and launch screens
  4. Arrivals, jumps and impacts in games
  5. Loading moments that end on a word

Pitfalls, in brief

  1. The stars streak only if you pass the moment a shutter ago: draw(now, before), or drawAt(t), which works it out.
  2. Draw at the canvas’s own width and height: size it (CSS size × devicePixelRatio, 1.5 is plenty) before drawing, or it draws at 300 × 150.
  3. Await document.fonts.ready before creating it (or call setWord again once the font loads): the word is drawn once with canvas 2D, in whatever font is ready.
  4. Past the end the last moment holds alive only while you keep drawing with a running clock; at 30 fps it looks the same and costs half.
  5. draw() skips while the last frame is still on the GPU (never more than one queued): call it every animation frame while something moves, not once per change.
2 more in brief
  1. arrivalAt(t) is the built-in sequence in seconds: scale t yourself for an effect speed.
  2. Without WebGPU createArrivalShockwave returns null: draw drawArrivalStill on a 2D canvas instead (the last moment, the same places).
7 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From SpaciousPro. Fully custom code.

Mark Jarzynski & Marc Olano, Hash Functions for GPU Rendering (2020): Their pcg3d and pcg4d hashes (from Melissa O’Neill’s PCG family) replace the source’s sine and float hashes under every noise, cell and particle.

Steven Worley, A Cellular Texture Basis Function (1996): The barrier’s cells are the distance between the nearest two feature points (F2 − F1).

Robert Penner, easing equations: The built-in sequence eases with the cubic in, out and in-out curves of his set.

lightspeedwarpshockwaveforce fieldmotion blurstreaksray tracingvoronoiwgslraw webgputitle sequencedeterministic

Near it in the frame