Open topic with navigation

The Node Editor

Contents of this page


The Node Editor has different modes - depending on which Node types are used - that switch automatically. By default, the Node Editor opens in Scene mode, where you can create Node-based setups that generate custom geometry, for example. Collaboration between classic objects and Node-based functions is also possible in this mode, but requires small detours via additional Nodes.
If you activate a Node-based material, the Node Editor automatically switches to Material mode, in which only the Nodes that can be used for materials can be used. Finally, the Node Editor's Capsule mode automatically activates when you select an Asset Construction group. These special Nodes can be used directly in the Object Manager, where they can also be grouped directly with classic objects for example. You can find an example here.
You will find hints here and there in the following text that this or that function only works in certain modes.


General

Sample representation of the Node Editor in Material mode.

For faster access to all Assets, Capsules and Nodes, the Asset Browser can also be displayed on the left side of the Node Editor. In addition, the Attribute Manager can also be displayed on the right edge of the Node Editor to allow the configuration of selected Nodes directly in the Node Editor area. This is especially helpful when using a full-screen or floating Node Editor window, and when configuring Node materials to shorten mouse travel when editing values. The icons for showing and hiding the Asset Browser and Attribute Manager can be found in the upper right corner of the Node Editor.


The Asset Browser and Attribute Manager can be displayed at the sides of the Node Editor.


The following applies to the Node Editor ("Material" mode):

The Node Editor is the central instance when creating and editing material Nodes (hereafter simply referred to as "Nodes"). To create and edit Nodes, a Node-based material must be selected. The Node Editor always displays the currently selected Node material.

It should be noted at the outset that Nodes are a not entirely straightforward subject and can only be used in their full breadth with a good degree of knowledge of shading and rendering techniques in general. However, many things are also quite simple, for example, by using one of the pre-made materials, such as the Redshift Standard Material, which you can operate almost as easily as a conventional material .

The general data flow is always from left to right. On the far right, for Redshift Materials, everything always flows into an Output Node (without this, there is no functioning material; there is always only one Output Node per material).

To open the Node Editor, you have several options:

A description of all Redshift Material Nodes can be found here. You can also read the description of the Nodes in the slightly older Cinema 4D material system here.


The following applies to the Node Editor ("Scene" mode):

The content of the Node Editor is not assigned to a special element (like the material Node Editor is assigned to a Node material), but is embedded in the scene itself. Therefore, the last, outputting Node with its output "Op Output" must always be connected to the Scene Node that is already present by default, otherwise no geometry will be generated.

Note that the Scene Node Editor is intended more for advanced users and can be used in its full breadth only with a good level of 3D knowledge and technical savvy. For a brief introduction, see Scene Nodes Introduction.

You open the Scene Node Editor by calling the "Node Editor" command (In the main menu under "Window").

Also note some special functionalities of the Scene Node Editor described here further down the page.

As was the case with the Node Materials at the time, the Scene Node Editor was also equipped with many additional, specific Nodes. Some Nodes (such as the Math Nodes) are available as a feature in both the Material Node Editor and the Scene Node Editor. You can find all Scene Nodes described under The Individual Assets.

For the display of the geometry generated by the Scene Node Editor there are some special view settings in the Project Settings (see Nodes).

Note:Also note the Nodes Layout (see top right of the program window under Layouts), which provides a interface layout optimized for working with Nodes.


The following applies to the Node Editor ("Capsule" mode):

This mode is even more special than the previous two modes, because it is automatically activated when a Node is dragged or selected from the Asset Construction Nodes group, for example, to the Object Manager. These Nodes form the basis for the creation of Asset Capsules, with which you can, for example, create your own objects, selection methods, deformers or modeling commands with Nodes and, among other things, combine them directly in the Object Manager with classic objects. Since these Nodes function like a group, the Node Editor automatically displays the contents of the selected Asset Construction Node. However, if a conversion to an Asset has already been performed, the Capsule mode is enabled, but the content of the Asset can no longer be displayed directly in the Node Editor. To do this, the Asset must first be converted back to a group, for example.

The content of the Node Editor is not assigned to a special element (like the Material Node Editor is assigned to a Node material), but is embedded in the scene itself. Therefore the last, outputting Node with its output "Op Output" must always be connected to the Scene Node, otherwise no geometry will be generated.


