octane-bridge
nobody · v2.4.0 · in useA Cinema 4D plugin that turns look development into a queryable library. Materials, HDRIs and render settings stop being files in a folder and become objects an agent can reason about.
On a booth project I rebuilt the same brushed-aluminium shader four times in three weeks, because the version I actually wanted was inside a scene file I had already archived. This plugin is the answer to that specific, stupid, expensive Tuesday.
- client
- nobody
- status
- in use
- version
- v2.4.0
- stack
- Python · c4d SDK · Octane
- runtime
- Python 3.11 / c4d 2025
- licence
- MIT
- v2.4.02026-06-14Batch chip rendering. Octane 2025.1 node coverage.
- v2.3.02026-04-02MCP tool surface. Library diffing between projects.
- v2.2.12026-02-19Fix — HDRI paths broke on network volumes.
- v2.0.02025-11-08Rewrite on the c4d 2025 API.
A rendered material library — the look-development records the plugin makes queryable.
Every material, HDRI and render preset in a project becomes a record in a local library with a stable identifier. Look development stops being a folder of scene files only I can navigate, and becomes something a teammate — or an agent — can query, diff and recombine.
A c4d plugin walks the document's material graph on save and writes a normalised JSON record per node, plus a rendered chip. An MCP server exposes the library as tools, so an agent can ask for the anodised aluminium from Vertical Field, two stops darker, and get back a material it can insert.