NIMOS / ENGINES / 3DSPTL
← THE BUILD SYSTEM3DSPTL
THE 3D ENGINE
3D, WebGL, WebGPU & Spatial Engineering
The spatial layer, held in reserve for builds that actually earn a 3D moment.
DRAWN BY THE HOUSE
One mark per engine, on one grid, in one hand.
18
TOOLS
PROJECT
WIRE
PARTIAL
THIS BUILD
Dependencies present (@react-three/fiber, drei, postprocessing, three); no 3D scene ships on this site.
THE PROOF LEDGER →WHAT
What it is
Eighteen tools for 3D and spatial work: three, React Three Fiber, drei, postprocessing, cannon, flex, custom shader material, WebGPU types, three-mesh-bvh, glTF Transform, Spline, Rapier, XR, PixiJS, sharp, dat.GUI, stats.js and maath.
WHY
Why it exists
A 3D hero can set the bar for a product; it can also add a download, a GPU dependency and a blank screen. The engine exists to make the first possible and the second visible before it ships.
HOW
How it runs
npm into projects; GLB processing through glTF Transform; the still-frame rule comes first — a pixel-matched poster exists before any motion. The engine is also allowed to argue that a build does not need 3D at all.
WHEN
When it runs
A product that must be turned, a space that must be walked, a WebGPU rendering path, dense mesh raycasting or physics. Not for decoration.
WHO
Who owns it
CEO owns scene quality and budgets; Research watches three/WebGPU; Build makes the scene; Data records draw calls, GLB sizes and frame budgets; Ops verifies in a browser.
TOOLS
The registry
The engine manifest is the source of truth. These are its entries, including the ones that are not used on this build — the proof ledger says which is which.
three
npmThe WebGL/WebGPU renderer itself — every 3D scene stands on it.
@react-three/fiber
npmReact renderer for three.js — scenes as components, state as props.
@react-three/drei
npmCamera controls, shaders, loaders and abstractions — the essential R3F helper layer.
@react-three/postprocessing
npmProduction post FX — bloom, depth of field, ambient occlusion.
@react-three/cannon
npmPhysics simulation engine for 3D web environments.
@react-three/flex
npmFlexbox layout inside R3F canvases.
three-custom-shader-material
npmExtend Three.js core materials with custom vertex and fragment shaders.
@webgpu/types
npmStrict TypeScript declarations for zero-overhead native WebGPU workflows.
three-mesh-bvh
npmSpatial indexing for real-time raycasting on dense geometries.
@gltf-transform/core
npmNode-driven glTF optimization workflow — squeeze assets for fast client delivery.
spline-runtime
npmInstant deployment of interactive, production-ready vector-3D assets.
@dimforge/rapier3d
npmHigh-speed WASM physics for browser runtime simulations.
@react-three/xr
npmWebXR environment adapters inside React Three Fiber.
@pixi/react
npmHigh-speed 2D rendering canvases on clean WebGL layers.
sharp
npmHigh-speed server-side image modification — multi-format optimization, texture workflows.
dat.gui
npmDynamic visual control panels for real-time geometric tuning.
stats.js
npmIn-view performance monitor — frame-rate and memory.
maath
npmHigh-precision math utilities specialized for spatial 3D environments.
18 registry entries. The proof ledger on the Gantry page says which of them this build actually used.
RUN
Run it
ENGCTL / THE ENGINE FLOOR
$ engctl show 3dsptl$ engctl awaken 3dsptl$ engctl install 3dsptl --dir ./site`engctl` is the registry control surface. `awaken` checks wiring before it activates a cell; `install` writes the parts into a project.
PROOF
On this build
PARTIAL
ALL ELEVEN ENGINES →Dependencies present (@react-three/fiber, drei, postprocessing, three); no 3D scene ships on this site.
N/A and PARTIAL are stated, not hidden. The ledger is generated from this project, not from a template.
LIMITS
What this does not claim
This site is a PARTIAL: the dependencies are here, but no 3D hero ships. That is the honest state, not a hidden failure.
The engine is the how. The brief is the start.