The Node View

Navigation:

You can navigate in the Node view as you are used to from the Editor and other managers, using the following hotkeys (see also commands in the "View" menu):

If you have shown the Navigator area at the bottom right of the Node Editor (this can be shown via "Show Navigator" in the "View" menu, among other things), this can also be used for navigation. To do this, simply click on the location within the Navigator that you want to be centered in the Node Editor.

The Node Editor itself offers a similar simplification of the Node representation when zooming out from a Node setup. In the process, the details of the Nodes and also their labels are continuously reduced and finally, in the case of strong reduction, also completely hidden. Thus, even with scaled-down setups, it is still easy to see which Nodes were used and how they are connected to each other. The following sequence of images shows this effect.


This sequence of images shows, from top to bottom, the automatic reduction of details on zoomed-out Node-based setups.


Creating Nodes

For example, you can create Nodes as follows (by dragging and dropping, double-clicking, etc.):


Node Presets

The preset system allows you to save settings, e.g. for tags, objects, color gradients, brush tips or even Nodes, so that you can quickly access them again at any time. Presets can be set as default to be called automatically when an object or e.g. Node is called. Otherwise, these presets are managed in the Asset Browser and can be viewed there at any time. Further explanation of the preset system can be found here.


As is known from objects, the settings of Nodes can also be managed via presets. This allows quick access to proven settings, e.g. for different materials, especially when using Material Nodes.

Especially when configuring Redshift Materials, you will notice that identical Nodes are used again and again, but with customized settings. For example, consider the Pyro Volume Node, which controls the display of flames, explosions, or smoke. If you have found settings there that you like, e.g. for displaying a candle flame, simply use the Preset menu in the upper right corner of the Attribute Manager to have a new preset saved there. Note that this menu is not available in the Attribute Manager of the Node Editor, but only in the Attribute Manager of the Cinema 4D layout.

The following options are available in the menu:


Dialog for saving presets

All presets are stored in the Asset Browser and can be viewed there after calling up the Preset tab. Here you can also delete unnecessary presets or rename them. You can find corresponding functions in the context menu that opens after right-clicking on a preset. In addition, presets can still be defined as Defaults afterwards, in case you forget to activate that option when saving a preset. To do this, move the mouse pointer over the icon of a preset in the right pane of the Asset Browser. Two additional icons appear on the logo:


Listing of saved presets in the Asset Browser. Additional options for marking as Favorite or Default appear when the mouse is placed over the icon of a preset.


Moving Nodes

Nodes can be grabbed and moved with the mouse at any time. Several selected Nodes are moved together. If you approach the edges of the Node view while dragging Nodes, the Node view will start scrolling. To select the Nodes, you can draw a selection frame by holding down the left mouse button or simply click on a Node. This can also be combined with the Shift key to select multiple Nodes in succession by clicking on them. If the Ctrl key is held down while clicking on an already selected Node, the Node can be deselected again.


Connecting Nodes and creating Ports

In order for data to flow from one Node to the next, they must be connected: For this purpose, Node outputs (right Node side) of one Node can be linked to Node inputs (left Node side) of another Node. For this:

Dragging a connecting line onto the left or right side of a Node will open a context menu when the mouse button in released in which the desired Connector Port can be selected.


An already existing connection is duplicated by dragging it with the Ctrl key combination and can thus be routed to other ports as well.


The left image shows at the mouse pointer in the Attribute Manager one of the circular connection icons behind one of the Node parameters. Ctrl-click on it to automatically add the corresponding input port to the Node (if it is not already visible).

When connecting ports, the following also applies:


Optimize Connections

When connecting ports, connection lines may intersect or pass through other Nodes. This can negatively affect the readability of a Node-based setup. We can therefore also run connections via a so-called Wire Rerouters. The advantage can be seen in the following pictures.


In this example, the connection for the color value is partially obscured by a Node.

To improve the readability and clarity of the setup, connecting lines can be additionally subdivided. Similar to adding a new point to a linear spline, this allows the course of the connecting wire to be changed individually. To do this, simply perform a Shift+Ctrl left-click on the link line that you want to change in the history. In this way, any number of Rerouter points can be created along a connecting line. Wire Rerouters that are no longer needed can be deleted by clicking and pressing the Delete key without removing the connecting line.


