ZeroBlender — Blender-style modeling in Zero
- Author
- zero-proxy @ DESKTOP-DB3UJOJAgent
- Opened
- Nov 15, 2026
- From
- contrib-bd5m9sfg
- Into
- main
- Merge
- Can be merged by fast-forward
ZeroBlender keeps only what its documents need between calls. Measured on the 44-step superbike replay (ZeroBlender execute_blender_code, one awaited step at a time, debug engine, live world), compared with the unchanged package on the same engine build.
What changed (3 files):
- pythonRuntime: the runtime a call is executing in is the active one for the length of that call only (a stack of running runtimes), and no module-level reference to a finished runtime remains. Before,
M.activeCallpointed at the last created runtime for ever, so a closed session's whole interpreter (environment, scopes, closures) stayed alive after eviction. Also corrects list.sort(key=) calling back into another session's runtime when two sessions are live. - pythonRuntime: every execute runs in a fresh namespace child of the builtins, as the Blender MCP add-on gives each call. Names a call defines are dropped when it returns; imported modules stay in R.modules. No step of the replay reads a name defined by an earlier step.
- blenderSession (packMeshes): a mesh no object uses is released at flush (its stores are freed, it leaves bpy.data.meshes). A reload from scene.json brings back only the meshes objects use, so the document never held them. Behaviour note: a mesh created with bpy.data.meshes.new in one call and attached to an object in a later call no longer survives between the calls, and a released mesh name can be handed out again (an object named like a deleted one gets mesh name "X", not "X.001").
- meshBuf / blenderSession: word stores and vec3 stores grow by doubling; Mesh:trim() (called from packMeshes for every mesh an object uses) gives each store back the capacity beyond its used size, with a bulk byte copy.
- blenderSession: image pixels rest as one f32 buffer between calls;
img.pixelsunpacks to a table on first read in a call and S.packImages (end of flush) puts it back. Values read back are f32, as in Blender.
Measured (luau.heap / substrate.cpuBuffers, MB; baseline = unchanged package, fixed = this change, two fixed runs):
| point | baseline | fixed run 1 | fixed run 2 | | end of step 44, luau.heap | 467.5 | 355.9 | 351.6 | | end of step 44, cpuBuffers | 136.1 | 26.3 | 27.0 | | end of step 44, after a full collection, luau.heap | 463.4 | 351.3 | 348.1 | | after the idle close (session evicted), luau.heap | 486.4 | 350.1 | 346.9 | | after the idle close and a full collection, luau.heap | 434.2 | 335.5 | 331.3 | | after the idle close, cpuBuffers | 0 | 0 | 0 |
Final document, fixed vs baseline: same scene_info (338 objects, 35 materials, object names/locations), the same geometry hash, vertex and face count for each of the 338 objects, the same image pixel sums, and identical printed output for all 44 steps. The released meshes were the 569 of 786 no object used (217 are used). The only difference is the mesh data-block names, which lose the ".00N" suffix a retained orphan forced.
Source world: 9bd61ce0-8a77-4959-adc7-9fa4c25c0c3b Contributed paths:
- ZeroBlender.package/modules/blenderSession.module/init.luau
- ZeroBlender.package/modules/meshBuf.module/init.luau
- ZeroBlender.package/modules/pythonRuntime.module/init.luau
- ZeroBlender.package/package.yaml
- ZeroBlender.package
- ZeroBlender.package/modules/blenderSession.module
- ZeroBlender.package/modules/meshBuf.module
- ZeroBlender.package/modules/pythonRuntime.module
- ZeroBlender.package/blender.toolbox/compare_to_reference.tool/init.luau
- ZeroBlender.package/blender.toolbox/execute_blender_code.tool/init.luau
- ZeroBlender.package/blender.toolbox/get_object_info.tool/init.luau
- ZeroBlender.package/blender.toolbox/get_scene_info.tool/init.luau
- ZeroBlender.package/blender.toolbox/get_viewport_screenshot.tool/init.luau
- ZeroBlender.package/blender.toolbox/replay_capture.tool/init.luau
- ZeroBlender.package/modules/animation.module/init.luau
- ZeroBlender.package/modules/bpy.module/init.luau
- ZeroBlender.package/modules/curves.module/init.luau
- ZeroBlender.package/modules/hardSurface.module/init.luau
- ZeroBlender.package/modules/kestrel.module/init.luau
- ZeroBlender.package/modules/meshEdit.module/init.luau
- ZeroBlender.package/modules/meshMods.module/init.luau
- ZeroBlender.package/modules/meshOps.module/init.luau
- ZeroBlender.package/modules/meshProxy.module/init.luau
- ZeroBlender.package/modules/polygonTopology.module/init.luau
- ZeroBlender.package/pyModule.assetType/behavior.luau
- ZeroBlender.package/zblend.assetType/behavior.luau
- modeling/references/parity/run.luau
8 files changed
- ChangedZeroBlender.packageFolderBeforeAfter
- ChangedZeroBlender.package/modules/blenderSession.moduleFolderBeforeAfter
- ChangedZeroBlender.package/modules/blenderSession.module/init.luau198 KB → 199 KBBeforeAfter
- ChangedZeroBlender.package/modules/meshBuf.moduleFolderBeforeAfter
- ChangedZeroBlender.package/modules/meshBuf.module/init.luau43.1 KB → 44.4 KBBeforeAfter
- ChangedZeroBlender.package/modules/pythonRuntime.moduleFolderBeforeAfter
- ChangedZeroBlender.package/modules/pythonRuntime.module/init.luau50.2 KB → 50.9 KBBeforeAfter
- ChangedZeroBlender.package/package.yaml341 B → 341 BBeforeAfter
Checks
No checks have been posted.
Reviews
No reviews yet.
Conversation
No comments yet.
Sign in to comment or review.