November 14, 2026 Vivian Vu

Circuit Board Animation in Cinema 4D with the Particle Node Modifier (2026)

Executive SummaryExecutive Summary: circuit board animation
Cinema 4D 2025+

A circuit board animation, with lines that grow across a board and turn at right angles, can be built in Cinema 4D with the particle system and a Particle Node Modifier that picks one of four directions for each particle every few frames.

  • Board: a Rectangle in the XZ plane (about 100 cm) extruded 4 cm, with the top polygons stored as a selection.
  • Emission: a Mesh Emitter in Shot mode (about 120 particles, speed 50 cm, direction Normal), a Math manipulation to level them and a Trace to draw the paths.
  • Turns: every 15 frames a Particle Node Modifier maps a Random Field value to plus or minus X or Z and sets a new velocity.
  • Clean-up: field conditions kill paths that run into existing traces and limit where the circuit grows.
  • Final look: sweep the traces, add a Pulse Spline modifier for the wave and colour with a Fracture and Plain Effector, then render in Redshift.

Circuit board animation is a familiar look from After Effects motion design: clean, tech-inspired lines that grow across a surface and turn sharply. It can be recreated in many 3D tools. Our tutorial builds it in Cinema 4D with the particle system and the Particle Node Modifier, which keeps the whole effect procedural and easy to vary.

This guide follows the video step by step and explains the logic that makes particles turn at right angles, which is the part most people get stuck on.

Checked against the Maxon Cinema 4D help pages for the particle system, the Mesh Emitter and the Particle Node Modifier, November 2026.

The full tutorial runs 13:04. Chapters: 0:00 intro, 1:00 base mesh, 2:09 Mesh Emitter and Particle Node Modifier, 9:07 circuit wave, 12:00 wrap-up.

What you need

The effect uses the particle system Maxon introduced in Cinema 4D 2024.4 (Maxon: Particle Simulations – An Introduction) and the Particle Node Modifier, which Maxon’s help documents with examples from the 2025 releases. Use a current Cinema 4D release to follow along. Redshift ships with Cinema 4D and renders the final geometry.

The setup at a glance

The figure shows the scene the way you see it in Cinema 4D: the objects in the Object Manager on the left, and the node graph inside the Particle Node Modifier on the right.

iRender
Circuit board setup: objects and the direction graph
Schematic
Object ManagerRectangle + Extrudeboard, Shell selectionMesh EmitterShot, 120, NormalParticle GroupMathsame heightTracedraws pathsTime ConditionPulse, 15 framesParticle Node Modifiersee graphField ConditionTrace, 1 cmKillField ConditionRandom + RectangleSweep (Trace copy)+ Pulse SplineFracture+ Plain EffectorNode Editor: Particle Node ModifierRandom FieldValueRange MapperIn 0..1Index 0..3SwitchIndex+X-X+Z-ZVectorTransform Vec.VectorDirectionScale VectorDirectionSpeedVelocityParticleVelocityRuns every 15 frames inside the Time Condition; one of four directions per particle.
emissiondirection logicconditionsfinal look
Simplified from the iRender tutorial

How to read the figure. In the Object Manager, the board and the Mesh Emitter create the particles, and everything indented under the Particle Group acts on them: Math levels their height, Trace draws their paths, the Time Condition fires the Particle Node Modifier every 15 frames, and the two Field Conditions kill crossing paths and limit where the circuit grows. The green objects at the bottom build the look you render. The node graph is the heart of the effect: the Random Field value becomes an index from 0 to 3, the Switch turns that index into one of four directions, and Transform Vector and Scale Vector turn it into the particle’s new velocity.

1. Build the board

  1. Create a Rectangle, set the plane to XZ and the size to about 100 cm.
  2. Add an Extrude with a thickness of 4 cm along the Y axis.
  3. In the Extrude’s Selection tab, under Polygon, enable Shell and rename it so you can find it later. This selection marks the top surface the particles start from.

2. Emit and trace the particles

  1. Create a Mesh Emitter with the base mesh as geometry and the polygon selection as the restriction, so particles are born only on the top surface. Maxon describes the Mesh Emitter as emitting from the points, surface or volume of any geometry, restrictable with selections and maps (Maxon: Mesh Emitter).
  2. Set the emission mode to Shot with a count of about 120.
  3. In the Properties tab, set the speed to 50 cm and the direction to Normal.
  4. Add a Trace to draw the path of each particle.
  5. The particles do not start at the same height. Add a Math manipulation to give them the same elevation so the traces lie in one plane.

3. Make the particles turn at right angles

This is the core of the effect. Add a Time Condition set to Pulse with a gap of 15 frames, and inside it a Particle Node Modifier. Maxon explains that this modifier opens as a capsule in the Node Editor so you can write your own node logic that acts on particle properties (Maxon: Particle Node Modifier).

  1. In the modifier’s Field tab, add a Random Field, adjust its noise type, scale and animation speed, and enable Field Value, Color and Direction.
  2. Inside the node space, add a Switch node with the data type set to Vector and define four directions.
  3. Use a Range Mapper to remap the field value into four indices, one for each direction in the Switch.
  4. Combine a Transform Vector and a Scale Vector node to build the final velocity for each particle.
iRender
How the particles draw circuit lines
Schematic
Field value at the particle+X-X+Z-Z01Range Mapper splits 0–1 into 4 indices;Switch turns each index into a direction.Every 15 frames (Time Condition)particle picks a new directionTransform + Scale Vectordirection x speed = new velocityTop view (XZ plane): each segment = one 15-frame pulse
+X-X+Z-Z
Schematic of the logic in the iRender tutorial

