Plexus Effect in Cinema 4D with the Constellation Node and Particles (2026)
The plexus look, points joined by thin lines into a glowing web, can be built natively in Cinema 4D: a particle point cloud emitted from a mesh, then connected with the Constellation generator from Scene Nodes.
- Base mesh: scale, subdivide and triangulate the model for an even point distribution.
- Point cloud: a Mesh Emitter in Shot mode with 7,500 particles, Noise distribution and speed 0.
- Motion: Turbulence (33%, Aerodynamic Wind), Friction (60) and Flock (cohesion 0, separation about 2 cm).
- Control: Surface Attract (Attract, 50 cm) with a Collider tag, a keyframed Linear Field for the reveal and a Color Mapper.
- Plexus: the Constellation generator with the Particle Group as point source; reduce Search Distance to about 15 cm and limit links in the Restrict tab.
The plexus effect is one of the most recognisable looks in motion graphics, from tech-style animations to abstract visuals. Houdini, Blender and Cinema 4D can all build it. Our tutorial does it in Cinema 4D with the particle system and the Constellation generator from Scene Nodes, which keeps the whole setup procedural.
This guide follows the video, gives the values used, and explains how the connection settings change the look, which is where most of the art direction happens.
Checked against the Maxon Cinema 4D help pages for the particle system, Mesh Emitter, Surface Attract and the Constellation generator, November 2026.
The full tutorial runs 9:08. Chapters: 0:00 intro, 1:00 base mesh and point cloud, 5:19 Constellation generator, 8:02 wrap-up.
What you need
The point cloud uses the particle system introduced in Cinema 4D 2024.4 (Maxon: Particle Simulations – An Introduction). The connections come from the Constellation generator, a node-based asset capsule that Maxon describes as similar to the Atom Array generator but with more settings, and able to read the positions of a particle group or a clone distribution (Maxon: Constellation). Use a current Cinema 4D release that includes it.
The build order at a glance
Three stages take you from a model to a finished plexus. The figure shows the same point cloud at each stage.
How to read the figure. Panel 1 is the point cloud: 7,500 particles in the video (fewer here) emitted on the bust with zero speed, so they keep its shape. Panel 2 adds motion: Turbulence and Friction make the points drift, and the keyframed Linear Field (red) decides where the drift has started, so the shape breaks up from one side. Panel 3 is the Constellation generator reading the Particle Group: every pair of points closer than the Search Distance gets a line, which turns the cloud into a plexus.
1. Prepare the base mesh
Start with a model (a Male Bust in the video). Scale it to fit the frame, subdivide it and triangulate it. A denser, even mesh gives the emitter a cleaner surface, so the point cloud has no obvious gaps or clusters.
2. Build the point cloud with particles
There are many ways to make a point cloud in Cinema 4D; the tutorial uses the particle system because it is easy to animate.
- Create a Mesh Emitter with the bust as geometry. Maxon describes it as emitting from the points, surface or volume of any geometry (Maxon: Mesh Emitter).
- Set the emission mode to Shot, the count to 7,500 and the distribution to Noise.
- Set the speed to 0 cm and leave the rest at defaults, so the points start on the surface.
3. Add motion that stays readable
- Turbulence Force: scale 33%, mode Aerodynamic Wind, for natural variation.
- Friction Force at strength 60, because the particles spread too quickly without it.
- Flock modifier with cohesion strength 0 and separation radius about 2 cm, so the points stay apart instead of clumping.
- Field Condition with a Surface Attract modifier (mode Attract, radius 50 cm) and a Collider tag on the mesh, so the points do not leave the surface at once. Maxon notes that in Attract mode the surface pulls nearby particles to their closest surface position (Maxon: Surface Attract settings).
- Linear Field with keyframed position to control how the point cloud spreads over time.
- Color Mapper to colour the whole system.
How to read the figure. All the numbers from steps 2 to 4 in one place, laid out the way you will find them in the Object Manager and the attribute panels. Build the tree from top to bottom and copy the values; the badges show which step each one comes from. If the points fly off the bust at the start, check that the Collider tag is on the mesh and that Surface Attract sits inside the Field Condition.
4. Connect the points with the Constellation generator
Add the Constellation generator and set the Particle Group as its Point Source. The plexus appears straight away. The rest is art direction:
- Search Distance: if the structure looks too dense, reduce it. The video uses about 15 cm.
- Point Radius, Connection Radius and Connection Length in their tabs shape the dots and lines.
- Colour the connections to match your style.
- Restrict tab: raise or lower the number of connections per point to control complexity.
How to read the figure. Both panels use the same 70 points. On the left every pair closer than a large distance is linked, and the web turns into a grey mass. On the right the distance is about half, and the lines read as a plexus with visible structure. The number of links grows much faster than the distance, which is why small changes to Search Distance make a big visual difference and also change render cost.
Render a dense plexus on several GPUs
A plexus with thousands of points can produce tens of thousands of lines, and each line is geometry. Before a long render:
- Cache the particles so every frame, and every machine if you split the range, sees the same cloud.
- Watch the connection count. Search Distance and the Restrict tab affect render memory as much as the look.
- Plan VRAM per card. Redshift can use every GPU in the machine, but each card holds the whole scene; memory is not combined (Maxon support).
Plexus checklist
Check these settings before caching and rendering the plexus.
SaaS or IaaS render farm for plexus and particle scenes?
Both farm models render the same frames if the particles are cached with the scene. The difference is in iteration: plexus looks are tuned by eye, and every change to Search Distance or the Restrict tab changes both the look and the render cost.
SaaS or IaaS for plexus scenes
How each farm model fits a Cinema 4D plexus built with particles and the Constellation generator.
| Your situation | SaaS render farm | IaaS render farm (iRender) |
|---|---|---|
| The look is approved and the particles are cached | A good fit: upload the scene and cache, the farm renders the frames | Works too; you open the scene and render it yourself |
| You are still tuning Search Distance or connection counts | Each change means fixing it locally, uploading again and resubmitting | Change it on the server, render a test frame and compare in minutes |
| Your scene relies on a recent Constellation asset | Check that the farm runs the same Cinema 4D release | Update Cinema 4D to the release you used; your server image keeps it |
| 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 look is final and the farm runs your Cinema 4D version, a SaaS farm saves you the machine work. If you are still tuning connections by eye, a server you control keeps the loop short.
A test workflow on an iRender server
- Upload first. Put the .c4d file and any cache on iRender Drive before you start a server; transfer and storage are free.
- Pick a server. Cinema 4D and Redshift are pre-installed. Check the version against the one you built the scene in.
- Cache on the server. Play the simulation and cache the particles.
- Render a test frame. Check the Redshift log for all GPUs and the line thickness 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. How do you make a plexus effect in Cinema 4D?
Emit a point cloud from a mesh with the particle system, then add the Constellation generator and set the Particle Group as its Point Source. It connects nearby points with lines.
2. What is the Constellation generator?
A node-based asset capsule in Cinema 4D that connects points of a geometry, a particle group or a clone distribution. Maxon describes it as similar to the Atom Array generator but with more settings.
3. Why does my plexus look too dense?
Search Distance is too large, so too many pairs are linked. Reduce it (the tutorial uses about 15 cm) or limit the connections per point in the Restrict tab.
4. Why use particles instead of the mesh points?
Particles can be animated with forces, kept on the surface with Surface Attract and revealed with a Linear Field, which makes the point cloud far more flexible than fixed vertices.
5. How do I stop the points from clumping together?
Add a Flock modifier with cohesion set to 0 and a small separation radius, around 2 cm in the tutorial.
6. How do I keep the points close to the model?
Use a Field Condition with a Surface Attract modifier in Attract mode and put a Collider tag on the mesh.
7. Do I need X-Particles or Houdini for a plexus?
No. The tutorial uses only Cinema 4D’s particle system and the Constellation generator, plus Redshift for rendering.
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.