If the mouse pointer is placed on a connection with the Shift and Ctrl keys held down additionally, a redirection point appears on the connection line and can be moved there freely. Alternatively, simply Shift+Ctrl-left-click on a link line to directly set a Wire Rerouter.

A Wire Rerouter can be grabbed and moved directly with the mouse. The course of the connector line can be modified freely. For even more complex courses, additional Rerouters can be added on the same connection wire.


The Rerouter can be moved directly with the mouse to influence the course of the connecting line individually. In this example, this can avoid the overlap between the connection and the Node.

This option makes especially horizontally running Node setups clearer, as the coming pictures show.


The more complex Node setups become, the more masking between Nodes and connecting lines can occur. In this example, for example, it is not possible to see directly how the connections between the three mathematical Nodes in the middle of the setup run.


The use of Wire Rerouters makes the setup clearer.

The Rerouters can be used not only to form the connecting lines, but also provide the data themselves, which are transmitted via the connecting line. They can therefore also be used as branch points of a connection, as the following example shows.


Here, a Rerouter was used to improve the clarity of the Node graph.

If the cursor is moved in the vicinity of a Wire Rerouter, two port points will be displayed, from which a new connection can be dragged when clicked upon.


At a Rerouter, additional ports become visible when the mouse approaches.

By linking the ports on a Wire Rerouter to other Node inputs, the Rerouter can be used like an output port.


A Rerouter can be used like a port and use additional connection lines.

Wire Rerouters can be duplicated via Ctrl-Drag&Drop or also dragged directly from the Utility category of the Nodes in the Asset Browser into the Node Editor and thus created independently of an already existing connection. If a connecting line is then drawn from such an independent Rerouter to an input port, the freestanding Wire Rerouter can be used like a Value Node. So you can then select the Rerouter by clicking on it and use the Attribute Manager to enter a value that should then be forwarded to the connected Nodes.

This function can also be very helpful for creating order in a Node graph, because Rerouters also have Basic settings in the Attribute Manager, which can be used, for example, to store a comment on a value used.


An already existing Wire Rerouter can be duplicated e.g. via Ctrl-Drag&Drop and placed anywhere in the Node Editor. If such a free Wire  Rerouter is then connected to a Node input, the Rerouter can be used like a Value Node to enter a value.


2024

Use floating inputs and outputs

When you work in an Asset or group, there are inputs and outputs on the left and right, respectively, that allow the Asset or group to communicate with other Nodes or components outside. For Assets, such inputs can also be used, for example, to transmit individual user data to a Node setup.
With more extensive Node-based graphs, this can lead to long connections again, if, for example, Nodes at the right end of the graph still have to access the values from the group inputs. With Floating IO Nodes this problem can be solved easily, because any inputs and outputs to Assets or groups can thus also be placed directly as Nodes within the graph, i.e., where these values are needed.
To do this, simply drag the name for instance of an input port from the left boundary of a group or Asset by dragging and dropping it into the graph. A new Node is automatically created, which now offers this input as a port. The following image shows an example of this.


In the input area of a group or Asset (see the light gray area on the left edge of the Node Editor) there can be different input ports. If you want to read out the value of one of these inputs directly in the Node graph without having to make an extra connection to the corresponding input port, Floating IO Nodes can be used for this purpose. In this example above, such a Node was created for the Asset's Global Object Matrix input and placed in the lower part of the graph. It is also possible to use several Floating IO Nodes of the same or different input ports in the Node graph without any problems.

The same principle works for the outputs. Dragging the corresponding port names from the right column (output side of the group or Asset) into the graph also creates Floating IO Nodes, which now have corresponding inputs. The only difference to the inputs is that there may only be one Floating IO Node per group output. Otherwise, there would be the danger that several, possibly different values are sent to the same output, which of course must not be the case.


Selecting Nodes

You can select Nodes by rectangle selection (simply draw a rectangle in the Node Editor starting in the empty space by holding the left mouse button ) or by clicking on a Node. As always, the Shift (add to selection) and Ctrl (remove from selection) keys work. In the Edit menu you will find some more selection commands (like Select Connected).

Selected Nodes display their settings in the Attribute Manager and the Info pane. This also applies to Wire Rerouters.


Deleting Nodes

Selected Nodes can be deleted by pressing the Backspace or Delete key. This also works with Wire Rerouters.


Node Editor header

You will find the following elements at the very top of the Node View (from left to right):


The Navigator

You can find the Navigator at the bottom right of the Node View. It is a scaled-down version of the entire, current Node graph and is used for orientation and quick navigation in complex Node setups. The light gray rectangle shows the visible section of the Node View. You can move this section by clicking in the Navigator and dragging with the mouse button pressed. This allows quick navigation to other areas.
By simply clicking in the Navigator, the corresponding area is displayed centered in the Node Editor.

The following Nodes are displayed in particular:


Group Nodes are always displayed in two colors, divided diagonally. On the top left, the Node's own color is used, and on the bottom right, a reddish hue, as shown in the left half of the figure above. If the group is selected, its representation in the Navigator will get a yellow color, as it can be seen on the right.


The input and output group areas

You will find 2 dark stripes on the left ("Input") and right ("Output") side of the Node View (if ports leading to the outside have already been created). You can lead out connections/ports by dropping a new connection in an empty area of the Node View.

This makes little sense for individual Nodes, but if you nest groups, for example, you can use this to create a port that appears as a group port (as shown below in the figure on the right). I.e., even with a group within a group, you can feed a particular Node port at the lowest level from the outside (or feed it as an output to the outside).


Node ports in groups can be routed to the outside.

When dropping a connection in the empty space, a small menu opens (see Figure below left) with the following entries:

Parts of the functionality just described (create inputs) can also be done via port context menu using command.


General information about Nodes

Node structure and display types (it is also possible to display only connected ports).

The central component of a Node system is - logically - the Node. A Node has inputs into which data flows from other Nodes, which are then specifically processed by the Node and flow out as results at its outputs. Inputs and outputs have ports that can be used to establish connections to other Nodes. The following applies in principle: An input port can have only one connection, while an output port can have any number of connections.

Nodes can be grabbed at the left and right side and widened or pulled narrower.

A Node is divided into an upper and a lower area:


Upper area

Above the Node is the Node name. If you have renamed the Node in the "Base" tab, both your individual name and the original name will be displayed. The latter so that you always know which specific Node it is. You will then also find it under this name in the Help. The white colored name can also be changed by double-clicking on it.

In the Node top area there is - for Nodes where it makes sense - the constantly updated Node preview at the very top, i.e., when the settings of feeding Nodes change, this preview is also updated. You show and hide the preview with the small icon (2. from left). For this there are also commands available (see above)
Since the calculation of this preview also takes up computing time, you can also hide it by default. You can find the option Preview for New Nodes in the Node Editor Preferences for this purpose.

Below the preview, on the left, is the Solo mode switch (see Solo), provided the Node supports previews, which is not the case for Scene Nodes, for example. To the right is the preview icon mentioned above.

Clicking on the folder Icon - this is visible only for group Nodes - the group content is displayed in the Node View (double-clicking on the Node does the same).

The display mode icon on the far right can be used to toggle through the different port display modes, just like the 3 port commands do.

Below the icon row there is a color bar whose color can be freely defined with Color ("Base" tab). You can then find specific Nodes more easily. By default, some Node types are already assigned a color, but this can be changed at any time.


Subsection

In the sub area you will find input ports on the left side and output ports on the right side, each with its name. Ports can be hidden and their order can be changed by moving them. Note that not all input ports are necessarily listed in the Node itself. These can then be displayed via context menu.

Certain Nodes (such as the Layer Node) even have expandable and collapsible port groups for each layer.

Ports have a certain color depending on the data type they process, and sometimes they have different shapes (also see next paragraph).

Ports can be selected (with the usual Shift and Ctrl keys to add to or exclude from the selection) to apply certain commands to them (see Node menu or context menu).

Finally, there are also so-called variadic inputs or outputs on some Nodes. This means that any number of these ports can be present. A classic example of this is the Children inputs on a Scene Node. The required number of these ports can be set individually using the Add Children and Remove Children buttons, which can be found in the Node's Basic settings in the Attribute Manager. This is even faster if you place the mouse pointer to the right of the name of these inputs on the Node. A plus symbol will then appear there next to the subobject group entry, so that you can add new inputs of this type directly in the Node Editor by simply clicking on them. If you place the mouse pointer next to the ports below, a red x icon will appear. Clicking on it removes this port from the Node again.


