Feature Library

World-space procedural surfaces

0.39 GPU · 0.28 CPU ms
A still of the World-space procedural surfaces demo
Still
The live demo starts when it’s in view.Click a yard part or select it · choose a finish · edit Surface parameters · compare Shimmer guard while zooming

Twenty-four ground, wall and roof finishes evaluated directly from world coordinates: brick, timber, corrugated metal, concrete, grass, gravel, snow, lava and more.

Pixel footprints soften joints toward their average coverage and fade fine relief before it aliases. A plain-data catalogue supplies colours, dimensions, hints and recommended values; live edits update uniforms without a bake or shader rebuild.

What it costs a frame

0.39 ms
0.28 ms
GPU
0.39 ms
CPU, median
0.28 ms
CPU, 95th pct
0.39 ms
Draw calls
37
Weight
Light

Measured 19 November 2026 on RTX 4060 Laptop, 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 157, 1920×1080 at 1×. 600 frames × 3 rounds, median kept (rounds ranged GPU 0.39–0.41, CPU 0.28–0.28 ms). What ran: Default whole yard: brick house, corrugated roof, timber shed, grass, gravel, concrete slabs and dirt, with a fitted sun shadow and hemisphere sky light. Shimmer guard on, no zoom or parameter edits. No textures, compute or bake; idle frames are held outside benchmarks. Other catalogue finishes have different fragment costs. Phones: tiers are being measured next.

How steadily it runs on RTX 4060 Laptop · 13th Gen Intel(R) Core(TM) i9-13900H · reference

Typical frame ?
3.15 ms
1% low ?
154 fps
Varies by ?
±0.87 ms
All metricsRTX 4060 Laptop · 13th Gen Intel(R) Core(TM) i9-13900H · reference
p50p95p990.14 ms6.52 ms +
How long each frame took. Most frames sit in the tall bars; a long tail to the right is hitching.

Frames run back to back, each starting once the GPU has finished the last, so frame times show the work itself. They have a floor of about 4–5 ms from the browser’s own scheduling: GPU and CPU ms stay the measure of cost.

Frames

Median (p50) ?
3.15 ms
p95 ?
5.37 ms
p99 ?
6.18 ms
Slowest ?
6.96 ms
Mean ?
3.65 ms
Standard deviation ?
0.87 ms
1% low ?
154 fps
0.1% low ?
144 fps
Hitches ?
4 of 600
Over budget ?
0 of 600

Main thread

Long tasks ?
0
Long frames ?
0
Event-loop delay ?
0.0 / 0.7 / 0.7 ms

Input

No input during this run.

Memory

JavaScript heap ?
55.1 → 49.8 MB
Growth ?
-5.29 MB

Browser

JavaScript a frame ?
0.01 ms
All tasks a frame ?
0.46 ms
Layout / style ?
0.00 / 0.00 ms
Main thread busy ?
13%

Garbage collection

Collections ?
1 (1 minor, 0 major)
Pauses ?
0.8 ms in all, longest 0.8

What it needs

Renders with
WebGPU or WebGLWebGPU where there is one, WebGL2 where there is not.
Your browser
Runs hereNo WebGPU needed
Depends on
three.js 0.187.0No other packages
With an agent
install("world-surfaces")Your coding agent reads its pitfalls and installs it through the library’s MCP server. Set it up

What it’s for

  1. Walls and ground with patterns at metre scale
  2. Brick mortar and corrugation that fade smoothly with distance
  3. Live material tuning without baking textures
  4. A portable catalogue of ground and wall finishes

Pitfalls, in brief

  1. World coordinates are Y-up and measured in metres.
  2. World projection is not a seamless unwrap: curved walls change tangent and can show phase jumps.
  3. Wall grime measures height above the mesh origin.
  4. Relief changes the shading normal, not geometry, silhouette, depth, collision or shadows.
  5. Footprint filtering suppresses sub-pixel pattern and normal aliasing; it is not temporal anti-aliasing or a guarantee that every noise term is band-limited.
5 more in brief
  1. All values start from resolvedValues. set() changes only known catalogue keys, clamps finite numbers and restores defaults for invalid types or colours.
  2. Each surface is a different shader.
  3. The catalogue’s fallbackColor is a parameter key for an optional plain-material tier, not a texture and not this demo’s WebGL path.
  4. These graphs run per covered fragment, every drawn frame.
  5. Dispose every created material and your geometry.
10 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From HaTac. Adapted from published work, named below.

Hannes Andersson: Source surface graphs, catalogue, analytic relief and footprint filtering.

Morten S. Mikkelsen: Surface-gradient bump mapping from screen-space height derivatives, as described in the source.

proceduralworld spacematerialssurfacesno UVsanti-aliasingfwidthbricktimberterrainrelieftsl

Near it in the frame