meshgen
Authors the mesh assets the props slice draws. It runs by hand, not from the build: `M.generate()` writes `PropMaskFace.mesh` into `/source/demo/props/` and the world carries the result, so a boot loads geometry rather than computing it.
demo.props.meshgen
Authors the mesh assets the props slice draws. It runs by hand, not from the
build: M.generate() writes PropMaskFace.mesh into /source/demo/props/ and
the world carries the result, so a boot loads geometry rather than computing it.
PropMaskFace
A clown mask as a height field on a polar grid: face(x, y) is the relief —
a domed forehead, two brow ridges, two eye sockets sunk into them, a nose ridge
with a bulb at its end, cheeks, and a mouth trough turned up at both corners.
The grid is a centre vertex and NR rings of NA points, which puts the
resolution where the relief is and leaves the rim cheap.
Normals come from a central difference of the same face function rather than
from the triangles, so the relief shades smoothly at any ring count.
The mesh is closed: the front surface, a dished back so the mask reads as a shell from an oblique angle, and a rim joining the two. Two hundred instances of it hang on the corridor wall.
Re-running it
M.generate() is idempotent — it rewrites the same asset in place and keeps its
guid, which is what every mask's Model references. Run it after changing the
relief, then commit what it writes.
Scoped to this part · feeds back into the world's score.