Noisy Isolines in Cinema 4D with Scene Nodes: Lines on Any Surface (2026)
Organic contour lines that wander across a model can be made in Cinema 4D Scene Nodes by deleting the polygons on one side of a noise map and keeping only the borders of what is left.
- Input: a Node Mesh with the model linked as the input object.
- Noise: a Noise Selection node with exposed parameters, or a Vertex Map shaped by a Random Field and Curve Modifier, switched with an If node.
- Delete: Invert Selection and Delete remove one side of the noise.
- Borders: Border Selection, Shrink Selection, Selection to Indexes and Dissolve clean the result; repeat with All Points if bits remain.
- Lines: Smooth Edge set to Point softens the border, Edge to Line turns it into splines; bake, then Sweep with an N-Side for a renderable mesh.
Isolines are lines of equal value drawn across a surface, the way contour lines show height on a map. Dominik Ruckli showed the Cinema 4D community a precise Scene Nodes method called gradient intersection for clean isolines. Our tutorial takes a simpler route that is less exact but gives a similar look and is easy to art-direct for motion design.
This guide follows the video step by step and explains why the method works: the borders of a noisy selection are, in effect, isolines of that noise.
Checked against the Maxon Cinema 4D help pages for Scene Nodes and the Node Editor, November 2026.
The full tutorial runs 17:48. Chapters: 0:58 initial model and selection, 7:43 border selection and dissolve, 11:27 edge to line, 15:40 line to mesh, 16:40 wrap-up.
Why the borders of a noise selection are isolines
A noise selection marks the polygons where a noise value is above a threshold. Delete everything else, and the edge of what remains runs exactly along that threshold, which is the definition of an isoline. Change the threshold or the noise and the lines move.
How to read the figure. The three panels use the same noise, computed on a flat grid instead of the head model so it is easy to see. Panel 1 is the noise value on the surface. Panel 2 keeps only the polygons above a threshold, the result of Invert Selection and Delete. Panel 3 keeps only the edges between kept and deleted polygons: those border edges are the noisy isolines you turn into splines.
1. Bring in the model and select by noise
- Import your model. The video uses a Head of David model from Sketchfab, prepared in advance.
- In the Scene Node workspace, set up a Node Mesh and link the model as the input object (Maxon: Scene Nodes Introduction).
- Add a Noise Selection node and create control parameters for it.
- Connect it to Invert Selection and Delete nodes and adjust until the surface matches your design.
Option: drive the selection with a Vertex Map
For more control, paint a noise map as a Vertex Map using a Random Field and a Curve Modifier. Back in the node graph, read it with a selection-by-weight node and the nodes needed to import the map. An If node lets you switch between the procedural noise and the Vertex Map at any time.
2. Extract and clean the borders
- Extract the borders with a Border Selection node.
- Apply Invert Selection, Shrink Selection, Selection to Indexes and Dissolve nodes to remove unwanted areas.
- Press Play to check. If parts of the surface are left behind, use Selection and Dissolve again with the mode set to All Points.
- If small errors remain, run Border Selection, Invert Selection and Delete one more time.
At this point only the border lines are left. Cleaning matters because any stray polygon creates a tiny closed loop that shows up as a dot or ring in the render.
How to read the figure. Use this as a checklist while you build steps 1 to 3. Each thumbnail is what the viewport should show after the node above it, computed on a flat grid so the shapes are easy to see. In panel 2 the noise has only selected the orange polygons; in panel 3 the rest has been deleted. If your result does not match the panel after a node, fix that node before adding the next one.
3. Smooth the borders and turn them into lines
Use a Smooth Edge node set to Point to soften the border, then an Edge to Line node to generate the splines.
How to read the figure. On the left, a border taken straight from a polygon mesh follows the polygon edges, so it steps like a staircase. On the right, the same border after its points are smoothed: the steps are gone and the line flows. That is the job of Smooth Edge before Edge to Line; on a dense model the steps are smaller, but they still show in close-ups.
4. Bake and build a renderable mesh
- When the lines look right, bake them so the scene does not re-evaluate the whole graph every frame.
- Use a Sweep object with an N-Side object as the profile to turn the isolines into a mesh.
- Experiment with other tools and modifiers to add variation and motion, for example animating the noise so the lines crawl across the surface.
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.
Noisy isolines 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 isolines?
Lines that connect points of equal value across a surface, like contour lines of equal height on a map.
2. How do you make noisy isolines in Cinema 4D?
In Scene Nodes, select polygons with a noise, delete one side, extract the borders of what remains, smooth them and convert them to lines with Edge to Line.
3. Is this the same as the gradient intersection method?
No. Gradient intersection is a more precise Scene Nodes method shared by Dominik Ruckli. This approach is simpler and less exact, but gives a similar look that is easy to control.
4. Why are there small loops or dots left on the surface?
Leftover polygons create tiny borders. Run Dissolve with the mode set to All Points, then a final Border Selection, Invert Selection and Delete pass.
5. Why do my isolines look stepped?
Borders follow the polygon edges. Add a Smooth Edge node set to Point before Edge to Line.
6. How do I render the isolines?
Bake them, then use a Sweep with a small N-Side profile to turn the splines into a mesh Redshift can render.
7. Can I use my own noise instead of the Noise Selection node?
Yes. Paint a Vertex Map with a Random Field and a Curve Modifier, read it with a selection-by-weight node and switch to it with an If node.
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.




