3D engine that AI agents drive
Accept the vegetation size growth, list the new material tags in tests and docs
Nguyen Xuan An2cd452ef489f
diff --git a/changes/321.size.md b/changes/321.size.mdnew file mode 100644index 00000000..d8ef82bd--- /dev/null+++ b/changes/321.size.md@@ -0,0 +1,12 @@+- entry:core: the wind heading uniform and its shadow-pass redraw check, 65 bytes against an allowance of 64, so a recipe can set the wind direction.+- entry:agent-scene+lazy: the on-demand vegetation module loads the tree generator, species, bark and leaf textures that a recipe vegetation node grows; nothing loads without a vegetation field.+- entry:agent-asset+lazy: the same on-demand vegetation module, reached through the shared agent scene chunk list.+- scene:gltf-box: the wind heading uniform in the world material shader and renderer, 70 bytes against an allowance of 64.+- scene:gltf-box+lazy: the same wind heading uniform, 70 bytes.+- scene:agent-scene: the vegetation node validation, the generated-part merge in the scene, the environment.wind field and the capabilities text that describes them; the tree generator itself loads on demand.+- scene:agent-scene+lazy: the on-demand vegetation module and the tree generator it loads, counted when every lazy module is bundled.+- tool-total: the vegetation node field, the wind environment field and two material tags are schema in scene_create, scene_apply and scene_create_asset; the detail stays in scene_capabilities.+- tool:scene_create: the recipe schema gains the vegetation node field, environment.wind and the foliage and grass material tags.+- tool:scene_apply: node edits and set-environment share those schema pieces.+- tool:scene_create_asset: the asset recipe shares the environment schema with the wind field.+- result:scene_capabilities: the vegetation entry (node fields, levels, season, wind, limits) and the two new material tags, kept here so the tool schemas stay short.diff --git a/docs/agent-scene.md b/docs/agent-scene.mdindex 32ccb329..17d485eb 100644--- a/docs/agent-scene.md+++ b/docs/agent-scene.md@@ -102,7 +102,7 @@ Shared resource IDs generate geometry once, regardless of the number of mesh nodMaterials contain `id`, `tag`, `color`, `metallic`, `roughness`, `emission`, optional `emissiveColor`, `opacity`, `alphaMode`, `doubleSided` and `pattern`.The defaults are `surface`, `[0.5, 0.5, 0.5]`, `0`, `0.5`, `0`, opacity `1`, `opaque` and `false`.-The tag can be `surface`, `unlit`, `liquid` or `foam` and remains fixed during editing.+The tag can be `surface`, `unlit`, `liquid`, `foam`, `foliage` or `grass` (the last two sway in `environment.wind`) and remains fixed during editing.`liquid` refracts and tints what lies behind it: its color is the light one metre lets through, so `[0.56, 0.84, 0.88]` is clear water. `foam` draws soft blended droplets.Any `opacity` below one draws the material blended after opaque geometry, which suits glass, windows and visors. `alphaMode` accepts `opaque` or `blend`; cutout masking needs a texture and is not available in procedural recipes.`doubleSided` draws and lights both faces of thin sheets.diff --git a/tests/agent-scene.test.js b/tests/agent-scene.test.jsindex 0d68ff14..933b8721 100644--- a/tests/agent-scene.test.js+++ b/tests/agent-scene.test.js@@ -93,7 +93,7 @@ test('shader arithmetic rejects cancelling product overflow and nonfinite emissi});test('recipes author liquid, foam and blended glass with batch-safe material handles', () => {- assert.deepEqual(AGENT_SCENE_CAPABILITIES.materialTags, ['surface', 'unlit', 'liquid', 'foam']);+ assert.deepEqual(AGENT_SCENE_CAPABILITIES.materialTags, ['surface', 'unlit', 'liquid', 'foam', 'foliage', 'grass']);const input = recipe();input.materials.push({ id: 'water', tag: 'liquid', color: [0.56, 0.84, 0.88], roughness: 0.05 });input.materials.push({ id: 'glass', color: [0.9, 0.95, 1], opacity: 0.3, doubleSided: true });