Cinema 4D MoGraph with Octane: Instance Modes, Clone Colors and VRAM
How a Cloner hands its clones to Octane decides memory, pre-processing time and whether colors work. What OTOY's own guides show:
- Instance mode: each clone becomes real polygons in VRAM; OTOY calls it right for several hundred to a few thousand copies
- Multi-Instance: the source geometry loads once; OTOY rendered 25 million light clones in about 8.8 GB on a 16 GB laptop GPU
- Trade-off: Multi-Instance cannot deform clones individually or offset their animation
- Clone colors: an OTOY forum expert says colors work once the Cloner uses Render Instance or Multi-Instance, not plain Instance
- Octane Scatter: Octane's own instancer, for millions of copies on a static surface
A MoGraph scene can look light in the viewport and still take minutes to prepare before Octane renders the first sample. Most of that comes down to one menu: the Cloner’s instance mode, which decides whether Octane receives thousands of copies of a mesh or one mesh and a list of positions.
This guide uses OTOY’s own Cinema 4D performance tests and documentation to show what each instance mode costs, how to keep clone colors working, and when to switch to Octane Scatter.
Checked against the OTOY help center, the OctaneRender for Cinema 4D manual, the Maxon Cinema 4D manual and the OTOY forum, November 2026.
1. Which Cloner instance mode should you use with Octane?
The Cloner and Instance objects in Cinema 4D have three instance modes. Maxon describes plain Instance clones as needing as much memory as if each clone existed as a separate object, and Multi-Instance as sharing the properties and restrictions of Render Instance (Maxon: Cloner object properties). For Octane, OTOY’s Cinema 4D performance guide compares them directly (OTOY help: 04 Instances).
Cinema 4D instance modes as seen by Octane
From OTOY's Cinema 4D performance guide and scene optimization page, and the OTOY forum.
| Mode | What Octane gets | Use it for |
|---|---|---|
| Instance | Each clone baked into real polygons and sent to VRAM | Hundreds to a few thousand clones; clones you deform or offset in time |
| Render Instance | Shared geometry; OTOY's optimization page says memory stays lower than Instance | A fallback; OTOY's performance guide skips it, and per-instance Octane tags have known limits |
| Multi-Instance | Source geometry loaded once; RAM set by the source object | Large counts; no per-clone deformation or time offset, no cloned lights or nulls |
| Octane Scatter | Octane's own instancer; loads one instance's geometry | Millions of copies on a static surface |
The OTOY sources do not fully agree on Render Instance. The performance guide says it “isn’t super useful for Octane” and leaves it out, while the scene optimization page suggests comparing Instance and Render Instance and says Render Instance memory will always be lower (OTOY: Scene Optimization). On the forum, a user reports that visibility set with Octane tags on render instances does not apply per instance (OTOY forum). In practice: Instance for small, editable systems, Multi-Instance for large ones, Render Instance only after a test.
2. What the modes cost: OTOY's measurements
OTOY tested both main modes on a 2021 laptop with an RTX 3080 Laptop GPU (16 GB), Cinema 4D 2023.1 and Octane 2022.1. With 30,000 single-polygon clones, Instance mode used about 3.7 MB of Cinema 4D RAM and about 18.5 MB of Octane geometry; Multi-Instance used about 1 KB and about 14.5 MB, and Octane reported one triangle instead of 30,000 (OTOY help: 04 Instances).
The difference grows with count. In Instance mode the guide reports about 40 seconds of pre-processing at 30,000 hidden clones and about 6 more minutes at 100,000. With Multi-Instance, it reached 10 million clones with about 20 seconds of pre-processing and 3.5 GB of VRAM, and 25 million with about 8.8 GB, before 30 million ran out of VRAM.
These are OTOY’s numbers for very light test geometry on one laptop. Real assets with more polygons and textures use more memory per clone, so measure your own scene on its heaviest frame.
Instance vs Multi-Instance at 30,000 single-polygon clones
Measured by OTOY on a 2021 laptop with Cinema 4D 2023.1 and Octane 2022.1.
| Measure | Instance | Multi-Instance |
|---|---|---|
| Cinema 4D RAM | about 3.7 MB | about 1 KB |
| Octane geometry | about 18.5 MB | about 14.5 MB |
| Triangles Octane reports | 30,000 | 1 |
What Multi-Instance gives up, according to the same guide: clones can no longer be deformed individually or have their keyframes offset, UV-based texturing becomes harder, and lights and nulls cannot be cloned.
3. Keeping clone colors and IDs
Octane reads MoGraph data through its Instance Color and Instance Range nodes, and the Cinema 4D MoGraph Color Shader can drive a material on a Cloner (OTOY: Instance Color). If colors from a Random or Shader Effector do not show, check the instance mode first: an OTOY forum expert explains that this works once the Cloner uses Render Instance or Multi-Instance instead of plain Instance, and a reply in the same thread points out that those modes do not work with every Cinema 4D feature (OTOY forum).
- Effector colors: Instance Color node in the material, Cloner in Render Instance or Multi-Instance.
- Per-object IDs: set an Instance ID in the Octane Object Tag and read it with Instance Range (OTOY: Octane Object Tag).
- Test one frame in the Live Viewer after changing the mode.
4. When to use Octane Scatter instead
Octane Scatter is Octane’s own instancer. OTOY’s guide reports that in Object mode it still loads only one instance’s geometry into VRAM, and that it built 25 million instances on the same laptop with about 9.9 GB of VRAM (OTOY help: 04 Instances). Two limits from the manual: For particles rather than clones, see X-Particles with Octane in Cinema 4D.
- Octane Scatter does not work with animated surfaces as the target object (OTOY: Octane Scatter distribution).
- All scattered objects still have to fit in VRAM. OTOY adds that generators consume VRAM, and that the Cinema 4D Matrix object is the most efficient cloner outside Octane Scatter (OTOY: Scatter VRAM considerations).
For a deeper look at scatter memory and preparation time, see our guide to OctaneScatter in Cinema 4D.
Rendering heavy MoGraph scenes on a render farm: SaaS or IaaS?
Choosing a farm type for MoGraph scenes
Instance modes are saved in the scene; what changes is how much memory and preparation time each frame needs.
| Situation | Usually a better fit | Why |
|---|---|---|
| Scene renders well at home | Either type | Same plugin version, same instance modes |
| Still testing Instance vs Multi-Instance | IaaS (remote machine you control) | You can switch modes and read memory in the Live Viewer on the render machine |
| Long pre-processing per frame | Measure before choosing | Preparation runs on the CPU before the GPUs start |
| Close to the VRAM limit | IaaS with 32 GB cards | Each GPU holds the scene; more cards add speed, not memory |
Rule of thumb: if the scene already fits and renders at home, either type works. If you still need to trade instance modes against memory, a machine you can open saves failed jobs.
A test workflow on an iRender server
On iRender you rent a whole Windows workstation with Cinema 4D and OctaneRender installed, and sign in with your own OTOY account:
- Upload the project through iRender Drive, with any MoGraph caches.
- Start a 1x, 2x, 4x or 8x RTX 5090 server (32 GB per card).
- Open the heaviest frame and read geometry memory in the Live Viewer.
- Switch large Cloners to Multi-Instance if colors and animation allow, and compare.
- Render the full range. Your image, software and settings stay saved for the next session.
Octane MoGraph checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Which Cloner instance mode is best for Octane?
For a few thousand clones, Instance mode is fine. For large counts, OTOY’s guide shows Multi-Instance loading the source geometry once, with far less memory and pre-processing.
2. Does Octane support Render Instance?
It renders, but OTOY’s performance guide skips it as not very useful for Octane, and the forum reports per-instance Octane tag limits. Test it before relying on it.
3. Why do my MoGraph colors not show in Octane?
Use the Instance Color node and set the Cloner to Render Instance or Multi-Instance; an OTOY forum expert notes it does not work in plain Instance mode.
4. How many clones can Octane render?
In OTOY’s laptop test with light geometry, Multi-Instance reached 25 million clones in about 8.8 GB of VRAM; 30 million ran out of VRAM. Real assets use more.
5. What does Multi-Instance give up?
Per-clone deformation and keyframe offsets, easy UV texturing, and cloning lights or nulls.
6. When should I use Octane Scatter?
For millions of copies on a static surface. It does not work with animated target surfaces.
7. Can more GPUs render more clones?
More GPUs render faster, not bigger. VRAM does not add up across cards, so the card with the least VRAM sets how many clones fit (OTOY Devices tab). To fit more, use Multi-Instance or Octane Scatter, or a card with more VRAM (an RTX 5090 has 32 GB). See Octane multi-GPU rendering in Cinema 4D.
Render your Cinema 4D and Octane projects on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 or RTX 5090 GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. Cinema 4D and OctaneRender are installed; sign in with your own OTOY account (OTOY’s Studio+ plan has no GPU limit for multi-GPU servers). Your server image is saved between sessions.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load, so they keep their boost clocks. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start Cinema 4D and Octane on an iRender server:
On a 4x RTX 5090 server, a 300-frame Cinema 4D + Octane animation rendered in 1 hour 18 minutes. The second clip runs the same kind of scene on 4x RTX 5090 and 4x RTX 4090:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Octane render farm page, download the iRender GPU app, or read OctaneScatter in Cinema 4D.




