Skip to content

armgit / kiln

Public Imported from GitHub
0

Build and revise procedural 3D assets with your coding agent. Local MCP server, CLI and TypeScript engine with rendered review, editable source and GLB export.

fix: give the hero asset a consistent material story

Matt Kissingeref6dfc9bfad3
diff --git a/README.md b/README.md
index 5c96cb12..2d6555fc 100644
--- a/README.md
+++ b/README.md
@@ -86,10 +86,11 @@ The same program — the well above — rendered both ways:
|---|---|
| ![Well rendered flat-shaded, brickwork invisible](examples/well-cpu.png) | ![Same well with brick texture and normal relief visible](examples/well-gpu.png) |
-Geometry is equally legible in both: silhouette, proportion, orientation, part contact. But the
-brick curb is **flat grey** on the CPU. Not dimmer — *absent*. The albedo, normal, and ARM maps that
-make it stone simply do not exist in a flat-shaded render, and neither does the metal on the
-windlass.
+Geometry is equally legible in both: silhouette, proportion, orientation, part contact. But on the
+CPU the brick curb is **flat grey** and the roof is **flat orange**. Not dimmer — *absent*. The
+albedo, normal, and ARM maps that make one stone and the other weathered planks simply do not exist
+in a flat-shaded render. Every material cue an artist would judge is gone, while every geometric one
+survives.
**If your assets have textures or metal, use the GPU.** That is most real assets, and it is why
`auto` reaches for a GPU first. The CPU rasterizer is the floor that guarantees the loop runs
diff --git a/examples/hero-sheet.png b/examples/hero-sheet.png
index 59e01bcc..ad78f031 100644
Binary files a/examples/hero-sheet.png and b/examples/hero-sheet.png differ
diff --git a/examples/well-cpu.png b/examples/well-cpu.png
index cadd016b..7c0db1cb 100644
Binary files a/examples/well-cpu.png and b/examples/well-cpu.png differ
diff --git a/examples/well-gpu.png b/examples/well-gpu.png
index 59e01bcc..ad78f031 100644
Binary files a/examples/well-gpu.png and b/examples/well-gpu.png differ
diff --git a/examples/well.glb b/examples/well.glb
index 6b87075f..d8efdc9c 100644
Binary files a/examples/well.glb and b/examples/well.glb differ
diff --git a/examples/well.kiln.js b/examples/well.kiln.js
index 05430d40..574b6df4 100644
--- a/examples/well.kiln.js
+++ b/examples/well.kiln.js
@@ -15,9 +15,24 @@ async function build() {
metallicRoughness: 'kiln.texture.brick-wall-arm.v1',
},
});
+ // Every material carries a full albedo/normal/ARM stack, deliberately. A flat
+ // baseColor here would render as plastic next to the textured curb -- and it
+ // would undercut the point the contact sheet is making, since half the asset
+ // would show no material information even on the GPU.
+ // No baseColor tint on the textured materials: the recipe multiplies the tint
+ // into the albedo, so a dark brown here crushes the plank texture to near-black
+ // in the flat orthographic cells. Let the map carry the colour.
const wood = await materialRecipe('kiln.material.wood.v1', {
- baseColor: '#6a4a2c',
+ textureResources: {
+ baseColor: 'kiln.texture.weathered-planks-albedo.v1',
+ normal: 'kiln.texture.weathered-planks-normal.v1',
+ metallicRoughness: 'kiln.texture.weathered-planks-arm.v1',
+ },
});
+ // Iron stays untextured on purpose. The rusted-metal stack was tried here and
+ // read as a glowing red bar on a part this thin -- worse than the flat metal it
+ // replaced. Not every surface needs a map; the material story is carried by the
+ // stone and the planks, and forcing a texture onto the windlass hurt the sheet.
const iron = await materialRecipe('kiln.material.painted-metal.v1', {
baseColor: '#3f4348',
roughness: 0.42,