Strange Attractor in Cinema 4D with the Particle Node Modifier: Thomas “Cosmic Jellyfish” (2026)
The “cosmic jellyfish” in our tutorial is Thomas’ cyclically symmetric attractor: three short equations that move every particle a little each frame. In Cinema 4D they run inside a Particle Node Modifier on a basic emitter.
- Emitter: a Basic Emitter with a small sphere shape (about 1 cm), about 800 particles per frame, lifetime 90 frames with 30 frames of variation, and near-zero speed.
- Equations: inside the Particle Node Modifier, Position and Split Vector feed trigonometry nodes that compute sin y - b x, sin z - b y and sin x - b z.
- Velocity: Compose Vector 3D rebuilds the vector, and a Scale node sets how fast particles follow it.
- Parameter b: it is the damping; in the standard form, chaos appears when b drops below about 0.208.
- Finish: add a Random Field for colour and direction, extend the scene to 900 frames, cache and bake to Alembic, then render.
Chaos theory, pioneered by Edward Lorenz and popularised as the butterfly effect, studies systems that never repeat yet stay inside a recognisable shape. Those shapes are called strange attractors. Our tutorial visualises one proposed by René Thomas, nicknamed the cosmic jellyfish, with Cinema 4D’s particle system and the Particle Node Modifier.
This guide follows the video, gives the equations behind it, and shows what the parameter b really does, which is the part the video invites you to experiment with.
Checked against the Maxon Cinema 4D help pages for the particle system and the Particle Node Modifier, and published descriptions of Thomas’ cyclically symmetric attractor, November 2026.
The full tutorial runs 12:05. Chapters: 0:00 intro, 2:03 Basic Emitter, 3:07 Particle Node Modifier, 10:56 wrap-up.
The equations behind the cosmic jellyfish
Thomas’ attractor is defined by three equations, one per axis: dx/dt = sin(y) – b·x, dy/dt = sin(z) – b·y and dz/dt = sin(x) – b·z (arXiv 1908.05989). Each axis is pushed by the sine of the next one and slowed by the damping term b. The same rule applied to every particle, every frame, is all the Particle Node Modifier has to compute.
How to read the figure. This is the path of a single point stepped through the equations thousands of times with b = 0.19, seen from an angle. The path never closes or repeats, but it never leaves this tangled, three-fold symmetric shape either. In Cinema 4D you see the same shape built from thousands of particles at once instead of one long path.
1. Create the emitter
- Create a Basic Emitter and set its shape to a small sphere, radius about 1 cm.
- Set the emission rate to about 800 particles per frame.
- Set the lifetime to 90 frames with a 30-frame variation.
- Keep the speed near zero so the starting cloud is stable.
Press Play and you get a small, clean cloud of starting points. The emitter belongs to the particle system Maxon introduced in Cinema 4D 2024.4, which can run on the GPU (Maxon: Particle Simulations – An Introduction).
2. Write the equations in the Particle Node Modifier
Add a Particle Node Modifier to the emitter and open it in the node space. Maxon describes it as a modifier that opens as a capsule in the Node Editor, where your own node logic acts on the particles (Maxon: Particle Node Modifier).
- Start with a Position node and split it with Split Vector into X, Y and Z.
- Use the Trigonometry node and math nodes to compute the three new values, and create a control parameter called b.
- Recombine them with Compose Vector 3D.
- Add a Scale node with a parameter that controls particle velocity.
Maxon notes that this modifier runs on the CPU while the other particle modifiers are GPU-accelerated, so it is slower but much more flexible. With 800 new particles per frame and long lifetimes, expect playback to slow down as the count grows.
How to read the figure. Each purple node is one line of the equations, built in the graph from a Trigonometry node (the sine) and two math nodes (multiply by b, subtract). Notice how the wires cross: the change in X uses sine of Y, the change in Y uses sine of Z, and the change in Z uses sine of X. Getting one of those crossings wrong is the most common reason the shape never appears. The values in the small panel are the ones from the figure in step 3.
3. Tune the parameter b
In the standard equations, b is the damping. Published analyses describe a Hopf bifurcation near b ≈ 0.329 and chaos below about b ≈ 0.208 (arXiv 2303.08126). How your parameter maps to that depends on how you wired it in the node graph, which is why the video asks you to experiment.
How to read the figure. All three panels start from the same point. With strong damping (b = 0.45) the path simply settles on one point and the particles would bunch up. With b = 0.24 it settles on a closed loop. With b = 0.19 it never settles, which is the chaotic state that gives the jellyfish its shape. Each panel is drawn at its own scale.
Then extend the scene to 900 frames and fine-tune the particle lifetime so the structure fills in without becoming a solid blob.
4. Add colour and direction, then bake
- Add a Random Field to the Particle Node Modifier.
- Use a Color Field to shade the whole system.
- Feed a Direction Field into the motion for new dynamic behaviour.
When you are happy with it, cache the particles and bake them to Alembic. The bake fixes the result, so every frame renders the same on any machine and the slow CPU-side node evaluation does not have to run again during the final render.
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.
Strange attractor checklist
Check these points before you bake 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 the cosmic jellyfish attractor?
It is Thomas’ cyclically symmetric attractor, a strange attractor proposed by René Thomas. Its three equations are dx/dt = sin y – b x, dy/dt = sin z – b y and dz/dt = sin x – b z.
2. How do you make a strange attractor in Cinema 4D?
Emit particles with near-zero speed, then use a Particle Node Modifier to compute the attractor equations from each particle position and set the result as its velocity.
3. What does the parameter b do?
It is the damping. With high b the motion settles on a point, with medium b it settles on a loop, and in the standard form it becomes chaotic below about 0.208.
4. Why is playback slow with the Particle Node Modifier?
Maxon notes that node logic in this modifier runs on the CPU, while the other particle modifiers are GPU-accelerated. Large particle counts make it slower.
5. Why bake the particles to Alembic?
Baking fixes the result, so every frame renders identically and the node evaluation does not run again during the final render, including on other machines.
6. Can I make other attractors with the same setup?
Yes. Swap the three equations in the node graph, for example for the Lorenz or Aizawa systems, and adjust the scale and speed.
7. Which Cinema 4D version do I need?
A version with the particle system introduced in 2024.4 and the Particle Node Modifier. A current release is the safest choice.
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.




