November 7, 2026 Kath Nguyen

Painting in Motion in Cinema 4D: Two Particle Methods, Step by Step (2026)

Executive SummaryExecutive Summary: painting in motion
Cinema 4D 2025+

A famous painting can be turned into a moving field of coloured particles in Cinema 4D in two ways: with a Particle Node Modifier that samples the image by UV and steers particles through a flow field, or with the Particles system, a Volume Builder and a Field Force masked by the image brightness.

  • Method 1 base: a Plane, a Mesh Emitter at 5,000 particles per frame with Normal and UVW output, Flock, Collider cube and Collide modifiers.
  • Method 1 colour: in a Particle Node Modifier, Sample Shader reads the image at each particle's UVW; 1 minus Y flips it the right way up.
  • Method 1 motion: velocity is the particle normal crossed with a Random Field direction, then curl, displacement along the normal and a time-based Mix.
  • Method 2 masks: a Shader Field reads the image into Vertex Color, Vertex Maps and Polygon Selections, plus their inverted versions.
  • Method 2 motion: a Volume Builder in vector mode with Vector Smooth, Curl and Normalize drives a Field Force set to absolute velocity; several Mesh Emitters use the selections and colour map.

Two tutorials on our channel animate famous paintings with particles in Cinema 4D. The newer one brings Edvard Munch’s The Scream (1893) to life with a Particle Node Modifier. The earlier one recreates Vincent van Gogh’s The Starry Night with the Particles system and field forces.

Both start from the same idea: a plane carries the painting, particles spawn on it and take their colour from the image, and a noise-based flow moves them like brushstrokes. This guide walks through both, so you can pick the one that fits your version of Cinema 4D and how much node work you want.

Checked against the Maxon Cinema 4D help pages for Scene Nodes and the Node Editor, November 2026.

The main tutorial runs 18:29. Chapters: 1:40 base mesh and Mesh Emitter, 3:50 colorize, 5:23 flow field, 7:10 vector curl, 9:13 displacement along normal, 11:18 scale time control, 14:35 fields modifier, 17:36 wrap-up. The second method has its own video further down.

Why a cross product makes particles flow like brushstrokes

A Random Field gives every point a direction. If particles simply followed it, they would pile up where the directions converge. Method 1 instead crosses the field direction with the particle’s surface normal. On a flat plane facing up, that turns every direction by 90 degrees, so the particles travel along the contours of the noise rather than across them. The result is a swirling flow that stays on the plane, which is what makes the motion look painted.

iRender
Why the cross product makes particles swirl
Schematic
Field direction from a Random Field (normalized)Velocity = surface normal × field direction
field directionparticle trails, coloured from the image under them
Computed on a sample noise field

How to read the figure. Both panels use the same sample noise. On the left, the yellow strokes are the field direction. On the right, trails follow the direction turned by the cross product, and each trail is coloured from the image underneath its starting point, the same way Sample Shader colours particles by UVW.

Method 1: Particle Node Modifier (The Scream)

Base mesh and Mesh Emitter

  1. Create a Plane with orientation Y+ and scale it to the painting’s proportions (1600 × 1920 cm in the video). Set the segments to match.
  2. Add a Mesh Emitter, pick the plane as its geometry, and set Emission Mode to Constant at 5,000 per frame.
  3. In the Output tab, enable Normal and UVW Coordinates; the node graph needs both later.
  4. In Properties, set Lifetime to 120 frames and Velocity Speed to 0 cm.
  5. Add a Flock Modifier: Strength 5, Neighbour Search Full, Cohesion Strength 10, Separation Strength 0.5.
  6. Enclose the plane in a Cube with a Collider tag, Collision Side Both, and add a Collide Modifier with Radius 1 cm and Dynamic Friction and Angle Variation at 2%.

Colour the particles from the painting

  1. Apply a Particle Node Modifier and open the Node Editor.
  2. Drag the painting image into the node graph and feed it to a Sample Shader node.
  3. Add Get Particle Property set to UVW, data type Vector 64, and connect it to the UVW port.
  4. The image appears upside down; take 1 minus the Y value and connect it to the Y of the UVW port.

