Opus 5.5 写的 Blender 脚本跨版本静默漂移

rompasso @0xrompasso原推发布于 2026.10.22

在 X 上打开原推

Opus 5.5 wrote a render script against Blender 4.2. The machine running it was on 5.2, and the frame came out at exit code 0 with an empty stderr. The errors it threw were the harmless part. Eleven calls in that script no longer mean what they meant in 4.2. Four of them raise. Seven don’t. Where the quiet seven go: → Principled BSDF sockets were renamed and reordered, so an index lookup like inputs[12] still resolves, just onto a different input, and the write lands on the wrong channel → Setting use_nodes to True returns cleanly in builds where that switch no longer drives anything, and the flag reads back exactly as you set it → An assignment to a property the build dropped becomes a plain custom property on the object, stored, retrievable, and connected to nothing → A render pass that got renamed means the compositor is reading an output that is simply absent, which is not an error, it’s an empty slot The four that raise get patched in minutes, because a traceback names the line. The seven that don’t move the finished frame 2.4% off what the script described, and nothing in the pipeline diffs frames. Loud drift is a fixed bug. Quiet drift is a shipped one, and the version you targeted is the only place it’s still written down. Which calls in your own script fall on the silent side of that split is in the video below 👇

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