render request: pin object materials, floor and lighting too (meshes already match)

render_request/README.md

@@ -51,12 +51,29 @@ to the one under test. Measured on the current demos: a reach task scores 82% wh
 manipulation tasks score 2% and 0%, with 99 of 100 rollouts running to the step cap — acting, never
 completing.
 
-**So please render all 20 demos of a task under ONE fixed appearance:** one table material, one
-floor, one lighting setup, held constant across every demo and every task. Concretely, either
-disable `TextureModder` and `LightingModder`, or hold `variant_seed` constant across the batch.
+**So please render all 20 demos of a task under ONE fixed appearance.** Everything in this list
+held constant across every demo of every task:
 
-If your pipeline cannot pin them, please say so rather than varying them — we would rather know and
-design around it than discover it in the frames again.
+| pin | why |
+|---|---|
+| **table material** | varies per demo today — six demos of task 953 have six different tables |
+| **floor / background** | varies with it; one demo sits on brown parquet, another on green grass |
+| **lighting** | `LightingModder` is active per demo |
+| **object materials / textures** | `TextureModder` recolours the OBJECTS too, so the same mesh reads as a different object between demos |
+
+Concretely: disable `TextureModder` and `LightingModder`, or hold `variant_seed` constant across
+the whole batch.
+
+**Object meshes do NOT need changing** — we verified those are already consistent. The eval scene
+loads `cup_2`, `muffin_4`, `sweet_potato_4`, `tissue_box_2` from exactly the same
+`tabletopgen/task_88200032_layout_1_rand_00000` directory the training scene references. The
+problem is purely that their *materials* are randomized, so identical geometry looks like a
+different object from demo to demo.
+
+Object PLACEMENT should keep varying — that is the axis the benchmark is meant to test.
+
+If your pipeline cannot pin any of these, please say so rather than varying them — we would rather
+know and design around it than discover it in the frames again.
 
 ## 2. What to render