Flow field, curl and displacement

  1. In the Field tab, add a Random Field: Perlin, scale 1800%, animation speed 100%, Sine Curve remapping, direction Length set to Normalize.
  2. In the Node Editor, read the Normal with Get Particle Property (Vector 32), take its Cross Product with the field direction, scale it with a Strength parameter around 200 and connect it to the Velocity port.
  3. For curl, split the cross product vector, multiply x and z by a curl parameter with Arithmetic nodes, and rebuild it with a 3D vector compose node.
  4. For depth, remap the field value from 0–1 to −1–1 with Range Mapper, multiply by a parameter, scale the normal by it and add it to the cross product vector. The particles now leave the plane in both directions.
iRender
Method 1 inside the Particle Node Modifier
Schematic
Get Particle PropertyUVW, Vector 64ValueSplit VectorVectorXYZ1 − YYYCompose VectorXYZUVWSample Shader (painting)UVWImageColor → particleGet Particle PropertyNormal, Vector 32NormalRandom Field directionPerlin, 1800 %NormalizeDirectionCross ProductNormalDirectionFlowCurl: × on x, zFlowCurlFlowScaleFlowStrength ~200VelocityVelocity portVelocity1Colour: read the painting at each particle's UVW1Motion: flow along the noise contours
particle data inresult out
Simplified; displacement along the normal and time control are added on top of the motion chain

How to read the figure. These are the two chains you build inside the Particle Node Modifier for Method 1. The top one only sets colour: it takes each particle’s UVW, flips Y so the painting is the right way up, and samples the image there. The bottom one sets motion: crossing the particle normal with the field direction gives a flow along the plane, which the curl and Scale nodes then shape. Build and check the colour chain first; once the painting appears on the particles, add the motion chain.

Control velocity over time

  1. Remap the field value again, this time to −0.5–0.5.
  2. Use Time, Compare, Range Mapper and If nodes to change the velocity scale by frame, and a Mix node to blend the velocity over time.
  3. Add more fields, change the seed, noise type, scale and remapping until the motion looks right, then cache the particles.

Method 2: Particles system and Field Force (The Starry Night)

This video runs 10:57. Chapters: 0:40 basic painting, 4:12 Volume Builder and Field Force, 7:17 the Particles system, 10:17 wrap-up.

Build the painting and its masks

  1. Create a Plane sized to the painting (320 × 260 cm in the video) with matching segments.
  2. Make a Standard material with Reflectance off and the painting linked in the Color channel. Apply it and name the plane Painting.
  3. Add a Vertex Color tag. Create a Shader Field with the channel set to Color, pointed at the material tag, Strength set to Gray (invert if needed), and use it in the Vertex Color tag.
  4. Create a Vertex Map from the Shader Field, raise its contrast with a Range Map, and build a Polygon Selection from it.
  5. Repeat to make an inverted Vertex Map and an inverted Polygon Selection.
iRender
From image brightness to two particle emitters
Schematic
1. Shader Field reads image brightness2. Vertex Map + Range Map → selection3. One emitter per selection
Polygon Selection (bright)Polygon Selection Invert (dark)
Computed on a sample brightness pattern, not the painting

How to read the figure. It uses a sample brightness pattern, not the painting. The grey map is what the Shader Field reads; the contrast step splits it into a bright selection and an inverted dark one; each selection then gets its own emitter with its own rate and colour.

Volume Builder and Field Force

  1. Create a Volume Builder set to Vector with a 1 cm voxel size.
  2. Add a Group Field containing a Random Field (Perlin, scale 600%, direction Normalize), masked by the Shader Field.
  3. Put Painting and the Group Field in the Volume Builder, set Creation Space to Object Below and the mode to Cross, then add Vector Smooth, Vector Curl and Vector Normalize.
  4. Create a Field Force, choose the Volume Builder as its volume object and mask it with the Shader Field.
  5. Add a Mesh Emitter on Painting with velocity 0 cm and Rate Per Frame. Particles drift off the plane at first; set the Field Force Velocity Type to Set Absolute Velocity with Strength 50 and they follow the surface.

Colour and emitters

  1. In the Mesh Emitter’s Property Maps, set the Color Map to Painting’s vertex color.
  2. Under Emission, set Restriction to a Polygon Selection to control where particles spawn.
  3. Create several Mesh Emitters with different Restriction, Color Map, Rate and Lifetime values.
  4. In the Particle Group’s Draw tab, set Draw Mode to Lines to see the flow patterns clearly.
