Blender & Cinema 4D Bridges

Both DCC hosts share the same _AI pattern as Creo/Minecraft: strategy profiles, dry-run, recipes, BridgeManager adapters, and Plugin SDK façades. Offline mock scenes work without installing Blender or Cinema 4D.

Related: PluginBridges.md · CreoIntegration.md

Blender (blender / blenderkit)

Profiles

Commands (excerpt)

blender status|doctor|profiles|selftest
blender profile template|interactive|headless|file|advanced
blender bridge start|stop
blender create cube Product | material Product metal
blender gn set Product Count 24
blender render | preview | export glb path
blender recipe run turntable_product
blenderkit status|recipe turntable_product
bridge start blender

Env

AI_BLENDER_PROFILE, AI_BLENDER_API (mock default), AI_BLENDER_HOST/PORT (8775), AI_BLENDER_TOKEN, AI_BLENDER_WORKDIR, AI_BLENDER_WORKER, AI_BLENDER_EXE, AI_BLENDER_DRY_RUN

Worker: python tools/blender_worker/blender_worker.py --port 8775

Recipes: turntable_product, logo_3d, gn_chart, game_prop_export, lookdev_sphere, math_field, scene_qa

Cinema 4D (c4d / cinema4d / c4dkit)

Profiles

Commands (excerpt)

c4d status|doctor|profiles|selftest
c4d profile template|live|batch|file|sdk
c4d bridge start|stop
c4d create cube Hero | material Hero metal
c4d userdata set Cloner Count 4,4,1
c4d frames 0 120 30 | render | preview
c4d export fbx path
c4d recipe run product_turntable
c4dkit status|recipe motion_graphics_lower_third
bridge start c4d

Env

AI_C4D_PROFILE, AI_C4D_API (mock default), AI_C4D_HOST/PORT (8776), AI_C4D_TOKEN, AI_C4D_WORKDIR, AI_C4D_WORKER, AI_C4D_EXE, AI_C4D_DRY_RUN

Worker: python tools/c4d_worker/c4d_worker.py --port 8776

Recipes: motion_graphics_lower_third, product_turntable, cloner_grid, broadcast_pack, redshift_lookdev, game_export_fbx, scene_qa

Files

Rebuild the VS solution after pull so new .cpp files link.

Application brainstorm (how to use them)

Creative production

1. Product hero stills — Blender turntable_product or C4D product_turntable → dry-run preview → export GLB/FBX → Adobe polish → O365 mail pack.
2. Motion graphics / broadcast — C4D lower-thirds + cloner grids driven by user-data titles from LLM/brief.
3. Lookdev — Blender lookdev_sphere / C4D redshift_lookdev for material boards.
4. Logo extrusion — Blender logo_3d from brand SVG import path (file profile).

Games & engines

5. Prop pipeline — game_prop_export / game_export_fbx into Minecraft/SE/Unreal content folders.
6. LOD batch — headless/batch profile: import mesh, decimate recipe (future), multi-export.
7. Kitbash library — file profile watch-folder: drop models → semantic_vectors index → place in scene.

Science / engineering (your stack)

8. Math fields — ODE/calc samples → Blender math_field / GN chart stills for papers.
9. Creo → DCC — Creo STEP export → Blender/C4D import → lookdev still (multi-bridge graph).
10. Chart automation — CSV/JSON → gn_chart / cloner counts → PNG for PowerPoint.

Agent / LLM patterns

11. Scene co-pilot — context JSON into grounded chat: “what’s selected? fix lighting.”
12. Recipe picker — LLM chooses recipe + params; host enforces allowlists (template profile).
13. Scene QA — scene_qa checklist before client delivery.
14. Approval bus — dry-run render markers → human dry-run off + re-run.

Studio ops

15. Overnight farm — headless/batch jobs queued from _AI CommandQueue.
16. Dual DCC — same brief: Blender for assets, C4D for motion graphics package.
17. ImGui dashboard — show both bridges’ metrics (renders, exports, profile).
18. Teaching / replay — log actions as recipes (parallel to Minecraft teaching).

Cross-app graphs (high value)

Brief (chat)
  → c4d recipe motion_graphics_lower_third Title=...
  → blender recipe turntable_product
  → creo export step (optional CAD)
  → adobe / office handoff (future)
  → semantic index of outputs

Safety defaults

• Prefer template profiles for agents.
• Keep dry-run on until previews look right.
• Do not free-exec bpy/c4d Python from the LLM; only allowlisted verbs + recipes.
• Tokens stay in _AI; workers stay local.

Live app next steps

1. Blender: package blender_addon/ai_bridge that speaks the same JSON verbs.
2. C4D: Script Manager / Python plugin or c4dpy runner using c4d_worker protocol.
3. Set AI_BLENDER_EXE / AI_C4D_EXE + worker paths; switch profile to interactive/live.