Dunes
GPU displacement paired with CPU contact height, analytic slope, and skiff attitude.
Integrated field application
Breach Run
Recover a stranded survey core and carry it across a flooded dune basin to the authored landing pad. The terrain, swell, wind, and moving breach body are not backdrop: CPU game rules query the canonical fields while the GPU consumes a named, assayed materialization.
Awaiting expedition start
Current directive
Recover the field core
— m
Window
01:30.0
Core integrity100%
Rendererinitializing
GPU materializerinitializing
CPU queries / tick0
GPU readbacks / frame0
Proxy drift0.000
Authority modeunified
Authority trial / flooded basin
One run.
Four field consequences.
The core is 30 metres east of your skiff. Recover it, then reach the landing pad before the window closes. Wind pushes the hull. Swell changes buoyancy. Dunes determine contact and slope. The breach body has a real CPU-queryable volume.
- Drive WASD / arrows, or tap a waypoint.
- Camera right-drag or two-finger orbit; wheel or pinch zoom.
- Survive avoid the moving breach body and deliver the core intact.
C recenters the chase camera · R retries · P pauses · F fullscreen. Changing lanes reloads the same mission; fault injection is a teaching mode, not a competitor benchmark.
Event recordNo events recorded
The recorder distinguishes authored-field arithmetic from mesh interpolation and simulation behavior. “Zero readbacks” means gameplay never waits for a GPU result; it does not claim that rasterized triangles are identical to the continuous CPU field.
Application map
The abstraction has to survive contact with a game.
This is not a benchmark dressed as a game. It is a compact application pressure test: sparse authoritative queries on the CPU, dense visual materialization on the GPU, no per-frame readback, and an explicit fallback path.
Swell
GPU water displacement; CPU four-probe buoyancy at the same game clock.
Wind
GPU flow tracers; CPU force continuously changes the route and handling.
Breach
GPU body animation; CPU proximity and collision against the authored spine and radius.
What the renderer path proves
The default WebGPU lane and the WebGL2 fallback materialize the authoritative adapter-authored tree through native TSL. The optional TypeGPU lane consumes the precompiled matter-field/typegpu/three integration: a separately maintained port checked against the canonical fields, not generated from their source. CPU gameplay remains the number/dual authority in every lane. Device receipts measure finite samples and declared absolute budgets; they are evidence, not a universal floating-point proof.