November 2, 2026 Linh Nguyen

Quilling Art Style in Cinema 4D Scene Nodes: Paper Spirangles on Any Mesh (2026)

Executive SummaryExecutive Summary: quilling spirangles
Cinema 4D 2025+

The look of paper quilling, rolled paper strips coiled inside shapes, can be generated in Cinema 4D Scene Nodes by splitting a mesh into separate faces and filling each face with a spirangle: a spiral that steps from the corners toward the centre.

  • Mesh: Mesh Primitive set to Platonic, type Tetra; Select all polygons, Inset 20%, Invert Selection and Delete to separate the faces.
  • Per face: Polygons Info gives centres and normals; each centre is lifted along its normal by a Normal Scale input.
  • Vectors: Subtract gives vectors from each vertex to the centre; a Range with a Loop input (8) divides them into equal steps.
  • Spiral: a second Range (Range Index), Get Element and Append Elements join step i of every vertex in order; Erase Elements stops faces from linking.
  • Paper: Trim Spline Modifier to grow it, Resample Spline to smooth, Extrude Line and Thicken for the paper strip.

Paper quilling is a craft where thin strips of paper are rolled, shaped and glued into designs. Its angular coils, called spirangles, are easy to recreate procedurally. This tutorial does it in Cinema 4D Scene Nodes, and the same setup can cover any mesh, from a simple platonic solid to the bird shown in the video.

The video thanks Dominik Ruckli and Donovan Keith for sharing their Scene Nodes knowledge. The guide below follows the video chapter by chapter.

Checked against the Maxon Cinema 4D help pages for Scene Nodes and the Node Editor, November 2026.

The full tutorial runs 13:54. Chapters: 0:40 basic mesh and split polygons, 3:40 quilling spirangles, 8:47 trim spline and line to mesh, 13:14 wrap-up.

How a spirangle is built

Every polygon has corner points and a centre. Draw a line from each corner to the centre and split each line into the same number of equal steps. Then walk around the polygon: take step 0 of every corner in order, then step 1 of every corner, and so on. Joining those points gives a spiral with straight sides that winds inward lap by lap, which is exactly the shape of a quilled paper coil.

iRender
How a spirangle is built from one polygon
Schematic
Triangle (Tetra face), Loop = 8Square (Hexa face), Loop = 8Pentagon (Dodeca face), Loop = 8
vertex-to-centre vectorsdivision pointspolygon centre
Computed: point i of every vertex vector, joined in vertex order

How to read the figure. All three are computed with Loop set to 8. The dashed lines are the vertex-to-centre vectors, the white dots are the division points, and the coloured line visits them corner by corner. A triangle, a square and a pentagon are the faces of the Tetra, Hexa and Dodeca platonic solids.

1. Basic mesh and split polygons

  1. Start with a Node Mesh (or an Object Group). Add a Mesh Primitive node with Primitive type Platonic and type Tetra, the simplest case.
  2. Add a Select node, type Polygons, selection string “all”, and connect it to an Inset node set to 20%.
  3. Use Invert Selection (Polygons) and a Delete node. This separates the faces of the solid.
  4. Use Polygons Info with its Centers port into an Iterate Collection, and link the Index port to the Select node’s selection string so the steps run per polygon.
  5. Group the nodes in a Scaffold.

2. Build the quilling spirangles

  1. Use another Polygons Info. Read each centre with Get Element, and run Iterate Collection over the Normals port into a Scale (Vector) node with a Normal Scale input. Add the scaled normal to the centre with an Arithmetic Add (Vector) node.
  2. Iterate over the Positions and use Subtract (Vector) to get the vector from each vertex to the centre.
  3. Divide these vectors with a Range node and a Loop input set to 8, using Subtract (Integer) and Divide (Float) nodes, then Scale (Vector) and Add (Vector) to place the points. The video corrects one connection here: the divide uses Input 1, not Input 2.
  4. Collect the points with Assemble Collection scoped to the Range, check them with Assemble Spline, then gather everything in another Assemble Collection scoped to the first Iterate Collection.
  5. Add a second Range, renamed Range Index, and an Iterate Collection scoped to it. A Get Element reads point i from each vertex list, and Append Elements collects them in order.
  6. The splines of neighbouring polygons join into one; fix this with an Erase Elements node scoped to the first Iterate Collection, connected to the Array port of Append Elements.
  7. Change the Platonic type to test other polygon shapes.
iRender
Step 2 as two node chains
Schematic
Polygons InfoCentersNormalsPositionsCentre + Normal × NSCenterNormalNormal ScaleCentreSubtract (Vector)CentreVertexVertex → centreRange ÷ LoopLoop = 8Input 1f = i / LoopScale + AddVectorfPointAssemble CollectionPoints per vertexListsRange Index0 … LoopiGet ElementList of vertex kIndex iPointAppend ElementsArrayPointSpirangleErase ElementsArrayClean2Points along each vertex-to-centre vector2Join point i of every vertex, lap by lapThe video fixes one wire here: the divide takes Input 1, not Input 2.
the divisionthe spiral
Simplified; helper nodes left out

