Opus 5.5 写 Blender 场景脚本并自动渲染

Codio @0xCodio原推发布于 2026.10.12

在 X 上打开原推

Opus 5.5 wired into Blender renders a finished scene while most people are still setting up the camera Most AI render tools spit out a flat image you can't touch, no scene, no lights, no way to change one thing without redoing all of it. Opus 5.5 never outputs the picture, it writes the Blender scene itself, then presses render: > Read: it parses your description into objects, materials, camera and lights > Build: it generates the .blend through Blender's Python, every value named > Light: it places a 3-point setup and checks the histogram for blown highlights > Render: it fires the render, looks at the result, and fixes what came out wrong • Why a scene beats an image > A bad shadow is one light to move, not a whole regeneration > It renders at any resolution, print to wall, with no quality loss > You open the .blend in Blender and keep working by hand • What it actually controls > Materials with real roughness, metalness and displacement, not a flat texture > Camera focal length and depth of field set from the shot you asked for > Geometry nodes for anything repeated, so a forest isn't 400 copies • Where it pulls ahead of image models > It reasons about why a composition feels off, then moves the camera > It keeps 30 objects consistent across every frame of an animation > It hands a studio a file they can finish, not a render they must redo One full scene builds and renders in about 80 seconds. And the part that broke my brain: A render I asked an image model for took 6 tries and still wasn't editable. Opus built the scene once, and I fixed the one wrong light myself in 10 seconds. Same frame. One of them you can still open tomorrow. The output was never the image. It's the scene that made it ↓

这条是引用着另一条写的：x.com/0xcodio/status/2109275834984915150