Things that should not run in a browser

Every one of these is deployed and running, not recorded. None of them solve a problem. That is the point of them: the goal is that something looks impossible, and the only hard constraint is a frame budget of about sixteen milliseconds.

GPGPU flow fieldOpen ↗

Particle positions computed on the GPU and fed back as texture data. The CPU never sees a particle.

Morphing particlesOpen ↗

One particle system interpolating between several models at once.

Cursor particlesOpen ↗

The pointer displaces the field and it settles back behind you.

Raging seaOpen ↗

Waves displaced in the vertex shader, lit as one surface.

OceanOpen ↗

A calmer sea. Most of the work is in the foam threshold.

Animated galaxyOpen ↗

Spiral arms rotating at different rates by radius, all in one draw call.

Galaxy generatorOpen ↗

Every parameter exposed. Worth breaking on purpose.

Portal sceneOpen ↗

Baked lighting and a shader portal. Runs on almost nothing.

HologramOpen ↗

Scanlines, fresnel and glitch, all in the fragment shader.

EarthOpen ↗

Day, night, clouds and atmosphere layered into one material.

HurricaneOpen ↗

A rotating volumetric mass. The spelling is a typo I kept.

Haunted houseOpen ↗

Fog, shadow-casting lights, and far too many draw calls.

DonutsOpen ↗

The first one. Everyone's first one.

Z-BallOpen ↗

A small game with physics. Playable, which is the point.

These came out of working through Bruno Simon's Three.js Journey end to end, and then not stopping when it finished.