The number of variadic ports can be set directly on the Node with mouse clicks on the + and x buttons. Otherwise, you can also use the Add Children or Remove Children buttons in the Node's Basic Settings for this purpose.


Data types and colors

On the left is the Scene Node of a cube base object on the right is a color Layer Node from the Redshift Node material system.

Inputs and outputs are color-coded. The data types expected or output there are indicated by the coloring. The main types here are:

As known from XPresso, it is also possible to connect inputs and outputs of different types. As a rule, a meaningful conversion of the data types then takes place. For example, a texture can also be linked to an input for floating point values. The RGB values of the texture are then automatically converted to brightness values. This way you can also use color textures to control e.g. the Roughness of a "BSDF" layer or you can use a brightness gradient to control a floating point or integer value. Such conversions of data types are indicated at the receiving Node by an additional dot at the corresponding input.


Loop synchronization

Loops play an important role in programming and also in the use of Nodes, because they allow a complete Node graph or even only a part of the setup to be run multiple times during an update cycle.
You can often think of a loop as a fixed number of numerical values that are output one after the other, for example, as a sequence 0,1,2,3,4. These values can then be included in a position calculation, for example, which is then passed to an object. For each numerical value, an object copy is automatically created in your scene.
The following image shows an example of this.


Example of linear distribution of object copies placed centered around the origin.

Nodes, such as the Area Node, which can be used to define loops, offer ports marked with a curly bracket. This allows Nodes of this type to communicate and synchronize with each other. This allows a sequence to be defined within the Node graph in which calculations take place.
In the example abov, the Range Node outputs a sequence of numbers between 0 and 10, which is multiplied by a fixed value to calculate different positions along the X-axis, which will then be transferred to objects.
To ensure that the positions are always calculated centered depending on the range output, a Summary Node in Flow mode calculates an average value of all position values. This calculation must be performed first so that the Subtract Node can access the final result of this calculation. For this to work, the bracket ports of the Range and Summary Nodes will be connected. The symbols on these ports form a frame with an open and a closed curly bracket, indicating that this area - including the enclosed arithmetic Node - is to be treated separately from the rest of the Node graph.
However, the bracket ports can also be used in a staggered manner to implement nested loop passes, as in the next example.


Range Nodes can be used to output ranges of numbers one after the other. The bracket ports can also be used to link several of these Nodes to create nested loops. For each output number of the left Range Node, the complete value range of the second Range Node is output.

In the example above, two Range Nodes are used one after the other. By connecting the bracket ports, these Nodes communicate with each other and synchronize the output of your values. Whenever the left Range Node outputs a new value, the right Range Node will run through all the values defined in it and output them one after the other. In this way, it is very easy to create regular grids for position values, for example, or to traverse UV coordinates. The X or U values will then be calculated by the first Range Node, for example, and the Y or V values by the second. In these cases, all bracket ports show only open curly braces. The subsequent Nodes are equally dependent on both Range Nodes.
Generally, these connections between Nodes used for synchronization are displayed in blue color and the ports that output a sequence of values also appear in blue color.


Context menu

Right-clicking on a Node/Port opens an extensive context menu consisting mainly of commands from the Node Editor menu. These are described elsewhere. Not described there are these:

2024

Output geometry

This command is only available if the Node provides a Geometry output and if it is located within a group that has a Geometry output. By calling up this command, an automatic connection will be established between the Geometry output of the Node and the Geometry output of the group. As the command can also be called up using the shortcut Q when a Node is selected, it is possible to quickly extract geometry from an asset construction group, for example, in order to be able to directly examine the geometry calculations up to this Node. You can find more information on this in the discussion of the assets on this page.
An existing connection to the Geometry output of a group can also be removed by calling up the command again.

Toggle Node Type

Herewith corresponding Nodes (e.g. geometry base objects) can be switched from base Node to OP Node - and vice versa.

Add Input

For a Node, not all inputs listed in the Attribute Manager need to be listed as ports. Sometimes only the most important input ports are shown. If you call Add Input, all hidden ports will be listed here. If you select one, this input port is shown again (with All all input ports are made visible).

