Fibonacci Lattices in Cinema 4D Scene Nodes: Phyllotaxis on Planes, Spheres and More (2026)
Even, natural-looking point spreads such as sunflower seeds can be built in Cinema 4D Scene Nodes with the golden angle: a Spiral Distribution node for a flat disc, a short formula for a sphere, and the same rule wrapped on any surface of revolution.
- Flat: Spiral Distribution (count, angle, scale), Decompose Container and Iterate Collection into a Matrix; Points to Line with y scale 0; spheres instanced with Transform Geometry.
- Sphere setup: Fill Array with the Length port, Iterate Collection for Count and Index.
- Sphere formula: y = 1 − 2·index/(n − 1), rY = √(1 − y²), θ = index × 137.5°, x = cos θ·rY, z = sin θ·rY.
- Colour: a Basic Gradient driven by position and a Color Operator tint each seed.
- Revolution: spin a base spline around Y; keep y and use |x| of the profile as the radius.
In botany, phyllotaxis is the arrangement of leaves or seeds around a stem. Many plants place each new leaf about 137.5° from the last, the golden angle that comes from the golden ratio of about 1.618, and the result is the familiar interlocking spirals of sunflowers and pine cones. The same rule gives one of the most even ways to spread points over a sphere, known as the Fibonacci lattice.
This tutorial builds three versions in Cinema 4D Scene Nodes: a flat spiral, a sphere and a general surface of revolution. The guide follows the video chapter by chapter.
Checked against the Maxon Cinema 4D help pages for Scene Nodes and Álvaro González’s paper on Fibonacci lattices, November 2026.
The full tutorial runs 17:19. Chapters: 1:43 spiral phyllotaxis, 5:23 spherical phyllotaxis, 14:30 phyllotaxis over a surface of revolution, 16:39 wrap-up.
Why the golden angle spreads points evenly
Each new point is placed a fixed angle further around than the last, and a little further out. If that angle is a simple fraction of a turn, points line up into spokes and leave gaps. The golden angle, about 137.508°, is as far from any simple fraction as an angle can be, so no two points ever line up neatly and the disc fills evenly at every size.
How to read the figure. The three spirals are computed with the same 420 points and only the divergence angle changed. Half a degree off the golden angle is enough to turn the even sunflower pattern into curved spokes, and 140° gives straight spokes with wide gaps.
1. Spiral phyllotaxis on a plane
- Create an Object Group and enter the Scene Nodes environment.
- Add a Spiral Distribution node. It controls the number of points, the rotation angle and the scaling factor.
- Use Decompose Container to split its output into usable data, then Iterate Collection to extract what you need and connect it to the Matrix port.
- Check the result with a Points to Line node set to Values, and set the y scale to 0 cm so all points lie flat.
- Use Transform Geometry to instance a small sphere on each point.
- Tweak count, angle and scale until the pattern looks right.
2. Spherical phyllotaxis
- Add a Fill Array node and enable its Length port to set how many points to generate.
- Use Iterate Collection to get Count and Index, and regroup them into the starting point set.
- For n points on a unit sphere, the video uses: y = 1 − 2·index/(n − 1), which runs from 1 to −1; the ring radius rY = √(1 − y²); the angle θ = index × the divergence angle (about 137.5°); then x = cos θ·rY and z = sin θ·rY.
- Build y with Arithmetic nodes and add a U parameter to control the y displacement.
- Get rY with Power and Root nodes, and x and z with Trigonometry nodes.
- Combine x, y and z with Compose Vector 3D, scale by the sphere radius with a Scale node, and connect to Transform Geometry.
- Adjust the U parameter until the spread is even, and use a smaller sphere for the seeds so the pattern reads clearly.
- Colour the seeds with a Basic Gradient driven by the y position through its Position port, passed into a Color Operator.
How to read the figure. Each purple node is one line of the formula in step 2, so you can build and check them one at a time. The index i is the only thing that changes from point to point: it sets the height y (from 1 at the top to −1 at the bottom), the ring radius at that height, and the angle around the axis. If all your points land on one vertical line, the θ node is not getting the index; if they bunch at the poles, check the rY node.
3. Phyllotaxis over a surface of revolution
The same idea works on any shape made by spinning a profile around an axis.
- Draw a base spline and rotate it around the Y axis to make the surface.
- Keep the same y values, but set the radius at each height to the absolute value of the profile’s x at that height.
- Change the base spline, or use another one, to get a different surface and a different phyllotaxis pattern.
How to read the figure. Both are computed. On the sphere, one spiral runs from the top pole to the bottom one and the points come out evenly spaced; Álvaro González showed that this kind of lattice measures areas on a sphere with at least 40% less error than a latitude-longitude grid. On the right, the same rule follows a wavy profile, so points crowd slightly where the surface narrows.
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.
Fibonacci lattice checklist
Check these points before you 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 Fibonacci lattice?
A set of points placed along one spiral using the golden angle, which spreads them very evenly over a disc or a sphere.
2. What is the golden angle?
About 137.5°, the angle that divides a full turn in the golden ratio.
3. What is phyllotaxis?
The arrangement of leaves or seeds around a plant stem, often in golden-angle spirals.
4. How do you place Fibonacci points on a sphere?
For point i of n: y = 1 − 2i/(n − 1), radius √(1 − y²), angle i × 137.5°, then x and z from cosine and sine of that angle.
5. Which node makes the flat spiral?
The Spiral Distribution node in Cinema 4D Scene Nodes.
6. How are the seeds coloured?
With a Basic Gradient driven by position, passed into a Color Operator.
7. Can this work on shapes other than spheres?
Yes, on any surface of revolution: keep y and use the absolute x of the profile as the radius.
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.




