3D engine that AI agents drive
Record the metal floor measurement, nothing kept (part of #167)
Nguyen Xuan And019f5a5fa0b
diff --git a/bench/reference/README.md b/bench/reference/README.mdindex df8ea9a4..2ec02cce 100644--- a/bench/reference/README.md+++ b/bench/reference/README.md@@ -1014,3 +1014,26 @@ Every other scene is unchanged (it has no object probe). The shadow on top of thFrame cost, RTX 3060 (`frame-time.mjs`, 200 frames): `brick-flat` plain 0.385 ms (0.375 to 0.39 before), `metal` plain 0.43 ms (0.44 to 0.45 before). SwiftShader `transparency` in `bench/runtime`: 350.3 ms (345.9 and 347.5 before; 15 frames, machine under load).Bundle size: the floor trace and the lookup correction add about 250 bytes gzip to the three bundles that carry reflection probes (`entry:agent-scene+lazy`, `entry:agent-asset+lazy`, `scene:agent-scene+lazy`), so each budget in `bench/size/budgets.json` is raised by 280 bytes. Measured: they were over by 244, 239 and 253 bytes.++## The floor of `metal`, measured and nothing kept (2026-11-03, part of issue #167)++Main reproduced `baseline.json` first (`metal` 0.0957 against Cycles, EEVEE 0.0916, GPU, on the stored arrays). The floor holds 44% of the frame error. Replacing the floor with the Cycles pixels (the ceiling for all floor work) gives 0.0555, so the floor costs 0.040 of 0.0957. FLIP over floor regions, cut by distance on the floor plane to the footprint of the nearest part (the parts' own pixels excluded), 67js against Cycles with EEVEE beside it, and the mean luminance difference to Cycles in display space (the last column is the EEVEE gap, FLIP difference times pixels):++| Region | pixels | share of the error | FLIP 67js (EEVEE) | luminance 67js minus Cycles (EEVEE) | EEVEE gap |+| --- | --- | --- | --- | --- | --- |+| contact, under 0.15 | 15887 | 6.8% | 0.2362 (0.2265) | -0.0021 (-0.0262) | 154 |+| near, 0.15 to 0.5 | 23729 | 8.2% | 0.1916 (0.1611) | +0.0071 (-0.0054) | 688 |+| mid, 0.5 to 1.5 | 99853 | 13.7% | 0.0762 (0.0598) | -0.0022 (-0.0018) | 1638 |+| open, 1.5 to 4 | 56116 | 6.0% | 0.0592 (0.0517) | -0.0066 (-0.0038) | 420 |+| far, over 4 | 81837 | 9.0% | 0.0610 (0.0531) | -0.0064 (-0.0023) | 646 |++Oracle ceilings (Cycles pixels pasted into one region of the 67js frame, whole frame FLIP): contact and near 0.0831, everything within 1.5 units 0.0698, within 4 units 0.0638, the sun shadow alone 0.0940, its edge band alone 0.0944. Each candidate cause below was tested against the data and none gives a change worth keeping.++- Shadow shape and softness: ruled out. Blender's sun is 1 degree wide (`SUN_ANGLE` in `render-blender.py`). The 67js filter reaches 3.5 texels of the 2048 map (extent 6, 5.9 mm a texel), about 2 cm, and a 1 degree sun gives a penumbra of 1.4 cm at 0.8 m and 2.1 cm at 1.2 m, so the two agree. Floor pixels where Cycles is below 0.6 of the open floor are 67js +0.0024 (EEVEE -0.0397) and score 0.204 (EEVEE 0.265): 67js is closer than EEVEE there, and a perfect shadow would be worth 0.0017.+- Shadow darkness (ambient in the shadow): ruled out by the same row. The shadow bands are within 0.013 of Cycles in luminance and hold 3% of the error.+- Floor level, colour and sky reflection: open floor is within 0.002 to 0.008 of Cycles in `metal`, `car-paint`, `brushed-film`, `material-spheres`, `outdoor-hdri` and `character`, and where it is off (the bottom right of the `metal` family, up to 0.008) EEVEE is off by the same amount, which is Cycles-only light from the copper box. A flat gain on the far floor is worth at most 0.0013 (+0.4% display: 0.0950 to 0.0937; a gain of 1.01 on the whole floor is worse, 0.0979), and so is a +0.4% push of red and green (0.0945). That is the size of a tuning knob and the other scenes do not show the offset, so no constant is added.+- Contact and sky occlusion: the visible halo (Cycles 0.620 to 0.635 around the parts, against 0.645 on open floor) is the band where 67js is worst against EEVEE (FLIP 0.164 against 0.112, 8% of the error), but analytic occlusion is not the cause. Over the sunlit floor within 2 units of each part, the difference to Cycles correlates with a sphere's cosine form factor only for the chrome sphere (+0.31; the excess is +0.036 within 0.2 units of it, +0.009 to 0.5 and nothing beyond); steel, torus and box give -0.06, -0.25 and +0.16. A cosine form factor sphere applied to the floor of the 67js image, as an oracle, was worse or equal in every variant: the chrome sphere alone 0.0957 (strength 0.2) and 0.0969 (0.5), sphere plus steel 0.0975, four spheres 0.1004 to 0.123 by size and strength. A mirror sphere shows the floor on its lower half, so what Cycles darkens there is bounced light, which #209 tried (0.1246) and did not keep.+- Screen-space occlusion: `--ambient-occlusion 0.3 --ambient-occlusion-radius 1.5` takes the halo band from 0.164 to 0.125 and the floor from 0.0873 to 0.0865, and the frame to 0.0970 (0.2 at radius 2.5 gives 0.0971; 1 at radius 1.0 gives 0.1018). The pass multiplies the whole frame, so it darkens the metal parts too, and with the parts untouched the floor would gain about 0.0004. It stays opt-in.+- Bake: `--bake metal --bake-preset standard` scores 0.1526, worse.++Where EEVEE beats 67js on the floor is the mid band (46% of the gap) and the open and far floor (30%), where the means are within 0.002 to 0.007 and the difference is spread thin (FLIP is also reading Cycles' own noise there); the one concentrated piece, the halo at the chrome sphere, is bounced light. No engine file, scene, baseline row or budget changed, and the first box of #167 stays open: `metal` 0.0957 against EEVEE 0.0916. The floor has no single cause left that a measured change reaches; what is left sits in the parts (the chrome sphere's lower half and the steel cylinder) and in bounce light.