3D engine that AI agents drive
JavaScript 3d3d-engineagentic-aiai-agentsblenderclaude-codegame-enginegaussian-splattinggltfjavascriptmcpmcp-servermodel-context-protocolpath-tracerpath-tracingpbrrenderingthreejs-alternativewebgl2webgpu
Fix the scene skill references after checking them against the code (#2247)
Nguyen Xuan An0e615331f602
diff --git a/skills/build-crucible-scene/references/materials.md b/skills/build-crucible-scene/references/materials.mdindex ed58d1b9..a6152e9c 100644--- a/skills/build-crucible-scene/references/materials.md+++ b/skills/build-crucible-scene/references/materials.md@@ -30,8 +30,9 @@ Starting values, then judge with `scene_look`:| Rubber, cloth | dark | 0 | 0.9 || Lamp, screen | the hue | 0 | any, with `emission` 2 to 8 |-Metal is 0 or 1 in practice; use a value between only for a worn edge. A `metallic` above 0 no longer fails `scene_apply` with-"Light bake takes at most 200000 triangles" (#2202 is fixed): no bake runs unless the recipe asks for one.+Metal is 0 or 1 in practice; use a value between only for a worn edge. A smooth metal part adds automatic reflection probes, and a scene over+200000 triangles used to fail `scene_apply` with "Light bake takes at most 200000 triangles" although no bake was asked for. Since #2202 the+probes are skipped past that limit and the sky reflection stays, so `metallic` above 0 is safe; the skip reason names `environment.objectReflections`.## Patterns@@ -142,7 +143,7 @@ fade each along the beam. Point and spot lights also scatter in `volumeFog` (up- `set-material` takes colour, `metallic`, `roughness`, `emission`, `emissiveColor`, `opacity`, `alphaMode`, `doubleSided`, `pattern`, `map`, `subsurface`, `snippet`, water fields and the layer fields. It rejects `tag` (the error lists the fields it takes). To change a tag, `add-material` a new one and `set-node` onto it.- A textured import (GLB placement): the `asset.materials` override multiplies its `color` into the texture, it does not replace the texture. To recolour, tint with `color` (a dark texture stays dark), or flatten with `asset.flatten.color`, which paints every material of the placement one colour and drops the textures; a named override still wins.-- Faces that lie flush flicker: `decal: true` on the top node or `depthLayer` 1 to 4 (see `light.md`). Do not add them for near-flush faces; the renderer ranks those itself.+- Flush faces are ranked automatically, so a flicker needs no fix. To choose which of two flush nodes wins (a sticker on a surface), set `decal: true` on the top one, or `depthLayer` 1 to 4 to stack several (see `light.md`).## Judge a surfacediff --git a/skills/build-crucible-scene/references/particles-and-vfx.md b/skills/build-crucible-scene/references/particles-and-vfx.mdindex a5e22037..9fb8951d 100644--- a/skills/build-crucible-scene/references/particles-and-vfx.md+++ b/skills/build-crucible-scene/references/particles-and-vfx.md@@ -30,6 +30,7 @@ one burst. `start` (alias `delay`) is the time of the first birth. `stop` is an`start` and at most 3600, so `{ "start": 1.6, "stop": 0.4 }` fails with "expected a time in seconds after the start (1.6), such as 3.6". Nothing is born at or after `stop`;particles already born finish their life.+`emitter.shape` is `point` (default), `box`, `sphere`, `disc` or `mesh`; `emitter.position` is in world metres. `direction` (default up) and `spread` (cone angle in degrees, 0 to 180, default 30) aim the launch.A box emitter takes `halfExtents`, not `radius`. Crucible no longer writes a `radius` into a box emitter, and a stored `radius: 0.5` on a box is dropped, so later batches apply (#2203). `sphere` and `disc` take `radius`.`set-particles` may name a node added in an earlier batch (#2204); the node and the system can be in one batch or two. A system replaces its node's own geometry with the@@ -43,7 +44,8 @@ A system can validate and draw nothing. Check these before changing values:2. The card. A `plane` faces +Z and keeps its facing (there is no camera-facing billboard), so seen from the side it is edge-on. Set `doubleSided: true` on the material and `orient: "random"` on the system, or use a `box` or low-poly sphere.3. `scale: "grow"` starts every particle at size 0 and reaches full size at death; `"shrink"` does the reverse. A short life with `grow` is mostly tiny.4. `alpha` and `color` become vertex colours and `alpha` multiplies the colour, so a particle fades toward black and never becomes see-through. On an `alphaMode: "add"` material black adds nothing, so the fade works; on an opaque or `blend` one the particle turns black against the background.-5. Size. `size` is the scale of the node's geometry in metres: a unit `plane` with `size` 0.002 is 2 mm.+5. `floor`. It stops a particle that is born above that height and reaches it; the particle then stays where it landed until it dies (with `bounce` above 0 it bounces instead). A particle born below `floor` ignores it. Combined with `scale: "shrink"` or an `alpha` fade, particles that landed vanish where they lie.+6. Size. `size` is the scale of the node's geometry in metres: a unit `plane` with `size` 0.002 is 2 mm.## Spray, dust and sparks@@ -82,7 +84,7 @@ any other tag is refused with a message that says so. `floor` stops them on the```json{ "expectedRevision": 1, "operations": [- { "type": "add-geometry", "geometry": { "id": "spark", "type": "box" } },+ { "type": "add-geometry", "geometry": { "id": "spark", "type": "box", "bevel": 0 } },{ "type": "add-material", "material": { "id": "spark", "tag": "unlit", "color": [1, 1, 1] } },{ "type": "add-node", "node": { "id": "sparks", "geometry": "spark", "material": "spark" } },{ "type": "set-particles", "particles": { "systems": [@@ -139,7 +141,7 @@ Point and spot lights scatter in it (at most 8, points first, no shadows, no lig] }```-- Open bug #2205: `scene_look` can fail with "WebGL render failed with error 1282" for a volume fog that combines `noiseAmount`, `drift`, `heightFalloff` and `color` on a physical sky, and the culprit field is not isolated. Add the fog fields one at a time with `scene_look` between, and keep the last set that renders.+- Open bug #2205: `scene_look` can fail with "WebGL render failed with error 1282" for a volume fog that combines `noiseAmount`, `drift`, `heightFalloff` and `color` on a physical sky, and the culprit field is not isolated. Add the fog fields one at a time with `scene_look` between, and keep the last set that renders. The fog block above (a spot light, `density`, `noiseAmount`, no `heightFalloff`, `drift` or `color`, default sky) rendered on a GPU backend without that error.- A visible beam is a cone part, not a fog effect: give it an `alphaMode: "add"` material with a low `opacity`, stack two or three shells of growing radius, and fade each along its length with a `snippet` (see `materials.md`, "Shader hooks"). One shell shows a hard silhouette from the side.## Not built yet