Mutual Pursuit Curves in Cinema 4D Scene Nodes, in 2D and 3D (2026)
When points chase each other in a ring, each heading for the next, they spiral into the centre along pursuit curves. Cinema 4D Scene Nodes can simulate this with a Loop-Carried Value that moves every vertex toward its neighbour, and a Memory node that records the trails.
- Start: an N-Side node with 3 sides; Geometry Property Get (Positions) gives the vertex array.
- Chase: inside a Loop-Carried Value, Get Element reads each vertex and its neighbour (index − 1); Subtract and Normalize give the direction.
- Move: an Alignment node (Y orientation 1) and a Mix node with an exposed Blend move each point toward the next; Assemble Collection gathers them.
- Trails: a Range sets the steps, Append Elements and Assemble Spline (linear) draw them; a Memory node records the paths as Progress is keyframed.
- 3D: a Platonic Tetra with Subdivide (0) and Polygons Info feeds its positions into the same loop.
A pursuit curve is the path of something chasing a target. In the classic “mice problem”, n points sit at the corners of a regular polygon and each chases the next at constant speed, the last chasing the first. For any regular polygon, each point traces a logarithmic spiral and all of them meet at the centre.
This tutorial recreates mutual pursuit curves in Cinema 4D Scene Nodes, first in 2D on a polygon and then in 3D on a platonic solid, without any calculus. The guide follows the video chapter by chapter.
Checked against the Maxon Cinema 4D help pages for Scene Nodes and MathWorld, November 2026.
The full tutorial runs 13:41. Chapters: 0:58 2D pursuit curves, 10:17 3D pursuit curves, 13:13 wrap-up.
Why the chasers spiral
Each point always heads straight for its neighbour, but the neighbour is moving sideways at the same time. So no point ever reaches its target directly; instead, the whole polygon shrinks and rotates a little every step. The corners stay the corners of a regular polygon at every moment, and their paths curl into spirals that meet at the centre.
How to read the figure. Both panels are computed with a fixed blend toward the next corner, which is what the Mix node in the video does. Drawing the polygon at every step gives the familiar whirl pattern on the left; following one corner at a time gives the spiral paths on the right.
1. 2D pursuit curves
Set up the polygon
- Start with an Object Group (a Node Spline also works) and add an N-Side node with 3 sides for a triangle.
- Add Geometry Property Get set to Positions to get the array of vertex positions. The goal: A chases B, B chases C, and C chases A, all at once.
Make each vertex chase its neighbour
- Add a Loop-Carried Value. Connect the Array port to its Type Of port to set the data type and to Variable 1; then delete the temporary data type node.
- Inside, add Iterate Collection on Variable 1 and two Get Element nodes of type Array containing Vector, both reading Variable 1.
- The first Get Element uses the Iterate Collection index. For the second, an Arithmetic node (Int, Subtract, input 2 = 1) gives index − 1, so you get each vertex and its neighbour.
- Subtract the two positions (Vector) for the direction, Normalize it for constant speed, and connect it to the Direction port of an Alignment node with the Y orientation set to 1.
- Use a Mix node (Vector) to move each vertex toward its neighbour, combine with the Alignment result, and collect with Assemble Collection scoped to the Iterate Collection. Expose the Mix Blend as a control.
- Give the loop a scope with a Range node, 5 for now, gather the results with Append Elements and check them with Assemble Spline set to linear.
As you raise Progress, the vertices chase each other into the centre. Change the number of sides to explore other shapes.
How to read the figure. The key trick is in the dashed box: two Get Element nodes read the same list of corners, one at index i and one at index i − 1, so every corner knows which neighbour it is chasing. Subtract and Normalize give the direction, and Mix moves the corner a fraction of the way there. The Loop-Carried Value repeats that for the number of steps set by the Range, and the green nodes on the right keep every step so Assemble Spline can draw the trails.
Record the trails
- Add a Memory node with Append Elements and Iterate Collection inside to record every position.
- Keyframe Progress to watch the curves form.
- Change the Operation of the Subtract node in the Loop-Carried Value to switch the rotation between clockwise and counter-clockwise.
- For plain pursuit curves without the polygon pattern, adjust what the Memory node records.
How to read the figure. Each panel is computed. More sides mean each point turns less per step, so the spirals are gentler. Reversing who chases whom, as the Subtract operation does in the video, reverses the direction of the spiral.
2. 3D pursuit curves
- Replace the N-Side with a Platonic object set to Tetra.
- Connect it to a Subdivide node with subdivisions at 0 to start.
- Add Polygons Info, use Iterate Collection on its Positions port, and feed the result into the same Loop-Carried Value.
- Scrub the timeline to check the result, then try other Platonic types and more subdivisions.
In 3D every polygon of the solid runs its own chase, so the result is a shell of interlocking spirals. Subdividing multiplies the number of curves quickly, so sweep them into thin tubes and bake before 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.
Pursuit curves 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 are mutual pursuit curves?
The paths traced by points that each chase the next one at constant speed, with the last chasing the first.
2. What shape do the paths make?
For a regular polygon, each path is a logarithmic spiral and all of them meet at the centre.
3. How does each point know its target in Scene Nodes?
Two Get Element nodes read the vertex at the current index and at index − 1 from the same array.
4. Why normalize the direction?
So every point moves at the same constant speed regardless of distance.
5. How are the trails recorded?
A Memory node appends each new position, and Assemble Spline draws the stored points.
6. How do you reverse the spiral?
Change the Operation of the Subtract node in the Loop-Carried Value.
7. How do you make it 3D?
Feed the positions of a Platonic solid, optionally subdivided, into the same loop.
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.