How to read the figure. Step 2 is the longest part of the tutorial, so here it is split into the two jobs it does. The top chain makes the dots: for each corner it finds the line to the centre and places Loop points along it. The bottom chain connects them in the right order: point 0 of every corner, then point 1 of every corner, and so on, which is what turns the dots into a spiral. Erase Elements at the end keeps each polygon’s spiral separate.

3. Trim the spline and turn it into paper

  1. Add a Trim Spline Modifier to control how much of each spirangle is drawn, so it can grow over time.
  2. Add Resample Spline to smooth the shapes.
  3. Give the splines a surface with Extrude Line and a Thicken node, so each one reads as a paper strip standing on its edge.
  4. Adjust the inputs until the look is right.
iRender
Growing the paper strip
Schematic
Trim Spline at 30%Trim Spline at 65%Trim Spline at 100%, extruded and thickened
strip while growingfinished strip
Computed: the spline cut at a fraction of its length, as Trim Spline does

How to read the figure. The spline is computed and cut at 30%, 65% and 100% of its length, which is what animating the Trim Spline value does. The last one is drawn with width and a highlight to suggest the extruded, thickened paper.

A full model can hold thousands of these strips, each with its own trim animation. Bake the result before rendering so every frame and every machine sees the same geometry.

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.

Quilling checklist

Check these points before you bake and render.

ChecklistQuilling checklist
0 / 9 done
Tip: Tick the items as you check the scene. The ticks reset when you reload the page.

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.

Farm modelFor this task

SaaS or IaaS for procedural scenes

How each farm model fits a procedural Cinema 4D scene built with nodes, fields or simulations.

Your situationSaaS render farmIaaS render farm (iRender)
The scene is final and the farm supports your exact Cinema 4D versionA good fit: upload the scene, the farm renders the framesWorks too; you open the scene and render it yourself
The setup depends on a recent Cinema 4D releaseCheck that the farm runs the same release, since node assets can change between versionsInstall or update to the release you used, so the setup evaluates the same way
A frame looks different from your viewportFix it locally, upload again and resubmitOpen the scene on the server and fix it where it renders
You have a deadline and need to know when rendering starts and endsJobs join the farm’s queue, so the start time depends on how busy the farm is; many farms sell higher-priority plans to start soonerThe server runs only your job from the moment it boots, so you control when rendering starts and can time the whole job
Note: A comparison of how the two farm models work for this task, not a speed test.

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

iRender
Works 1:1 like your own PC: we keep your setup, you just get more GPUs
IaaS render farm
Your workstationscene.c4d · .blend · .hip1 GPUYour iRender serverscene.c4d · .blend · .hipup to 8 GPUs=same setupWindows or Ubuntu desktopYour software, in the version you chooseYour plugins and scriptsYour licensesYour scene and render settings, unchanged1 GPUGPU power: the only difference1, 2, 4 or 8 × RTX 5090 / 4090✓ Only the GPU count changes: open your scene and render the way you do at home
Same on both machinesTip: upload the full project folder with relative paths so textures are found
  1. Upload first. Put the .c4d file and its assets on iRender Drive before you start a server; transfer and storage are free.
  2. 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.
  3. Check the setup. Scrub the timeline and confirm the animation evaluates the same way as on your PC; cache any simulation.
  4. Render a test frame. Check the Redshift log for all GPUs and the detail at final resolution.
  5. 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 spirangle?

A spiral with straight sides that winds inward around a polygon, like a quilled paper coil.

2. How is the spirangle built in Scene Nodes?

Vectors from each vertex to the polygon centre are split into equal steps, and step i of every vertex is joined in order, lap by lap.

3. Why inset and delete at the start?

To separate the faces of the mesh so each polygon gets its own spirangle.

4. What does the Loop input control?

How many steps each vertex-to-centre vector is divided into, which sets how many laps the spiral has.

5. Why are neighbouring spirals joined into one line?

Because the points of all polygons are appended into one list; an Erase Elements node fixes it.

6. How do you animate the strips?

With the Trim Spline Modifier, which draws only part of each spline.

7. How do the lines become paper?

Extrude Line and Thicken give each spline height and thickness.

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.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, , , , , , ,

Linh Nguyen

Linh Nguyen works in customer support at iRender, helping artists render Blender and Houdini projects on multi-GPU servers. She has written more than 300 articles for the iRender blog, covering Blender, Houdini and practical GPU rendering.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →