Torus Knot Patterns in Cinema 4D Scene Nodes: From Trefoil to Decorative Knots (2026)
Torus knots, curves that wind p times one way and q times the other around a doughnut, can be generated in Cinema 4D Scene Nodes from a short formula, traced over time with a Memory node and then varied into decorative patterns.
- Torus: two N-Side nodes, the Ring and the Pipe, joined with Sweep Line.
- Formula: parameters Theta, p and q; Arithmetic and Trigonometry nodes build cos(pt)·cos(qt), sin(pt) and sin(qt), then x, y and z.
- Trace: a Memory node with Append Element (Array/Vector) stores each position; Assemble Spline shows the path.
- Animate: keyframe Theta from 0 to 360°; p = 2, q = 3 gives a trefoil.
- Display: Resample Spline, Sweep Line with an N-Side for a tube, and an Object Group node to show knot and torus together.
A torus knot is a knot that lies on the surface of a torus. It is described by two whole numbers with no common factor, p and q, that count how many times it wraps around the torus in each direction. The simplest is the trefoil. Torus knots are also studied in physics, chemistry and topology, and they make striking motion-design shapes.
This tutorial builds a torus knot in Cinema 4D Scene Nodes and then turns it into decorative patterns, following ideas from two papers: Jim Hoste’s “Torus knots are Fourier-(1,1,2) knots” and Lindsay D. Taylor’s “Decorative Knot Patterns”.
Checked against the Maxon Cinema 4D help pages for Scene Nodes, Jim Hoste’s paper on arXiv and MathWorld, November 2026.
The full tutorial runs 17:50. Chapters: 1:15 base torus, 3:00 torus knot, 13:16 decorative knot patterns, 17:10 wrap-up.
What p and q do
Picture a point running along the torus. One number sets how many times it goes around the small circle of the tube, the other how many times it goes around the big ring, before it meets its starting point. If the two numbers share no common factor, the path closes into a single knotted loop. A (p, q) torus knot is the same knot as a (q, p) torus knot.
The video simplifies the published parameterization into a form that is easy to build with nodes. A common version of that form is x = (R + r cos pt) cos qt, y = r sin pt, z = (R + r cos pt) sin qt, where R is the ring radius and r the pipe radius; the nodes compute the same cos(pt)·cos(qt), sin(pt) and sin(qt) terms. Hoste’s paper gives a different, more compact formula that describes the same knots.
How to read the figure. Both panels are computed. The torus on the left is the Ring and Pipe you build first. On the right, the curve winds twice around the pipe and three times around the ring: a trefoil. Fainter segments are behind; where they cross, the front strand passes over.
1. Build the base torus
- Create a Node Mesh and open the Scene Node workspace.
- Add an N-Side node for the longitude curve, the outer ring (called the Ring in Cinema 4D), with parameters for radius and number of sides.
- Add a second N-Side for the meridian curve, the small profile around the ring (the Pipe), with its own radius and sides.
- Join them with a Sweep Line node. You now have a fully procedural torus.
2. Build the torus knot
- Create parameters Theta, p and q.
- With Arithmetic and Trigonometry nodes, compute cos(pt)·cos(qt), sin(pt) and sin(qt), then combine them into x(t), y(t) and z(t).
- Feed x, y and z into Compose Vector 3D. This gives the position of the point on the knot for the current Theta.
- To record the path, add a Memory node with an Append Element node of data type Array/Vector, so each new position is stored as the animation runs.
- Connect it to Assemble Spline to see the trace.
- Keyframe Theta from 0 to 360° and set p and q for a trefoil, the simplest knot.
Make it visible
- Add Resample Spline to smooth the curve.
- Use Sweep Line with an N-Side profile to turn the line into a tube.
- Put the knot and the torus in an Object Group node to display both.
- Try other p and q values from a knot table to get other torus knots.
How to read the figure. Six torus knots computed with the same formula, seen nearly from above. Crossing numbers follow the MathWorld formula min(p(q − 1), q(p − 1)): 3 for the trefoil up to 14 for (3, 7). Higher numbers mean denser knots and longer splines, which is worth knowing before you sweep them into heavy tube meshes.
How to read the figure. Read the top chain as “where is the point right now”: for the current Theta it computes one position on the knot. The Memory node is what turns that single moving point into a curve, by appending each new position to a list as Theta is animated. The bottom chain only draws that list. If you see one point moving but no curve, the Append Element inside the Memory node is not connected.
3. Decorative knot patterns
Lindsay D. Taylor’s paper “Decorative Knot Patterns” (Visual Mathematics, 2011) explores artistic variations of knot curves; the author’s own implementation used Blender and Python. The tutorial rebuilds the core idea in Scene Nodes: it adds parameters for x, y and z to the formula and builds a node setup around them, then changes those parameters to transform the knot into new patterns. Work through values gradually and keep the Memory trace on so you can see each variation draw itself.
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.
Torus knot checklist
Check these points before you sweep 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 a torus knot?
A knot that lies on the surface of a torus, described by two numbers p and q with no common factor that count its windings in each direction.
2. Which p and q give a trefoil?
p = 2 and q = 3 (or the other way round).
3. How is the knot drawn over time in Scene Nodes?
A Memory node with Append Element stores each new position as Theta is animated, and Assemble Spline turns the stored points into a curve.
4. Why use an Object Group node?
To show the knot and the torus together.
5. How many crossings does a torus knot have?
min(p(q − 1), q(p − 1)), for example 3 for the trefoil and 8 for the (3, 4) knot.
6. What are decorative knot patterns?
Artistic variations of knot curves explored by Lindsay D. Taylor; the video rebuilds the idea with extra x, y and z parameters in Scene Nodes.
7. How do I turn the knot into geometry?
Resample the spline, then use Sweep Line with an N-Side profile.
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.




