X-Particles with Octane in Cinema 4D: Particle Geometry, Trails, Motion Blur and Farm Rendering
Octane does not render X-Particles directly; it renders geometry you attach through an Octane Object tag. The points that decide whether particles show up and render the same on another machine:
- Tag placement: put the Octane Object tag on the xpEmitter first, then the Particle Group, then the xpGenerator
- Geometry mode: Geometry is the main Particle Rendering option; Voxel and SDF are not supported with X-Particles
- Colors: use the Instance Color node; trail colors come from the Attribute node
- Trails: render as hair, with fixed root and tip thickness and no motion blur
- Other machines: OTOY: only local networks render X-Particles directly; otherwise export Alembic
X-Particles and Octane are a common pair in Cinema 4D motion design, but the connection is indirect. Octane cannot read particles as such, so every particle has to be given geometry, and trails, colors and motion blur each follow their own rules.
This guide follows OTOY’s X-Particles page for Cinema 4D: where the Octane Object tag goes, how to get particle and trail colors into materials, what to do about motion blur, and how to render the scene on machines other than your own.
Checked against the OTOY OctaneRender for Cinema 4D manual and the OTOY forum, November 2026.
1. How does Octane render X-Particles?
OTOY states it plainly: OctaneRender does not render X-Particles directly, so Octane has to be given geometry for them. That is done through the Octane Object tag, typically with a sphere, though any geometry works, as long as it is light, because many particles consume a significant amount of VRAM (OTOY: X-Particles).
The tag goes on the xpEmitter, the xpGenerator or the Particle Group, depending on the setup. OTOY admits that finding the right one can take experimentation and suggests an order: start with the xpEmitter, then the Particle Group if present, then the xpGenerator. The page also lists X-Particles build 895 or newer as a requirement.
In the tag’s Particle Rendering tab, Geometry is the option to use: any Cinema 4D geometry can stand in for a particle. OTOY notes that the Voxel and SDF options are not supported with X-Particles.
2. Particle and trail colors
What works when X-Particles meet Octane
From the OTOY OctaneRender for Cinema 4D manual.
| Element | How Octane renders it | Limit |
|---|---|---|
| Particles | Octane Object tag › Particle Rendering › Geometry, with a small mesh | Many particles use a lot of VRAM; keep the mesh minimal |
| Particle colors | Instance Color node in the material on the particle geometry | Material on the geometry or on the emitter |
| Voxel / SDF modes | — | Not supported with X-Particles |
| Trails | xpTrails with an Octane Object tag in hair mode | Fixed root and tip thickness; no motion blur |
| Trail colors | Attribute node | — |
| xpOpenVDBMesher | Mesh generated on the fly for motion blur | xpCache does not write its motion blur data |
To match the colors set in X-Particles, put an Instance Color node in the material on the particle geometry. For trails, OTOY uses the Attribute node to pick up the trail color (OTOY: X-Particles). The Instance Color page walks through a full example with an xpEmitter, an Octane Object tag and a Platonic object as the particle (OTOY: Instance Color). The same node reads clone colors from MoGraph; see Octane MoGraph in Cinema 4D.
One small trap reported on the OTOY forum: a sphere with “Perfect Sphere” checked showed in the Live Viewer but not in the Picture Viewer, and unchecking it fixed the render (OTOY forum).
3. Trails as hair
Trails render through xpTrails with an Octane Object tag set to hair mode. OTOY lists two limits (OTOY: X-Particles):
- Trail thickness comes from the hair root and tip values, which are fixed, so trail width cannot follow individual particle size.
- Motion blur is not available on trails, because the point counts change from frame to frame.
If you need trails that vary in width or blur with motion, plan for that in compositing, or test a polygon-based trail setup on a few frames first.
4. Motion blur, caches and the OpenVDB mesher
OTOY’s page gives specific notes for motion blur on X-Particles meshes (OTOY: X-Particles):
- The xpCache does not write motion blur data for xpOpenVDBMesher output. Disable that generator’s cache so the mesh is generated on the fly.
- Enable Transfer Velocity on the xpOpenVDBMesher, then connect the velocity tags to the matching axis slots under Vertex Speed.
- Smoothing filters may affect motion blur data.
- Enable Use GUIDs on Motion Blur in the Octane Object tag if needed.
- If crashes occur, set M.Blur caches to 1 in the Octane Camera tag.
- The Live Viewer does not show motion blur accurately, so check it in a real render.
OTOY also notes that render times rise frame by frame as particles accumulate, so time a late frame, not frame 0.
5. Rendering an X-Particles scene on other machines
This is the point that affects farms most. OTOY states that only local networks, such as Team Render or Deadline, can render X-Particles directly; otherwise the system has to be exported as Alembic, which can greatly increase file sizes and transfer times (OTOY: X-Particles).
A remote workstation where you install the same Cinema 4D, X-Particles and Octane versions behaves like your own machine, so the scene can render without the Alembic step. For cache sync problems between particles and VDBs, see our guide to Octane particle and VDB cache desync.
Rendering X-Particles scenes on a render farm: SaaS or IaaS?
Choosing a farm type for X-Particles scenes
X-Particles is a third-party plugin; what matters is whether the render machine runs it.
| Situation | Usually a better fit | Why |
|---|---|---|
| Farm does not run X-Particles | Export Alembic first | OTOY: only local networks render X-Particles directly |
| Farm runs your X-Particles version | Either type | Check the build and the cache paths |
| You install your own plugins | IaaS (remote machine you control) | Same Cinema 4D, X-Particles and Octane as at home |
| Large caches | Plan the upload | Caches and Alembic files can be large |
Rule of thumb: the deciding question is whether the render machine runs your X-Particles version. If not, budget time for an Alembic export and a larger upload.
A test workflow on an iRender server
On iRender you rent a whole Windows workstation with Cinema 4D and OctaneRender installed, sign in with your own OTOY account, and install your own plugins with full administrator access:
- Upload the project and its X-Particles caches through iRender Drive.
- Install the same X-Particles version you use, with your license.
- Open the scene and check one late frame in the Live Viewer: particles, colors and trails.
- Render a few frames with motion blur in the Picture Viewer, since the Live Viewer does not show it accurately.
- Render the full range. Your image, software and settings stay saved for the next session.
X-Particles + Octane checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Can Octane render X-Particles directly?
No. OTOY states that Octane does not render X-Particles directly; you give each particle geometry through an Octane Object tag.
2. Where should the Octane Object tag go?
Start with the xpEmitter, then the Particle Group if present, then the xpGenerator. OTOY says finding the right one can take some experimentation.
3. Why are my particles white in Octane?
Use an Instance Color node in the material on the particle geometry to read the X-Particles colors.
4. Why do my trails have no motion blur?
Trails render as hair, and OTOY notes that motion blur is not available because their point counts change every frame.
5. Why do particles show in the Live Viewer but not in the final render?
One reported cause on the OTOY forum is Perfect Sphere being checked on the particle sphere. Uncheck it.
6. Can a render farm render my X-Particles scene?
OTOY says only local networks render X-Particles directly; otherwise export Alembic. A remote machine with the same plugins installed renders it like your workstation.
7. Does an X-Particles scene use every GPU?
Once the particles have geometry through the Octane Object tag, Octane renders them like any other mesh on every GPU enabled in Octane Settings > Devices. VRAM does not add up across cards (OTOY Devices tab), so a dense particle cache must fit on each card. 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 Octane particle and VDB cache desync.
Sources: OTOY: X-Particles (C4D), OTOY: Using X-Particles, OTOY: Instance Color, OTOY forum: particle sphere. Checked November 2026.