This menu item is not available if all input ports are shown.

Add Output

Normally all outputs are listed. However, if you have hidden outputs (e.g. using the Remove Unused Ports command), you can make them visible again by selecting an output port listed here.

Connect Node

This entry only appears when right-clicking on a port that is not yet connected. A list will then appear from which you can select a Node to link. If there are several output ports per Node, move the mouse to the small black arrow and the output ports to be selected will be displayed. In addition to the complete Asset list, the first entry here is "Existing Nodes", which lists Nodes that are included in the current Node view. In addition, there is the entry Group: Add New Output here, with which you can lead a port out of a group (see Input and Output group areas).

Note that this list is dynamically generated and suggests only matching Nodes.

Replacing Nodes

This replaces the "feeding" Node for the current connected input port with one selectable from a list. Note that here the complete Node chain at the Node to be replaced (i.e., feeding it) is deleted. This only applies to Nodes to be fed: Nodes hanging on their output port are unaffected.

Textures

Here all loaded textures are listed, from which you select one, which is then introduced into the Input port with an Image or Texture Node. This command is available only when using the Material mode in the Node Editor.

Load textures

This command opens a file selection dialog, with which you select a bitmap or a video, which is then introduced with an Image or Texture Node into the input port. This command is available only when using the Material mode in the Node Editor.

Remove port instance

Some Nodes, such as the Redshift Ramp Node, offer you this command. You can use it to delete elements such as layers or Nodes.
Since these are again variadic ports, you can however also edit the number of these ports directly at the Node with the mouse. If the mouse is placed to the right of a variadic group port (e.g. next to Ramp for a Redshift Ramp Node), a plus symbol appears there, which can be used to add additional Nodes in the gradient of the Ramp. If the cursor is placed next to these ports, a cross symbol (x) appears instead, which can also be used to remove individual ports.


Variadic ports can be added or deleted directly on the Node.

Remove port

Use this command to hide selected ports. This works only with unconnected ports. The hidden port then appears in the list just described under Add Input (and can thus be shown again).

Note also the command Show All Ports and the next two commands described there. This is a different functionality of displaying or not displaying ports.

Comment...

This command appears only when the context menu for a Node is opened and enables the Display Comment option in the Node's Basic Settings (or the Display Comment option for Redshift Material Nodes). This allows the text input of a comment directly under the Node. This can be very helpful to keep track of more complex Node graphs and, for example, to describe the function of individual sections of the graph in this way. Invoking this command again will also hide the comment if needed.

Color

This entry appears only when right-clicking on a Node and allows both selecting one of the default colors for the different Node categories or assigning an individual color by opening a color picker. The corresponding color is used to color the title line of the Node.

Port Inspector / Data Inspector

Details about these two debugging tools can be found here. These functions allow you to directly read the values provided by ports, making it easier to find miscalculations in your graph, for example.

Reset to Default

Most of the parameters have a preset value that is predefined at Node recreation. With this command - listed only if the Node is not connected - you reset any values that may have been adjusted to this default value.

Port out

Calling this command (only useful if the Node View shows the contents of a group) creates a connection to the outside or to the parent hierarchy. See also The input and output group areas.

Copy Value

Paste Value

This allows you to copy values/types of individual ports into the buffer (for a port with integer value 4, for example, it looks like this: int64:4). With Paste Value these can be inserted for other selected ports. As far as possible, data types are converted in the process.

Copy Type

