3D engine that AI agents drive
Merge remote-tracking branch 'origin/main' into feat/grand-scene-options
Nguyen Xuan An86f41f519478
diff --cc CHANGELOG.mdindex 4b0eb0ea,7b47bb9c..37783c0f--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -2,8 -2,7 +2,9 @@@## Unreleased+- Add three options for each grand reference scene, to pick from (part of issue #168, which stays open until An picks). `bench/reference/grand-scenes.js` holds `mountain-valley`, `temple-hall` and `megacity-dusk` as `-a`, `-b` and `-c`, each with its own composition, light and time of day, drawn by `npm run reference -- --grand` into `grand.json` and `images/grand-<id>.jpg` (`baseline.json` and the existing images are unchanged). The Blender side gained a `gradient` world, written as the same equirectangular image 67js draws. `bench/reference/grand-sheets.py` makes one comparison sheet per scene.++ - Make the recipe bake presets bake large rooms (issue #189). A preset that does not fit the 5 million path step budget at 16 samples and 1 texel per unit now gives up bounces one at a time instead of refusing, and `bake.reduction` tells the agent what it asked for, what ran and that explicit samples, bounces and texelsPerUnit (up to 24 million path steps, 20 s inline) buy more. `temple-hall` at `standard` now bakes (16 samples, 1 bounce, 1.37 texels per unit, 0.0705 against 0.1504 unbaked with a probe). `fine` is now the same as `standard`: five samples and density mixes within the 20 s limit scored no better on the room scenes. Table in `bench/reference/README.md`.- Score the recipe bake presets against Cycles (part of issue #170, open for the frame costs). `standard` scores 0.127 to 0.159 on the three rooms (no bake 0.51), `fine` is no better, and `standard` and `fine` refuse `temple-hall`. Table in `bench/reference/README.md`.- No test asserts real elapsed time any more (issue #179): work counts and a fake clock replace stopwatches. `smoke:agent-review-close` and `smoke:film-physics` are wired; the second starts its own server.- Show the floor and the other parts in smooth metal (part of issue #167, which stays open). `traceObjectProbes` in `src/probe-trace.js` gives each part with `metallic` of at least 0.5 and `roughness` of at most 0.6 a reflection probe of its own, traced from the middle of the part without it (up to 8 parts, lit by direct light and the environment's diffuse light), and `placeProbes` assigns it. `metal` scores 0.1294 to 0.1036 against Cycles (EEVEE 0.0916), `brushed-film` 0.1149 to 0.1029, `car-paint` 0.1059 to 0.1038, `material-spheres` 0.1312 to 0.1293; every scene without a reflective part is unchanged to four digits and draws the same frame (`metal` 1.51 ms plain, 1.58 ms with four probes). `npm run reference -- --object-probes` places them (opt in; the committed baseline is unchanged); recipes do not yet.