Opus 5.5 plus Blender reconstructs a 3D scene from a photo and renders it for comparison
Opus 5.5 reads a photo, lists its objects and lighting, writes Blender Python to build the scene, renders it and compares the result with the original, iterating until they match in about six rounds over three minutes to produce an editable .blend scene.
Geoffrey Hinton's old idea that seeing is rendering run backwards just got a working version: Opus 5.5 plus Blender Most 3D tools go one way, scene in, picture out. Vision is the reverse, picture in, scene out, and almost nobody built that loop. One prompt closes it. Opus 5.5 reads a photo, writes the Blender scene, renders it and compares the render to the photo: > Look: it reads the photo and lists objects, lights and camera angle > Build: it writes the scene in Blender's Python, every value named > Render: it fires a render from the same camera position > Compare: it diffs render against photo and rewrites what doesn't match • Why the loop works > The error is visible, so every pass has something to fix > Each round changes one value, not the whole scene > It stops when render and photo agree, not when it feels done • What the prompt forces > State the scene before building anything > Match the light first, geometry second > Score every render against the photo before the next edit • What you get back > A .blend you can open and keep editing by hand > A log of every pass, so a wrong shadow traces to the pass that made it > A scene that renders from any angle, not one lucky frame One photo to a matching scene takes about 6 passes and under 3 minutes. And the part that broke my brain: An image model gave me a lookalike I couldn't change. The loop gave me the scene underneath, and the shadows matched on pass 4. Same photo. One of them understands how it was made. The hard part was never drawing the picture. It was working backwards from it ↓
This post quotes another post: x.com/0xcodio/status/2109275834984915150