Cymatics Simulation in Cinema 4D with a Formula Field and Particles (2026)
Chladni-style cymatics patterns, where sand gathers on the still lines of a vibrating plate, can be simulated in Cinema 4D by driving a Field Force with a Formula Field and letting particles from a Basic Emitter settle on its zero lines.
- Field: a Formula Field with the cymatics formula, an animated variable f, and a subfield with the formula =f.
- Force: a Field Force set to Set Absolute Velocity, strength 20, using the Formula Field; f is keyframed.
- Emitter: a Basic Emitter rotated 90° in pitch, Rectangle 400 × 400 cm, 5,000 per frame for a 10-frame range, speed 0 cm.
- Shape: Invert Direction on the Formula Field; a Curve Field with the Gauss preset and a Range Map Field in the Field Force.
- Life: a Turbulence Force and a Flock Modifier (separation 2 at 0.5 cm, cohesion 5 at 2 cm, flock strength 5).
Cymatics is the study of visible sound and vibration. When a plate vibrates at a resonant frequency, some lines on it stay still while everything else moves, and sand scattered on the plate is shaken off the moving parts and collects on those still lines. The resulting figures are named after Ernst Chladni, who demonstrated them in the 18th century.
This tutorial recreates the effect in Cinema 4D with a Formula Field and the particle system. The guide below follows the video chapter by chapter.
Checked against the Maxon Cinema 4D help pages and Paul Bourke’s notes on Chladni plates, November 2026.
The full tutorial runs 9:14. Chapters: 0:50 Formula Field, 1:38 Field Force and Basic Emitter, 5:20 Turbulence Force and Flock Modifier, 8:49 wrap-up.
Where the sand goes
For a square plate held at its centre, a widely used idealised formula for the still lines is cos(nπx/L)·cos(mπy/L) − cos(mπx/L)·cos(nπy/L) = 0, where n and m are whole numbers and L is the plate size. Wherever that expression is zero the plate does not move; wherever it is large, the plate shakes hardest. Changing n and m changes the pattern.
How to read the figure. Each plate is computed by keeping only random points that lie very close to a zero of the formula, which is where real sand ends up. Higher n and m give denser, more intricate figures. The video shows its own version of the formula on screen, with a variable f in place of fixed numbers so the pattern can be animated.
1. Build the Formula Field
- Create a Formula Field and enter the cymatics formula shown in the video. It uses a variable f and subfields to control the waves.
- Add a subfield to the Formula Field with the formula =f.
2. Field Force and Basic Emitter
- Create a Field Force, set the velocity type to Set Absolute Velocity with strength 20, and assign the Formula Field.
- Keyframe f so the force changes over time.
- Create a Basic Emitter. In Coordinates, set R.P to 90°. In Emission, choose a Rectangle of 400 × 400 cm, 5,000 particles per frame, with a Range of 10 frames. Set the speed to 0 cm in Properties.
- Press play: the particles spread outward. Tick Invert Direction in the Formula Field’s Direction tab and they move inward instead.
- In the Field Force’s Object tab, add a Curve Field and load the Gauss preset in Layer Controls. The cymatics pattern starts to appear.
- Adjust the curve’s control points and the force strength, and add a Range Map Field to fine-tune.
How to read the figure. On the left, the computed vibration amount for n = 2, m = 5, with arrows pointing toward the still lines, which is the motion you want after inverting the direction. On the right, a generic bell-shaped curve compared with a straight line: a curve like this keeps the response strong for one range of values and fades it elsewhere, which is how the Gauss preset sharpens the pattern.
How to read the figure. Every value from steps 1 to 3 in the places you will find them. The two settings people miss most are Set Absolute Velocity on the Field Force, without which the particles keep drifting instead of settling, and Invert Direction on the Formula Field, which makes them move toward the still lines rather than away from them.
3. Turbulence and flocking
- Add a Turbulence Force to the Particle Group and adjust it.
- Apply a Flock Modifier: Separation Strength 2 with a 0.5 cm radius, Cohesion Strength 5 with a 2 cm radius, Flock Strength 5.
- Keyframe the Formula Field parameters to move between patterns.
- Check the full effect with a Cloner and a Plane.
At 5,000 particles per frame the particle count climbs quickly, so cache the simulation before 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.
Cymatics checklist
Check these points before you cache and render.
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.
SaaS or IaaS for procedural scenes
How each farm model fits a procedural Cinema 4D scene built with nodes, fields or simulations.
| Your situation | SaaS render farm | IaaS render farm (iRender) |
|---|---|---|
| The scene is final and the farm supports your exact Cinema 4D version | A good fit: upload the scene, the farm renders the frames | Works too; you open the scene and render it yourself |
| The setup depends on a recent Cinema 4D release | Check that the farm runs the same release, since node assets can change between versions | Install or update to the release you used, so the setup evaluates the same way |
| A frame looks different from your viewport | Fix it locally, upload again and resubmit | Open the scene on the server and fix it where it renders |
| You have a deadline and need to know when rendering starts and ends | Jobs join the farm’s queue, so the start time depends on how busy the farm is; many farms sell higher-priority plans to start sooner | The server runs only your job from the moment it boots, so you control when rendering starts and can time the whole job |
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
- Upload first. Put the .c4d file and its assets on iRender Drive before you start a server; transfer and storage are free.
- 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.
- Check the setup. Scrub the timeline and confirm the animation evaluates the same way as on your PC; cache any simulation.
- Render a test frame. Check the Redshift log for all GPUs and the detail at final resolution.
- 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. What is cymatics?
The study of visible sound and vibration patterns, such as sand gathering on the still lines of a vibrating plate.
2. What are Chladni figures?
The patterns formed by sand on a vibrating plate, named after Ernst Chladni.
3. Which Cinema 4D field drives the effect?
A Formula Field with an animated variable, used by a Field Force.
4. Why tick Invert Direction?
So particles move toward the still lines instead of away from them.
5. What does the Curve Field with the Gauss preset do?
It reshapes the field values so the force sharpens the pattern.
6. Why add a Flock Modifier?
Separation and cohesion make the particles spread and clump like sand grains.
7. How many particles does the setup emit?
5,000 per frame for a 10-frame range in the video.
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.




