Three.js From Zero · Article s12-15
S12-15 Procedural Meshes after S10
Skip to demo
Season 12 · S12-15 · Specialized Production Patterns
Procedural Meshes after S10 — taking generated forms into a production scene
Procedural meshes get easier every month. Making them belong inside a real scene is still the hard part. This finale is about that handoff: generated form to art-directed scene element.
aigeometryproduction
1. Why this article exists
It closes the season by continuing the AI line without lapsing back into pure novelty. The question is not “can we generate it?” but “can we ship it?”
2. What we are building in the demo
- A deformable hero mesh with controls for structure and refinement.
- A scene role model: background prop, focal object, or variant layer.
- A framework for deciding when procedural geometry is worth the downstream cleanup.
3. Live demo
The demo below is a compact study model, not a full production system. The goal is to make the article’s mental model tactile: what changes, what matters, and what you would keep when the codebase graduates into a real project.
booting...
Season 12 is deliberately less single-vertical than Season 11. The throughline is still applied production: every demo is framed as a pattern you could reuse in paid work.
4. Implementation sketch
const mesh = generateBase(seed);
const cleaned = remeshForShading(mesh);
const tagged = assignSceneRole(cleaned, 'hero-prop');
scene.add(tagged);5. Production notes
Useful companion articles from earlier seasons:
What usually goes wrong first:
- Interesting form is not the same thing as usable form.
- Generated geometry that cannot be shaded or simplified cleanly becomes workflow debt.
- Production scenes need role clarity, not endless morph possibilities.
6. Takeaways
- Procedural geometry is only valuable when it earns a role in the final scene.
- Cleanup, simplification, and shading readiness matter more than novelty.
- The production question is always “what is this for?”