Laser Scan Effect in Cinema 4D with Scene Nodes: Procedural Setup (2026)
A laser scan effect, where beams run from a moving point to a band of polygons on a model, can be built fully procedurally in Cinema 4D Scene Nodes instead of MoGraph. The selection updates on its own as the target or the model moves.
- Direction: the vector between the global matrices of the model and a Target null feeds the custom axis of a Select Facing node.
- Band of polygons: store the facing selection, shrink it, store again, and keep the difference as a third selection.
- Lines: Polygon Info gives the centre of each polygon in the band; Build Array pairs each centre with the target position and Assemble Spline draws the beams.
- Control: a condition with Append Element decides which polygons actually fire a beam.
- Render: give the splines thickness for Redshift, then render the animation on one or several GPUs.
The laser scan look, with beams sweeping over a face or a product, is a classic motion design effect, and in Cinema 4D it is usually built with MoGraph tools. Our tutorial takes a different route and builds it entirely in Scene Nodes, which gives a clean procedural setup that reacts to movement and is easy to adjust.
This guide walks through the node chain in the same order as the video, explains what each node contributes, and shows how to think about the selections that decide where the beams start.
Checked against the Maxon Cinema 4D help pages for Scene Nodes, the Node Editor and the Select Facing node, and the Redshift documentation on mesh topics, November 2026.
The full tutorial runs 10:32. Chapters: 0:00 intro, 0:43 initial setup and selection, 5:45 laser spline and condition control, 9:29 wrap-up.
Why Scene Nodes instead of MoGraph?
Scene Nodes let you build geometry, selections and modelling functions from nodes, including functions that are hard or impossible to reach with ordinary objects (Maxon: Scene Nodes Introduction). For a laser scan that matters because the effect is really a chain of calculations: find the polygons that face a point, keep a band of them, and draw a line from each one to that point. In nodes, every step stays live, so when the Target moves the selection and the beams update without keyframes or caches.
The trade-off is the learning curve. Maxon notes that the Scene Node Editor is aimed at users with good 3D and technical knowledge (Maxon: The Node Editor). If you have not used Scene Nodes before, keep the Node Editor open next to the viewport and test each node as you add it.
The node chain at a glance
The whole setup is one graph. The figure draws it the way it looks in the Node Editor, simplified to the nodes that matter.
How to read the figure. Follow the wires from left to right. The orange nodes turn the bust and the Target null into one direction (target position minus bust position) and feed it into the Axis port of Select Facing. The blue nodes keep the polygons that face that direction (selection 1), shrink them (selection 2) and store the difference as selection 3. The dashed wire carries selection 3 down to the green row, which reads it back, gets each polygon centre, pairs it with the target position, keeps only the pairs that pass the condition and assembles them into splines.
1. Bring the objects into Scene Nodes
- Start with the model (a Male Bust in the video) and a Null object named Target.
- Create an Object Group and open the Scene Node workspace.
- Use Object Link inputs to bring the original objects into the node graph.
- Add a Children Operation node so the graph can handle several objects.
2. Select the polygons that face the target
Add a Select Facing node with the type set to Polygon and the axis set to Custom. Maxon describes it as selecting polygons by normal direction with tolerance controls (Maxon: Select Facing). For the custom axis, use the vector between the global matrices of the two objects, that is the target position minus the model position, and create the ports you need to wire it in.
Name the result 1 and give it a material so you can see it. When you move the Target or the model, the selected area follows automatically.
Turn the area into a band
- Shrink Selection node to offset the selection inward.
- Store Selection node to save the shrunk result as 2.
- A second Store Selection node that saves the difference between 1 and 2 as 3.
How to read the figure. The blue arc is everything that faces the target (selection 1). The grey arc is the same area shrunk inward (selection 2). What is left between them, the two ends of the band where the green lines start, is selection 3. Only those polygons send beams, which is why the effect reads as a scan line along the edge of the lit area instead of a solid cone.
3. Draw the laser lines
- Use a Select node to read back selection 3.
- Add a Polygon Info node to get the centre position of each selected polygon.
- Feed those centres and the Target position into a Build Array node. Each centre is paired with the target.
- Use an Assemble Spline node to turn the pairs into spline segments. At this point every polygon in the band is connected to the Target, wherever it moves.
Control which polygons fire a beam
Connecting every polygon looks busy. The tutorial adds a condition and uses an Append Element node to collect only the positions that pass it from the Build Array. The video shows the exact condition on screen; the idea is that any test on a polygon (its index, its distance to the target, or a random value) can thin out the beams. Preview the result and adjust until the scan reads clearly.
How to read the figure. Left to right, this is the data at each stage of step 3. Polygon Info gives one point per selected polygon. Build Array puts each of those points next to the Target position, so Assemble Spline can draw one segment per pair: that is your laser beam. The last panel shows why the video adds a condition: keeping, for example, every third index gives a cleaner scan. Any test you like (index, distance, random value) works the same way.
4. Render the beams with Redshift
Splines have no thickness on their own. To render the beams, either sweep them with a small profile or let Redshift render the curves directly through a Redshift Object tag; the Redshift documentation covers both meshes and Cinema 4D curves and splines under its mesh topics (Redshift: Mesh Topics). An emissive material on thin beams, plus a little bloom in post, gives the classic laser look.
Because the setup is procedural, the node graph is evaluated for each frame. For long animations, render a short range first and check that the beams update as expected before you send the full shot. Redshift can then render the frames on every GPU in the machine; each card needs enough VRAM for the scene, because memory is not combined across GPUs (Maxon support).
Laser scan checklist
Check these points before you render the animation.
SaaS or IaaS render farm for Scene Nodes setups?
A Scene Nodes setup is stored in the .c4d file, so any farm with a compatible Cinema 4D version renders it the same way. The difference is version matching and how quickly you can fix a node graph that behaves differently at render time.
SaaS or IaaS for Scene Nodes scenes
How each farm model fits a procedural Cinema 4D scene built in Scene Nodes.
| 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 |
| Your node graph 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 graph evaluates the same way |
| A frame looks different from your viewport | Fix the graph locally, upload again and resubmit | Open the Node Editor 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 debug the node graph 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 graph in if needed. Your server image keeps the change.
- Check the graph. Open the Node Editor, scrub the timeline and confirm the beams follow the Target.
- Render a test frame. Check the Redshift log for all GPUs and the beam 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 laser scan effect in Cinema 4D?
You can build it with MoGraph, or procedurally in Scene Nodes: select the polygons that face a target, keep a band of them, and draw a spline from each polygon centre to the target. The node version updates on its own when the target moves.
2. What does the Select Facing node do?
It selects polygons by the direction their normals face. With the axis set to Custom, you can feed it the direction from your model to a target object.
3. How do I get only a thin band of polygons?
Store the facing selection, shrink it with a Shrink Selection node, store the result, then store the difference between the two. That difference is the band.
4. How are the laser lines created?
A Polygon Info node gives the centre of each selected polygon. A Build Array node pairs each centre with the target position, and an Assemble Spline node turns the pairs into spline segments.
5. How do I reduce the number of beams?
Add a condition and use an Append Element node to collect only the positions that pass it. Any test on the polygon, such as its index, distance or a random value, can thin the beams.
6. How do I render splines in Redshift?
Give them thickness with a Sweep, or let Redshift render them as curves through a Redshift Object tag. An emissive material gives the laser look.
7. Is this effect possible without Scene Nodes?
Yes. MoGraph tools can create a similar laser scan. Scene Nodes give a fully procedural version that reacts to movement without extra setup.
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.