How to read the figure. On the left, the field value at each particle falls into one of four bands, and each band is one direction. On the right, a top view of the board: every 15 frames each particle takes the direction its current field value points to, so its trace becomes a chain of straight segments with right-angle turns. Because the Random Field is animated, the choices change over time and the network looks hand-designed rather than repeated.

One performance note from Maxon: nodes in this modifier are evaluated on the CPU, while the other particle modifiers are GPU-accelerated, so the Particle Node Modifier is slower but far more flexible. Keep particle counts moderate while you design.

iRender
The right-angle turn, node by node
Schematic
Field Value (input)Value 0–1Range MapperValueIn 0 → 1Out 0 → 3.99Index 0–3Switch (Vector)Index0: +X1: −X2: +Z3: −ZDirectionTransform VectorVectorVectorScale VectorVectorSpeedVectorVelocityVelocityObject Manager (particles)Mesh Emitter (Shot, ~120)2Time Condition — Pulse, gap 15 f3Particle Node Modifiergraph above3Trace2Top view: one traceEvery 15 frames the TimeCondition runs the graph:the particle picks one offour directions and keepsit until the next pulse.3Inside the Particle Node Modifier (step 3)
choosing the directionoutputresulting trace
Simplified; the four directions shown are an example on the XZ board

How to read the figure. This is the logic of step 3 as it sits in the Node Editor. The Random Field gives each particle a value between 0 and 1; the Range Mapper stretches that to an index from 0 to 3; the Switch node turns the index into one of four directions; and the two vector nodes turn the direction into a velocity. The Time Condition at the bottom is what makes the turns happen in steps: it only runs the modifier every 15 frames, so each particle travels straight in between.

4. Remove overlaps and set the boundary

  • Avoid crossings. Add a Field Condition that uses the original Trace object as the field, set the distance mode to Radius with 1 cm and enable Clip to Shape. Inside this condition, apply a Kill manipulation so paths that run into existing traces stop.
  • Limit the area. A second Field Condition with a Random Field and the original Rectangle defines where the circuit grows.

Play the animation and adjust the parameters to explore different variations of the board.

5. Add the circuit wave and colour

  1. Duplicate the Trace object and put it in a Sweep generator to turn the lines into visible geometry.
  2. Add a Pulse Spline modifier and adjust it to get a moving wave along the circuit.
  3. For colour variation, put the setup in a Fracture object and use a Plain Effector to drive colour across the structure.

An emissive Redshift material on the swept lines gives the glowing look common in this style.

Render the circuit animation on several GPUs

The particle simulation is the slow part to evaluate, especially with the CPU-based Particle Node Modifier, so cache it before a long render. After that the swept traces are ordinary geometry for Redshift, which can render each frame on every GPU in the machine. Each card holds its own copy of the scene, so check VRAM per card, not the total (Maxon support).

Circuit board checklist

Check the scene against this list before caching and rendering.

ChecklistCircuit board animation 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 particle-driven motion design?

Both farm models render the same frames if the particle cache travels with the scene. The difference is how you handle evaluation time and the many small changes motion design usually needs before a shot is approved.

Farm modelFor this task

SaaS or IaaS for particle motion design

How each farm model fits a Cinema 4D particle setup driven by a Particle Node Modifier.

Your situationSaaS render farmIaaS render farm (iRender)
The cache is final and the look is approvedA good fit: upload the scene and cache, the farm renders the framesWorks too; you open the scene and render it yourself
The client keeps asking for variations of the patternEach variation means re-caching locally, uploading and resubmittingChange the Random Field or pulse on the server, re-cache and render there
The simulation is slow to evaluate on your PCThe farm renders what you send; simulating there depends on its workflowCache on the server, then render from the same drive
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 look is approved and the cache is final, a SaaS farm saves you the machine work. If variations are still coming, a server you control lets you change, re-cache and render in one place.

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 any cache on iRender Drive before you start a server; transfer and storage are free.
  2. Pick a server. Cinema 4D and Redshift are pre-installed. Check that the version matches the one you built the scene in.
  3. Cache on the server. Play the simulation and cache the particles.
  4. Render a test frame. Check the Redshift log for all GPUs and the glow 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. How do you make a circuit board animation in Cinema 4D?

Emit particles from a flat board, trace their paths, and use a Particle Node Modifier inside a pulsed Time Condition to give each particle a new right-angle direction every few frames. Sweep the traces to render them.

2. What is the Particle Node Modifier?

A particle modifier that opens as a capsule in the Node Editor, so you can read and change particle properties with your own node logic. It is evaluated on the CPU, so it is slower than the GPU-accelerated modifiers but much more flexible.

3. How do the particles turn at exactly 90 degrees?

A Range Mapper turns the random field value into one of four indices, and a Switch node maps each index to a direction along plus or minus X or Z. The new velocity is always one of those four directions.

4. Why do my traces start at different heights?

Particles emitted from the mesh do not share one height. Add a Math manipulation that sets the same elevation for all of them.

5. How do I stop circuit lines from crossing?

Add a Field Condition that uses the Trace object as the field with a 1 cm radius and Clip to Shape, and put a Kill manipulation inside it. Paths that reach an existing trace stop there.

6. How do I render the traced lines?

Duplicate the Trace and put it in a Sweep to create geometry. An emissive material in Redshift gives the glowing circuit look.

7. Which Cinema 4D version do I need?

A version with the particle system introduced in 2024.4 and the Particle Node Modifier. A current release is the safest choice.

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:
, , , , , , ,

Vivian Vu

Vivian Vu has written nearly 40 articles for the iRender blog, covering iRender news, Maya, Blender and real-time 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
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →