November 17, 2026 Kath Nguyen

Cinema 4D Particle Flow on a Moving Surface: Jiggle Deformer and Redshift Matrix (2026)

Executive SummaryExecutive Summary: particle flow on a moving flag
Cinema 4D 2024.4+

A flow of particles that follows every ripple of a waving flag can be built entirely with Cinema 4D’s particle system, a Jiggle deformer and a few field conditions, with no third-party plugin. The finishing detail is scattered with a Redshift Matrix.

  • Flag: a Plane with enough segments, a Jiggle deformer driven by Turbulence and Wind forces, and a Smoothing deformer.
  • Emission: a Vertex Map on the flag and a Mesh Emitter that follows it, coloured from the flag image with a Shader Field.
  • Keep forces apart: particle forces go in their own subgroup, or the flag’s wind pushes the flow off course.
  • Stay on the surface: Surface Attract plus a Collider tag on the flag; field conditions remove strays and add colour variation.
  • Scatter and render: a Redshift Matrix on a polygon selection, rendered in Redshift on one or several GPUs.

Cinema 4D’s particle system makes a flow that follows a moving surface much easier than it used to be. This guide follows our tutorial, where particles run along a flag as it waves in the wind, and explains what each object does, why the order matters and where the setup usually goes wrong.

The build has five stages: animate the flag, emit particles from it, shape how they move, clean up the result, and scatter render-ready elements with a Redshift Matrix.

Checked against the Maxon Cinema 4D help pages for the particle system, Mesh Emitter, Surface Attract, the Jiggle deformer and Redshift Matrix Scatter, November 2026.

The full tutorial runs 15:53, from building the flag mesh to fine-tuning the final scatter. The steps below follow the same order.

What you need before you start

The setup uses the particle system Maxon introduced in Cinema 4D 2024.4. Maxon’s introduction notes that the new system handles much larger particle counts, can run on the GPU, and is built around Groups, Conditions and Modifiers that you find in the Simulate menu (Maxon: Particle Simulations – An Introduction). On older versions these objects are not available. The scatter at the end uses Redshift, which ships with Cinema 4D.

What the finished setup does

The figure below shows the finished scene and where each part of the build acts. The sections after it build it step by step.

iRender
Particle flow on a waving flag: what each part does
Schematic
windPoleCapsule objectFlow from the poleMesh Emitter on a Vertex MapRS Matrixon a polygon selectionBox Fieldstrays killedFree edgemoves most (Jiggle)
particles on the surfaceRedshift Matrix scatterBox Field condition
Schematic of the tutorial scene, not a render

How to read the figure. The flag hangs from the pole and waves in the wind; the free edge on the right moves most, because a Linear Field limits the Jiggle deformer near the pole. The coloured dots are particles: they are born on a Vertex Map and flow from the pole toward the free edge while staying on the surface. The dashed red box is the Box Field condition: particles that leave it are killed. The green shapes are the Redshift Matrix scatter, limited to one polygon selection on the flag.

1. Build the flag that moves in the wind

  1. Material. Create a standard material and load the flag image into its Color channel. You will reuse it later to colour the particles.
  2. Plane. Raise the Width and Height segments so the plane has enough points to bend like cloth.
  3. Jiggle deformer on the plane, then add a Turbulence force to it. Maxon documents that particle modifiers can be dragged into the Jiggle deformer’s Forces list to drive the secondary motion (Maxon: Jiggle forces).
  4. Springs. Tune the Springs value inside Jiggle. Maxon notes that Springs set to zero lets the forces deform the mesh at full strength without any jiggle effect (Maxon: Jiggle properties).
  5. Linear Field linked to the Jiggle deformer to control which area moves: the side near the pole stays calm, the free edge moves most.
  6. Smoothing deformer on top so the motion reads as cloth, not noise.
  7. Pole and wind. Model the pole from a Capsule object and add a Wind force to the Jiggle forces as well.

2. Emit particles from a Vertex Map

  1. Vertex Map on the flag to paint where particles are born.
  2. Mesh Emitter with its distribution set to follow that Vertex Map. Maxon describes the Mesh Emitter as emitting from the points, surface or volume of any geometry, restrictable with selections and maps (Maxon: Mesh Emitter).
  3. Direction. Set the movement along the X axis so the flow starts at the pole and travels toward the far edge.
  4. Colour. Create a Vertex Color map and apply a Shader Field that uses the same flag material, so each particle picks up the colour of the image where it is born.

