Octane Scatter vs Cinema 4D Cloner (2026): Multi-Instance, Scatter Settings and Millions of Instances
Grass, rocks, crowds of props: whether Octane loads one copy of the geometry or every copy depends on how you clone. OTOY's documentation and its instancing guide show where each method fits.
- Cloner in Instance mode. Each copy becomes real geometry for Octane; good for a few hundred to a few thousand copies you edit one by one.
- Cloner in Multi-Instance mode. OTOY: Octane does true instancing for multi-instance cloners; per-clone deformation and animation offsets are not available.
- Octane Scatter. A native Octane object for millions of instances, referenced efficiently on the GPU.
- Static only. Octane Scatter does not work with animated surfaces as the target and does not animate scattered objects.
- Not unlimited. OTOY's guide hit 9.9 GB of VRAM at 25 million instances and ran out of VRAM at 30 million.
Large environments in Cinema 4D usually come down to one choice: a MoGraph Cloner or the Octane Scatter object. Both place copies of an object on a surface, but they hand very different amounts of data to Octane. This guide follows OTOY’s Octane for Cinema 4D documentation and OTOY’s own instancing guide.
Checked against the OTOY documentation, November 2026.
1. Cloner or Octane Scatter: which should you use?
OTOY describes Octane Scatter as a simpler version of the MoGraph Cloner that distributes a source object over a target, typically faster and with less resource use (OTOY: Native Octane Geometry). The Cloner’s mode matters just as much. In OTOY’s instancing guide, Instance mode turns every copy into real geometry, while Multi-Instance lets Octane instance the copies.
How to read the figure. Compare the three methods property by property: what Octane loads, the count range OTOY gives, whether each copy can deform or animate, and effector support. Cloner in Instance mode gives Octane geometry for every copy, while Multi-Instance and Octane Scatter load one copy per source, which is why they reach much larger counts. The line at the bottom sums up the choice.
OTOY’s guide also skips the Cloner’s Render Instance mode, noting it is not very useful for Octane. Its recommendation: Instance mode for a few hundred to a few thousand copies that need individual edits, Multi-Instance for very large counts without per-copy changes, and Octane Scatter for millions.
2. What OTOY measured
OTOY’s instancing guide ran the methods side by side on its own test scenes. The figures below are OTOY’s, not iRender measurements, and they depend on the source object and hardware, but they show the scale of the difference.
| Test in OTOY's guide | Result reported |
|---|---|
| 30,000 clones, Instance mode | Octane triangle count matched the 30,000 copies; about 18.5 MB of geometry |
| 30,000 clones, Multi-Instance | Triangle readout dropped to one; about 14.5 MB of geometry |
| 100,000 hidden clones, Instance mode | Single-digit viewport FPS and about six minutes of pre-render processing |
| 25 million instances, Octane Scatter | About 9.9 GB VRAM, 48 GB peak RAM, 3:10 build time |
| 30 million instances, Octane Scatter | Render ran out of VRAM |
Source: OTOY Help Center, 04: Instances (Cinema 4D).
The last two rows matter for planning: instancing saves a great deal of memory, but millions of instances still fill VRAM and system RAM. Our servers have 32 GB of VRAM per RTX 5090, 24 GB per RTX 4090, and 256 GB of RAM. VRAM is not pooled across GPUs, so each GPU must hold the whole scene.
3. How to set up Octane Scatter (step by step)
- Create the object: Live Viewer menu › Objects › Octane Scatter (OTOY: Objects menu). It appears in the Object Manager.
- Parent the sources: put the objects to scatter as children of Octane Scatter. Several children are allowed; any parametric or geometric object can be cloned, but lights and cameras are not.
- Set the Surface: in the Distribution tab, drag the target object into the Surface field. OTOY’s guide notes Surface can take a polygon object, particles or a Matrix, with Surface or Vertex distribution.
- Set Count and Seed, then scale, rotation and normal alignment (OTOY: Distribution settings). Keep the source objects as light as possible; OTOY notes high-polygon sources slow Scatter down.
- Set the Display tab so the viewport stays responsive (OTOY: Display settings): a simple Display Type and a low Display Rate for very large counts.
- Add effectors by hand if needed: drag MoGraph effectors into the Effectors tab list. Unlike Cloners, Scatter does not assign them automatically (OTOY: Effector usage).
How to read the figure. The badges follow the numbered steps above. Badge 1 is the Octane Scatter entry in the Live Viewer Objects menu, badge 2 marks a source object placed under Octane Scatter in the Object Manager, badges 3 and 4 are the Surface and Count fields in the Distribution tab, badge 5 is the Display Type in the Display tab and badge 6 is the Effectors tab list. Each orange outline marks the setting to change.
How to read the figure. Follow the setup from the Object Manager to GPU memory. The pine and the rock are children of Octane Scatter and become its sources. The Distribution tab sets the static surface, the count and seed, and scale or rotation variation from Cinema 4D CPU shaders. Display Rate and the Effectors list control the viewport and effectors. At render each GPU holds one copy of each source, and the instances add only position, rotation and scale.
One detail that catches many users: do not use Octane textures, such as Octane noise or turbulence, in Scatter’s scale or rotation fields. OTOY explains that Octane textures are GPU shaders, while Octane Scatter works with Cinema 4D’s CPU shaders only. Use Cinema 4D’s own noise shaders there.
4. Variation: instance color and effectors
Identical copies are what make instancing cheap, so variation comes from transforms and from color at render time. OTOY’s Instance Color tutorial drags the Octane Scatter object into an Instance Color node’s color source, then maps it through an Octane Gradient, to tint millions of instances without new geometry. A Random Effector in the Scatter’s Effectors list adds position, scale and rotation variation.
5. Why is my scatter slow, empty or wrong?
How to read the figure. Each symptom is paired with its first fix: an animated surface that is ignored needs a Cloner in Instance mode, a crawling viewport needs the Simple display type and a low Display Rate, out of VRAM at render means fewer instances or lighter sources, ignored random scale needs Cinema 4D CPU shaders instead of Octane textures, and an effector with no effect has to be dragged into the Effectors tab list.
Nesting is limited too. On the OTOY forum, the Octane for Cinema 4D developer explains that only plain geometry should go under a Scatter object, and that render instances cannot be used there.
6. Rendering heavy scattered scenes on multi-GPU servers
Because each GPU holds its own copy of the scene, a scatter that fits in one GPU’s VRAM renders on every GPU of the server, and more GPUs share the samples. The build time OTOY measured, more than three minutes at 25 million instances, happens before sampling starts, so check it on a test frame.
We have not timed a scatter-heavy scene on our servers yet, so this section gives no specific figure. The table lists Cinema 4D + Octane runs recorded in iRender videos.
Octane runs measured on iRender servers
| Test scene | Server | Frames | Render time | Cost at list price | Video |
|---|---|---|---|---|---|
| Car drift scene1080p, 800 max samples | 5i 4x RTX 5090 | 300 | 1h 18m 24s · 15.6 s/frame | ~$49.65 | Watch the test |
| Car drift scenesame scene and settings | 5S 4x RTX 4090 | 300 | 18.8 s/frame (about 1h 34m) | ~$47 (estimated from s/frame) | Watch the test |
| Cinema 4D animation1080p | 9S 8x RTX 4090 | 320 | 1h 02m render · 1h 16m session billed | ~$65.87 | Watch the test |
| Sailboat animation1080p | 5i 4x RTX 5090 | 120 | 2h 01m | ~$76.63 | Watch the test |
The rows are different scenes and do not rank the servers. Render one frame of your scattered scene to see its build time and VRAM use before rendering the sequence.
SaaS or IaaS render farm for an Octane Scatter scene?
Both farm models can render an Octane scene. The difference is how much of the setup you can see and change when a scatter-heavy scene is close to the GPU memory of one card, because each GPU holds the full scene.
Rendering a scatter-heavy Octane scene on a farm
How the two farm models fit depending on how ready the scene is.
| Your situation | SaaS render farm | IaaS render farm (iRender) |
|---|---|---|
| The scene is final and fits comfortably in GPU memory | A good fit: upload and the farm renders the frames across its nodes | Works as well: open the scene and render on 2x to 8x GPUs |
| Instance counts are close to the VRAM of one GPU | Check the GPU memory of the farm’s nodes before you submit | Render a test frame on the exact server and watch VRAM use in Octane |
| You may need to change counts, sources or Display Rate | Changes usually mean a new upload and a new job | Change the scene on the server and render again |
A test workflow for scattered scenes on an iRender server
How to read the figure. The top row is the setup: your own PC or Mac connects by remote desktop to a whole bare-metal server with 1, 2, 4 or 8 GPUs, so you open your Cinema 4D and Octane project there exactly as at home. The numbered row is the order of a session: register and top up, upload to iRender Drive before the server runs, start and connect, render a test frame and the job, then shut down so billing stops.
- Upload the project, source models and textures to iRender Drive before you start the server, so upload time is not billed.
- Start a 4x or 8x RTX 5090 server (packages 5i or 9i); multi-GPU servers are billed per minute. Cinema 4D and OctaneRender are pre-installed; sign in with your own OTOY account. OTOY’s Studio+ plan has no GPU limit.
- Lower the Display Rate before opening the scene so the viewport loads quickly.
- Render one frame and watch the build time and VRAM use in Octane.
- Render the sequence; split long frame ranges across several servers.
Frequently asked questions
1. Is Octane Scatter better than the Cinema 4D Cloner?
For large static sets, OTOY describes Octane Scatter as typically faster and lighter than a MoGraph Cloner. For copies that need individual edits, deformation or animation offsets, a Cloner in Instance mode is the right tool.
2. Does Octane instance Cinema 4D Cloner copies?
In Multi-Instance mode, yes: OTOY says Octane does true instancing for multi-instance cloners. In Instance mode each copy becomes real geometry for Octane.
3. Can Octane Scatter work on an animated surface?
No. OTOY states Octane Scatter does not work with animated surfaces as the target, and objects scattered with it are not animated.
4. Why does Octane noise not work in Octane Scatter?
Octane textures are GPU shaders, while Octane Scatter works with Cinema 4D CPU shaders only. Use Cinema 4D noise in the scale and rotation fields.
5. How many instances can Octane Scatter handle?
OTOY’s guide reached 25 million instances at about 9.9 GB of VRAM and ran out of VRAM at 30 million. The real limit depends on the source objects and the GPU memory.
6. Why does my effector not affect Octane Scatter?
Unlike MoGraph Cloners, Octane Scatter does not assign effectors automatically. Drag the effector into the Effectors tab list.
7. Can I render Octane Scatter scenes on iRender?
Yes. Cinema 4D and OctaneRender are pre-installed on iRender servers with 1 to 8 RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs and 256 GB of RAM; sign in with your own OTOY account.
Render your Cinema 4D + Octane scattered scenes 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, connect by remote desktop and work on it like your own workstation.
- Multi-GPU servers: 1x to 8x RTX 4090 (24 GB) or RTX 5090 (32 GB), AMD Threadripper PRO CPUs, 256 GB ECC RAM and 2 TB NVMe SSD.
- Octane ready: OctaneRender is installed on the servers; you sign in with your own OTOY account and open your project in Cinema 4D as usual. Your server image is saved between sessions, and the physical machine is fully wiped before anyone else uses it.
- Pay for what you use: billed per minute (1-hour minimum on single-GPU servers), with 10% off sessions of 3 hours or more. See pricing.
- Elite Support, 7 days a week: by hotline, live chat, Skype, WhatsApp and email.
The quickstart below shows how to render a Cinema 4D + Octane project on an iRender server, from uploading the files to downloading the frames.
Two iRender tests show what the 4-GPU servers do with a Cinema 4D + Octane animation. In the first, 4x RTX 5090 rendered 300 frames in 1 h 18 min; the second compares 4x RTX 5090 with 4x RTX 4090 on the same scene.
New accounts get a 100% bonus on the first top-up (minimum $50). See the Octane render farm page for server options, or download the iRender GPU app.
Sources: OTOY Help Center: 04: Instances, OTOY: Native Octane Geometry (Cinema 4D), OTOY: Objects menu (Cinema 4D), OTOY: Octane Scatter Distribution settings, OTOY: Octane Scatter Display settings, OTOY: Effector usage with Octane Scatter, OTOY: Instance Color (Cinema 4D), OTOY forum: Octane Scatter nesting.