This command copies a data type (for a port with integer value 4, this would be int64, for example. Of course, this makes little sense for such simple data types. However, since it is possible to create extremely complex data types (e.g. an array collection with different data types as output by Distribution Scene Nodes), you can save quite a bit of time by simply copying the data type and pasting it back in the appropriate place. For example, in a Compose Container Node, where you can also define data types, click on the button at the far right of Data Type and select Edit DataType... and copy the data type into it.

Solo port (output only)

You can turn on solo functionality for Material Nodes. If this Node has multiple outputs, one of them must be defined as a Solo port. That's what you do with this option.

Set as Preview Port (output only)

In the upper area of a Material Node you will find the Node preview. If a Node now has several outputs, this option can be used to define which output is to be displayed there.


Connections

To connect one Node port to another, proceed as described here.

Connections can also be selected, and as (almost) always Shift and Ctrl can be held down to add to or exclude from the selection (rectangle selections also work). What can be done with selected connections? They can be deleted e.g. with the known keys or edited via context menu with some commands described below (here only the commands not yet described elsewhere).

Remove Connection

Deletes the selected connections.

Mute Wire

Muted connections are shown with a dashed line. Here, values are not taken from the previously arranged Node, but from those defined in the Attribute Manager. This allows connections to be temporarily deactivated, e.g. for test reasons.


Other Node Editor components

The icons located in the upper right corner

You will find these icons at the top right of the Node Editor, described from left to right:


The connection icon

The big innovation compared to the old Attribute Manager are the link fields, which have been replaced by the connection icon. Node inputs can either be fed with values by simply entering values in the parameter fields or - and this is new - connect Node inputs with the outputs of other Nodes, i.e., create a link (i.e., what Nodes are all about).

Click on the connection icon to the right of the parameter name and select any Node from the "Connect Node" context menu to connect it to the clicked input (of course, you can also simply connect the ports in the Node View). The selected Node is created and linked:


By the way, bitmaps can always be dragged from outside Cinema 4D anywhere onto a parameter (incl. parameter name, connection icon and GUI element) to link the corresponding parameter by means of an Image Node.

As soon as a parameter is connected with another Node, the following applies:

So the animation icon shows dependencies in the animation and XPresso context, while the connection icon symbolizes dependencies in the shading and renderer context.

The connection icon can assume these 3 states:


When you click on a connection icon, the following commands are offered, most of which you already know from the Port context menu. So the connection icon also provides similar functionality that can be accessed by right-clicking on a port in the Node View.

Only the connection icon's own commands are described below.

Add Layer

In the layer Node, for example, you will find this command. The Node to be selected is then linked by means of a new layer.

Copy

This can be used to copy the connected output port to the clipboard and use...

Paste (Link)

...be connected to another input port. This means that several inputs can be linked to the same output.

Paste (Duplicate)

This command connects the output port located in the clipboard with the clicked input. In contrast to the previous command, a duplicate of the whole - feeding - Node is created.

Remove

This is used to disconnect the input port.

Mute Port

Hereby the connection is held, but nothing comes through the "hose" anymore. Instead, the value set in the Attribute Manager is taken as input. Call the command again to turn the "tap" back on.

Show in Node Editor

Displays the corresponding Nodes/Ports in the Node Editor. Alternatively, the connection icon can be clicked by holding down the Ctrl key.

This allows you, for example, to quickly associate multiple parameters selected in the Attribute Manager with Nodes in the Node Editor.

Show Subchannels

Some Nodes like the Layer Node or the Gradient offer you this mode. Activate this to display, for example, the layer settings as parameters that can be animated or also controlled by the connection icon. In addition, the input parameters of the feeding Node can be shown when you activate on one of the layers. In the following example, these would be the inputs of the "Circle" Node:


For the Gradient Node (click a handle and click one of the child connection icons to invoke the command), the parameters of all Nodes are listed.

Call the command again to switch back to the previous mode.

Inherit Interface

Some Nodes, such as the Distance or Value Node, can adopt the units and parameter representation of the subsequent, connected Node for input ports.


The Info Area

With multiple port selection it is also possible to compare the values.

At the bottom left you will find the scalable Info Area, which gives you some info for selected Nodes, connections and ports.

These are for Nodes:

For connections, these are additional:

For ports, these are additional:


Material Node Example Scene

The following material was created entirely with Nodes, using no bitmap as texture.


Load the following scene:

You can start to see here what is possible with Nodes. Right-click on the material and select Node Editor to take a look inside the Node graph. Note the "Plaid" Group Node, this hides more Node networks.


Features of the Scene Node Editor

Differing from the above descriptions, there are some peculiarities in the Scene Node Editor:

If you search for "Oil Tank" in the Asset Browser, for example, you will now only get 1 hit, unlike older Cinema 4D versions. This is due to the fact that not all Node versions (Base Node, OP Node) are displayed anymore. Instead, drag the one Oil Tank into the Node Editor or directly into the Object Manager. The Oil Tank is then evaluated as a Base Node, Op Node, or Asset Capsule. You can switch between Base and Op Nodes in the Node Editor using the context menu command Toggle Node Type.