3. Keep flag forces and particle forces apart

When you press play at this point, the flow does not go where you set it. The particles are being pushed by the same dynamic forces you added for the flag.

iRender
Why the particle flow drifts, and the fix
Schematic
Forces shared: flow blown off the flagForces split: flow stays on the flagTurbulence and Wind also push the particlesParticle forces moved to their own subgroup
particles pushed offparticles on the surface
Schematic of the fix shown in the tutorial

How to read the figure. On the left, the Turbulence and Wind meant for the flag also reach the particles, so they lift off the surface and drift with the wind, most of all near the free edge. On the right, the flag forces stay inside the Jiggle deformer and the particle forces sit in their own particle subgroup, so the particles stay on the waving surface. The fix in the tutorial is exactly that: create a separate particle group and move the forces into it as a subgroup.

iRender
Where each force belongs
Schematic
Object ManagerCapsule — polePlane — flag (more W/H segments)VCMC1Jiggle (Springs tuned)1Smoothing1Linear Field → Jiggle1Turbulence + Wind (flag only)in Jiggle Forces3Mesh Emitter2Particle Group — Flow3Data Mapper4Flock4Surface Attract4Turbulence (particles)4Field Condition (Box) — kill strays5Mesh Emitter › EmissionGeometryPlane — flag2Distributionby Vertex Map2Directionalong +X (pole → edge)2Jiggle › ForcesForce 1Turbulence3Force 2Wind3FalloffLinear Field1Collider tag (on flag)Used bySurface Attract4Rule: flag forces live in the Jiggle Forces list,particle forces live inside the particle group.
badge = step number in this guideemitter and particle group
Layout reconstructed from the steps in the video

How to read the figure. Most problems in this setup come from forces in the wrong place. Keep Turbulence and Wind for the flag in the Jiggle deformer’s Forces list (steps 1 and 3), and put every modifier meant for the particles inside the particle group (step 4), so each set only touches what it should. The badges match the steps above.

4. Shape the motion and stick to the surface

  • Data Mapper to control how particle velocity and lifetime change over time.
  • Flock modifier to keep natural spacing between particles.
  • Surface Attract modifier plus a Collider tag on the flag, so the modifier knows which surface to follow. Maxon describes Surface Attract as pulling particles toward dynamic object surfaces, deflecting or capturing them (Maxon: Surface Attract). It works within a Radius layer around the surface and does not do direct collision detection, so a few particles can still pass through; keep that in mind when you judge a test frame.
  • One more Turbulence force on the particles to make the motion feel less mechanical.

5. Clean up with field conditions

  • Remove strays. A Field Condition with a Box Field kills particles that drift too far from the surface.
  • Colour variation. A second Field Condition that combines a Random Field with a Linear Field gives the flow a controlled, random colour change instead of a uniform colour.

Conditions are cheaper than trying to tune forces until no particle ever escapes: let the forces do most of the work and remove the few that misbehave.

6. Scatter detail with a Redshift Matrix

  1. Create a new Vertex Map, apply the Shader Field to it, and use the result to make a polygon selection on the flag.
  2. Create a Redshift Matrix scattered on the flag and restricted to that polygon selection.
  3. Add a Scale Field with a Plain Effector to the Redshift Matrix to control the size of each element across the flag.

Maxon describes Redshift Matrix Scatter as a MoGraph Matrix object with a Redshift Object tag, so Redshift renders the matrix points directly with the shapes or objects you assign, without building the geometry in the scene first (Maxon: Redshift Matrix Scatter). That keeps the viewport light even with many scattered elements.

Render the particle flow on several GPUs

Particle scenes get heavy on the render side as well as in the simulation. Before a long render:

  • Cache the particles so every frame, and every machine if you split the frame range, sees the same simulation.
  • Check VRAM per card. Redshift can render on all GPUs in a machine, but each card holds its own copy of the scene; memory is not combined (Maxon support).
  • Test one frame first. The tutorial’s final shot was rendered on a multi-GPU RTX 4090 server; time one frame on your target server before you commit the full range.

Particle flow checklist

Use this list to check the scene before you cache it and send it to render.

ChecklistParticle flow checklist
0 / 10 done
Tip: Tick the items as you check the scene. The ticks reset when you reload the page.

SaaS or IaaS render farm for particle flow scenes?

Both farm models render the same frames if the particle simulation is cached with the scene. The difference is how you handle a cache that is large or not final yet, and how fast you can react when a test frame shows particles drifting off the flag.

