Comment by drusepth
13 hours ago
A huge benefit of local setups at our studio is that a lot of our software can't run headless, so when we're having agents work in Blender or in Unity etc with MCP that'd otherwise eat up our normal computer use. (Try to have two people try to work in the same Unity editor at once... then try ten!)
We also built some QA agents that are always playing our games from the same builds a player would and flagging things to fix/improve; that alone needs the game focused and front-and-center so it can properly screen-capture for deciding what inputs to take next (and for screenshots/replays), which also means we can't really do any hands-on work at all on the machine when it's running.
Having a separate (and tiny) machine for all of this has been great. We don't bother with local models because, you're right, the $20/month sub is way better than anything that can run on small consumer hardware atm.
> A huge benefit of local setups at our studio is that a lot of our software can't run headless, so when we're having agents work in Blender or in Unity etc with MCP that'd otherwise eat up our normal computer use
I'm curious about your setup. I've been tinkering with the idea of setting up Blender (cli use) in a container to allow agents to verify the scripts they are generating compile at a minimum. One thing I've found extremely helpful was generating a RAG of the current version of Blender.
For anyone wondering, I'm running Gemma4 26b A4B on a mini PC with 32 GB of DD4 and a Vega 7 iGPU (llama.cpp w/ Vulkan).