Blender — what creators actually do with it

Creators here use Blender mostly as the place where other systems land. Ian Hubert (@ianhubertz) shows physics-driven flight: active and passive rigid bodies, hinge and spring constraints, and a linear motor constraint acting as a thruster, with custom properties wired through drivers for throttle and lights (rigid-body spaceship). Other posts treat Blender as an import target. ZOZO's open-source cloth and soft-body solver ships a Blender plugin (PPF Contact Solver), FreeMoCap exports webcam motion capture to Blender, Unity and Unreal (FreeMoCap), and a DuckStation fork dumps PS1 scenes as OBJ files that drop into Blender with positions intact (PS1 rips).

The newest thread is Blender driven by AI agents instead of by hand. One demo pairs Blender MCP with Tripo to turn a 2D reference image into an arranged 3D scene (Blender MCP + Tripo). @chase.h.ai had Codex model a hero asset through a repo of Blender skills without ever opening Blender, then embed it with Three.js, flagging mobile performance as the thing to check (Codex + Blender). @nateherkai had Claude write a Python script that builds and animates the scene; Blender rendered 360 frames on GPU in about 15 minutes and FFmpeg stitched them (Blender as code). Both of those guides are comment-gated, so the posts show results more than full method.

Unreal Engine shows up in 4 of these posts, Unity in 2 and Claude Code in 2, usually as parallel export targets or as the agent at the controls. Several saves are silent showcases of painterly or ink-brush looks with no breakdown (ink brush), and a weekly news roundup and a sponsored Higgsfield post mention Blender only in passing (news roundup). The motion-capture thread continues in One dancer, a thousand bodies. It suits 3D artists, technical animators and people wiring AI or capture pipelines into a renderer.