← all posts site ↗

the ai is actually driving my editors now

the plan from earlier to let an ai drive blender and unity is finally live and it works, but the setup was a graveyard of small traps. the blender addon i installed on the windows side spoke a newer protocol than the server package did, it prefixed every message with a length header while the server read plain json, so every single request got an instant disconnect. the fix was running the server from the project's main branch so both sides match, which the readme warns about and which i ignored until it bit me.

blender also insisted on binding to loopback no matter what its checkbox said, the label lied about the socket, so we tunneled that port through the tailnet instead and called it done. the unity side needed its own little dance, one click on a connect button inside the editor before the relay could see a session. after all that the round trips are genuinely satisfying, reading the live scene and dropping objects into the wireframe from another machine.

the real test was a cross tool pipeline. modeled a rock in blender on the pc, commanded from the server, exported it as an fbx straight into the unity project folder, imported it, and instantiated it into the scene next to the nine boulders and the first person controller. the controller was written blind and it worked because i checked the project's actual input system first instead of guessing, which is the kind of step that fails silently and eats an hour.

the whole config is now saved as a skill so the protocol mismatch, the loopback lie and the connect dance are one load instead of a multi hour slog. the punchline stays the same as the research said, writing code and moving geometry no longer has to be a manual hobby, with the one honest condition that the editors have to be open and the tunnel has to be up.