iRender
Method 2, object by object
Schematic
Object Manager (Method 2)Painting (Plane 320 × 260 cm)SVCM2 maps, 2 sel.1Shader Field (Color, Gray)1Volume Builder (Vector, 1 cm)2Group Field2Random Field (Perlin 600 %)2Field Force2Mesh Emitter A (bright)3Mesh Emitter B (dark)3Particle Group (Draw: Lines)3Volume BuilderObjectsPainting + Group Field2Volume TypeVector2Creation SpaceObject Below2ModeCross2FiltersSmooth, Curl, Normalize2Field ForceVolume objectVolume Builder2Velocity TypeSet Absolute Velocity2Strength502Mesh Emitter ARestrictionPolygon Selection3Color MapPainting vertex color3
badge = part of Method 2: 1 masks, 2 force, 3 emitters
Layout reconstructed from the steps in the video

How to read the figure. This is where Method 2 ends up. Badge 1 is the painting and its masks, badge 2 the Volume Builder and Field Force that move the particles, and badge 3 the emitters. Most “particles fly off the painting” problems come from the Field Force: check that its volume object is the Volume Builder and that Velocity Type is Set Absolute Velocity.

Which method to choose

Method 1 keeps everything in one Particle Node Modifier, so colour, flow, curl, depth and timing are all parameters in one graph. It takes more node work but gives the most control. Method 2 uses standard objects and tags, which is quicker to set up and easier to read if you rarely work in nodes, and the selections make it simple to treat bright and dark parts of the painting differently. Both use particle counts in the thousands per frame, so cache or bake before final rendering.

Render the animation on several GPUs

Procedural setups are evaluated before each frame renders, so time a test frame first and cache anything that simulates over time. After that, Redshift can render each frame on every GPU in the machine. Each card holds its own copy of the scene, so plan VRAM per card, not in total (Maxon support). A scene that fits on one RTX 4090 (24 GB) or RTX 5090 (32 GB) fits on each card of a 4x or 8x server.

Painting in motion checklist

Check these points before you cache and render.

ChecklistPainting in motion checklist
0 / 9 done
Tip: Tick the items as you check the scene. The ticks reset when you reload the page.

SaaS or IaaS render farm for procedural Cinema 4D setups?

A Scene Nodes or particle setup is stored in the .c4d file, so any farm with a compatible Cinema 4D version renders it the same way. The differences are version matching, how heavy the evaluation is before each frame renders, and how fast you can fix a setup that behaves differently at render time.

Farm modelFor this task

SaaS or IaaS for procedural scenes

How each farm model fits a procedural Cinema 4D scene built with nodes, fields or simulations.

Your situationSaaS render farmIaaS render farm (iRender)
The scene is final and the farm supports your exact Cinema 4D versionA good fit: upload the scene, the farm renders the framesWorks too; you open the scene and render it yourself
The setup depends on a recent Cinema 4D releaseCheck that the farm runs the same release, since node assets can change between versionsInstall or update to the release you used, so the setup evaluates the same way
A frame looks different from your viewportFix it locally, upload again and resubmitOpen the scene on the server and fix it where it renders
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 scene is final and the farm runs your Cinema 4D version, a SaaS farm saves you the machine work. If you need a specific release, or want to check the setup where it renders, a server you control is the safer choice.

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 and its assets on iRender Drive before you start a server; transfer and storage are free.
  2. Match the version. Cinema 4D and Redshift are pre-installed; check the version and update it to the one you built the scene in if needed. Your server image keeps the change.
  3. Check the setup. Scrub the timeline and confirm the animation evaluates the same way as on your PC; cache any simulation.
  4. Render a test frame. Check the Redshift log for all GPUs and the detail 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 particles get the colours of a painting in Cinema 4D?

In Method 1, a Sample Shader node reads the image at each particle’s UVW coordinate. In Method 2, the Mesh Emitter’s Color Map uses a Vertex Color tag filled from the image.

2. Why does the painting appear upside down?

The V direction of the UVW coordinates runs the opposite way to the image; taking 1 minus Y fixes it.

3. Why cross the normal with the field direction?

It turns the field direction 90 degrees within the surface, so particles flow along the noise contours and stay on the plane.

4. What does the Field Force velocity type change?

Set Absolute Velocity makes particles follow the volume field directly instead of drifting off the plane.

5. Why use inverted selections?

So bright and dark parts of the painting can have separate emitters with different rates, lifetimes and colours.

6. Which paintings do the tutorials use?

The Scream by Edvard Munch for Method 1 and The Starry Night by Vincent van Gogh for Method 2.

7. Should the particles be cached?

Yes. Caching gives the same result on every frame and every machine when rendering.

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
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →