Skip to content

3D engine that AI agents drive

Merge remote-tracking branch 'origin/main' into 2015-wt

t5686da9465b9
diff --cc docs/cycles-parity.md
index 59b14f70,387bf29f..529696de
--- a/docs/cycles-parity.md
+++ b/docs/cycles-parity.md
@@@ -1089,11 -1089,10 +1089,12 @@@ The bridge is not exact. Cycles on the
| the same JSON, 3 bounces | 0.4065 / 0.3795 / 0.3391 |
| the same JSON, 2 bounces | 0.3416 / 0.3190 / 0.2850 (0.91 / 0.96 / 0.92 of the original) |
| the same JSON, 1 bounce | 0.2555 / 0.2386 / 0.2132 |
+ | original `.blend`, every light's own bounce limit cleared (`--variant sun-only-unlimited-bounces`) | 0.6371 / 0.5605 / 0.5272 (the export at 8 bounces is 0.91 / 0.97 / 0.92 of it) |
- The gap is now the other way round: the export is 1.6 times brighter, not 10 times dimmer, so the sun fix is in and the sun-only gate is not met. The sun in the file has a per-light limit of 2 bounces (`cyclesSettings.max_bounces`), which the JSON format cannot carry, so the original's sun light stops at two bounces and the export's runs to eight. Capping the whole export at 2 bounces lands within 4 to 9 percent of the original `[inferred: it caps camera paths and every other light as well, which are off here, so only the sun matters; a run that clears the sun's limit in the original would settle it]`; the remainder is not explained. Cook was not measured: its native addon is not built on this machine. This does not affect the Cook against Cycles comparison above, which reads one file on both sides; it means the scene Cook was tested on is a faithful reading of the Classroom only in its camera, the 886 instances it exports, the sun and the world.
+ The gap is now the other way round: the export is 1.6 times brighter, not 10 times dimmer, so the sun fix is in and the sun-only gate against the original as it stands is not met. The cause is shown, not only inferred: the original has per-light bounce limits (`cyclesSettings.max_bounces`: sun 2, corridor ceiling light 2, blackboard light 1, one point light 1) that the JSON format cannot carry, so the original's sun stops at two bounces and the export's runs to eight. Clearing those limits in the original (`classroom_bridge.py reference --variant sun-only-unlimited-bounces`, same 960x540, 256 spp, seed 1, 8 bounces) raises its sun-only mean from 0.3762 / 0.3310 / 0.3113 to 0.6371 / 0.5605 / 0.5272, and the export is then 0.91 / 0.97 / 0.92 of it, 3 to 9 percent dimmer. So the 1.6 times is the bounce limit, and a bridge that cannot carry the limit differs from the file by that limit; the 3 to 9 percent left, a little more in red and blue than in green, is not explained. Capping the whole export at 2 bounces lands within 4 to 9 percent of the original only because it applies the limit to every path. Cook was not measured: its native addon is not built on this machine. This does not affect the Cook against Cycles comparison above, which reads one file on both sides; it means the scene Cook was tested on is a faithful reading of the Classroom only in its camera, the 886 instances it exports, the sun and the world.
+Since #2015 the format carries it: the exporter writes `environment.sunMaxBounces` (and `maxBounces` on point, spot and area lights) for every light whose own limit is below the scene's, and the native `cycles` kernel stops that light after its bounces ([lighting guide](lighting.md#a-lights-own-bounce-limit)). A light without the field runs as before, so no scene changes unless it names a limit. Not measured yet: the Classroom sun-only run against the original needs the GPU, so the "within 10 percent mean RGB" gate stays open until it is rendered.
+
### Commands
On a machine with Blender 5.3, Node, `uv` and the built Cook addon (a GPU):