Farm modelFor this task

SaaS or IaaS for particle scenes

How each farm model fits a Cinema 4D particle scene with a Redshift Matrix scatter.

Your situationSaaS render farmIaaS render farm (iRender)
The particle cache is final and approved on your PCA good fit: upload the scene and cache, the farm renders the framesWorks too; you open the scene on the server and render it yourself
You still need to adjust Surface Attract or the field conditionsEach change means fixing it locally, re-caching, uploading again and resubmittingChange the setting on the server, re-simulate and render a test frame there
The cache is large and you want to simulate on the render machineThe farm renders what you upload; simulating there depends on its workflowSimulate and cache on the server, then render from the same drive
You have a deadline and need to know when rendering starts and endsJobs join the farm’s queue, so the start time depends on how busy the farm is; many farms sell higher-priority plans to start soonerThe server runs only your job from the moment it boots, so you control when rendering starts and can time the whole job
Note: A comparison of how the two farm models work for this task, not a speed test.

Simple rule: if the particle cache is final and travels with the scene, a SaaS farm saves you the machine work. If you are still tuning the flow, or the cache is easier to build on the render machine, a server you control is the better fit.

A test workflow on an iRender server

iRender
Works 1:1 like your own PC: we keep your setup, you just get more GPUs
IaaS render farm
Your workstationscene.c4d · .blend · .hip1 GPUYour iRender serverscene.c4d · .blend · .hipup to 8 GPUs=same setupWindows or Ubuntu desktopYour software, in the version you chooseYour plugins and scriptsYour licensesYour scene and render settings, unchanged1 GPUGPU power: the only difference1, 2, 4 or 8 × RTX 5090 / 4090✓ Only the GPU count changes: open your scene and render the way you do at home
Same on both machinesTip: upload the full project folder with relative paths so textures are found
  1. Upload first. Put the .c4d file, the flag image and any particle cache on iRender Drive before you start a server; transfer and storage are free.
  2. Pick a server. Cinema 4D and Redshift are pre-installed. Use a 1x server to check the simulation and a 4x or 8x RTX 4090 or RTX 5090 server for the final frames.
  3. Cache on the server. Play the simulation and cache it if you have not done so on your PC.
  4. Render a test frame. Check the Redshift log for all GPUs and look at the scatter at final resolution.
  5. Render the shot. Save frames to iRender Drive and shut the server down when the job is done; multi-GPU servers are billed per minute.

Frequently asked questions

1. How do you make particles follow a moving surface in Cinema 4D?

Use the Surface Attract modifier from the particle system and put a Collider tag on the moving surface. Emit the particles from the surface with a Mesh Emitter, and keep a Turbulence force light so they do not leave the surface.

2. Which Cinema 4D version has this particle system?

The particle system with Mesh Emitter, Groups, Conditions and Modifiers was introduced in Cinema 4D 2024.4. Older versions only have the legacy emitter and Thinking Particles.

3. Why do my particles drift in the wind direction?

The forces you added for the flag are also acting on the particles. Keep the flag forces in the Jiggle deformer’s Forces list and move the particle forces into a separate particle subgroup.

4. How do I control where particles are emitted?

Paint a Vertex Map on the surface and set the Mesh Emitter distribution to follow it. Only the painted area emits particles.

5. How do the particles get the colour of the flag image?

Create a Vertex Color map and apply a Shader Field that uses the same material as the flag, so each particle takes the colour of the image where it is born.

6. What is a Redshift Matrix and why use it here?

It is a MoGraph Matrix object with a Redshift Object tag. Redshift renders the matrix points directly with the shapes you assign, so you can scatter many elements on the flag without heavy geometry in the viewport.

7. Do I need a plugin such as X-Particles for this effect?

No. The whole setup uses Cinema 4D’s own particle system, deformers and fields, plus Redshift for the scatter.

Render your Cinema 4D and Redshift 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 (24 GB) or RTX 5090 (32 GB) 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 Redshift are pre-installed, and 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. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.

Two recorded Redshift runs on iRender servers:

New users get a 100% bonus on the first top-up (minimum $50). See plans on the Cinema 4D and Redshift render farm page or download the iRender GPU app.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, , , , , , ,

Kath Nguyen

Kath Nguyen works in customer support at iRender, helping artists move Blender and Cinema 4D projects to multi-GPU servers. She has written more than 140 articles for the iRender blog.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →