Node Editor Menu
Page contents
Note that, depending on the Node Editor, different commands will be available. They are all described here.
Create menu
The Node Commander makes a similar functionality available as in the Content Browser's asset list. You don't have to use the mouse but simply have to press the C key and the list will open. However, the Node Editor must be active. You can also click on the + button in the Node view.
In addition to the functions described for the asset list, the Node Commander also offers the following:
- The ESC key or click outside of the window will close the window (the filter icon order will be saved)
- The TAB key switches from the list to the Filter field
- Shift + TAB switches from the Filter field to the list
If you copy a value to the clipboard using the Copy Value command, the Create Value Node from Clipboard command can be used to create a new Value Node with correctly set values..
This will copy a given port's current data state and fixate it in the Value Node. If the clipboard contains a value that comes from outside of Cinema 4D it will always be read in using the String data type.
Example: You used a classic object node to create geometry in the Node Editor. If you want to place this geometry into a Value Node, first create a Port Inspector for the geometry output (this should link to a Scene Node, otherwise nothing may be output at the port). Then execute the Copy Value command for this port. When the Create Value Node from Clipboard command is called up the complete geometry will be saved in the Value Node with the correct data type. The classic object node can then be deleted.
Creates an empty group for the current Node Material or for the currently active Node setup.
Click on the Folder icon or double-click on the Group Node to open the group.
What is a Group?
Groups are summary, parent Nodes that contain a network of Nodes (and/ or groups as well) The ports of Nodes in these groups can also be propagated outwards in order to feed values from Nodes outside of the group or to access values of Nodes within the group.
Groups can be converted to Assets and passed on.
You can also select multiple Nodes and group them using the following command.
Groups selected Nodes (see also previous command).
Here you will find various Nodes, that, among other things, serve as a basis for the Capsules' settings. This menu is only active if one or more Nodes have already been selected. All Nodes listed here can - similar to groups - contain other Nodes. The selected Nodes will therefore be added to the Node selected here.
Group Nodes As
Here you will find various Nodes that, among other things, serve as the basis for Capsule settings. This menu will only be active if one or more Nodes have already been selected. All Nodes listed here can - similarly to a Group - contain other Nodes. The selected Nodes will therefore be placed into the Node selected here.
Change Group Type To
The commands in this menu are only available if a Group has already been selected. If so, the Group's type can be switched, e.g., from a simple Node Group to an Object Group or Selection Modifier Group.
Ungroups grouped Nodes and deletes the Group Node. Connections are maintained - as well as outwardly, if possible. This also works with the Asset Construction Nodes such as the Mesh Primitive Group.
Edit menu
These are the usual commands with which you can delete changes made in the Attribute Manager or undo/ redo functions. Contrary to the XPresso editor, moving or expanding Nodes is not included for these functions.
Here you can copy selected Nodes to the cache (for Cut, the Nodes will also be deleted) and Pasted in the Node Editor. Existing connections between the selected nodes will also be copied.
Selected Nodes will be duplicated, (including all existing connections).
Alternatively you can Cmd/Ctrl + click on selected nodes and move them. This will duplicate them automatically after the mouse button is released.
Selected Nodes will be deleted. Pressing the Backspace- or Del keys will do the same.
All existing connections at the Input and Output ports of the selected Node will be removed.
Selects all Nodes.
Selects all Nodes connected to the selected Node. This makes it easy to select a series of connected Nodes.
All Nodes that are connected with the Input of the selected Node will be selected.
All Nodes that are connected with the Output of the selected Node will be selected. This selection includes the entire branch of the setup that follows, not only the Nodes that are connected directly. As a rule, this selection will therefore end at the Scene Node of the setup or at the Output Node for a Redshift material.
Deselects all Nodes.
Opens the Material Editor for the material currently displayed in the Node Editor. In principle, the Material Editor has the same settings as the Attribute Manager for a selected material.
This command selects the corresponding Node Material in the Material Manager for the active Node Editor, whose material settings will then be displayed in the Attribute Manager.
Using this command, a Scene Node setup can be converted to a common scene, which primarily offers access to the generated mesh that can in turn be edited using the normal Cinema 4D tools. To do so, open the Scene Nodes Representation: you will find all meshes under the Meshes Null object.
Furthermore, under Hierarchy, you will find all instances that reference the aforementioned meshes, arranged in a correct hierarchy. The hierarchy displayed in the Object Manager is a representation of that defined in the Node Editor.
Why instances? Scene Nodes generate almost all geometry internally as instances and will therefore be shown as such in the Object Manager.
Here you can access specific Preferences settings for the Node Editor.
Shows all Nodes in the Node Editor view. The view will be scaled accordingly.
Selected Nodes will be displayed at the center of the view without changing the zoom factor. For multiple selections, the center of the selected Nodes will be placed at the view's center.
All Nodes will be placed at the center of the view without changing the zoom factor.
Enlarges or reduces the Node Editor view. Using the 2 hotkey and the mouse works faster.
If you have a Node network made up of 376 Nodes, for example, you won't see much detail in the Node Editor view. This command sets the zoom to a quite legible 100%.
Hides or shows the grid in the Node Editor view. Grid snapping works independently of this display.
Enables or disabled grid snapping. If enabled, Node edges will snap to the grid lines.
Shows or hides the Navigator.
. Here you can hide or show the Info Area. The Info Area can also display the IDs of selected Nodes and Assets. The size of the Info Area can be adjusted individually by clicking and dragging at the area's top or right edge.
When working with groups you often have to delve into these, i.e., the Node Editor shows the contents of a given group. Call up this command if you want to move up a level, i.e., out of this group. Alternatively, you can click on a layer to which you want to jump next to the Node path.
This command can be used to display the contents of a selected Group. This also includes traditional Group Nodes as well as most Nodes in the Asset Construction Group, which can also contain Nodes. This command's function reflects the action of clicking on the Node's Folder icon.
This command will let you jump to the next lower layer in the Node path and can be helpful when working with nested groups. The image below shows an example of this. Alternatively you can click directly on the elements of the Node path to jump to another hierarchical level within the setup, or you can click on a Folder icon of the respective Group Node.
On the left you can see the path at the top of the Node Editor that contains the visible Group as well as two additional Groups. Each time The Step Up command is executed, the neighboring component to the right in the Node path will be activated. As you can see on the right, calling up the command once will open the first Group. The complete path will only be made visible if you navigate through all layers by clicking on the Folder icons on the Group Nodes.
Selected or all Nodes will be arranged so they are visible in the current view - compact, arranged in order and positioned horizontally/ vertically:
Before and after the Arrange Selected Nodes command is called up.
All Nodes displayed in the Node Editor will ba arranged according to the previous description.
With this command you can create parameter input ports for all selected ports. See Input and Output Group Area for differences between input and output ports and propagated ports.
Node menu
This command only affects Material Nodes. These commands can be used to show or hide the Node's preview (in the upper area of each Node). The application's Preferences menu has a Material tab in which a default setting defines if the preview for new Node creation should be visible or not. What good does it do to hide the preview since it actually offers valuable information. Well, for very extensive Node networks it can be very computationally intensive to update all previews when changes are made. In such cases it can be useful to hide the preview.
Furthermore, under Hierarchy you will find all instances that link to the previously mentioned meshes, arranged hierarchically. The hierarchy shown in the Object Manager is a representation of what is defined in the Node Editor.
Why instances? Internally, Scene Nodes generate practically all geometry as instances and are therefore displayed accordingly in the Object Manager.
Hide all Ports hides the port area for all selected Nodes, The connections are maintained. This is a purely optical effect, for example, to get a better overview of your setup. Calling up the Show all Ports command will reverse the effect.
Selected ports can also be defined as hidden with the Del key. The Show all Ports command will then not make these visible again. You will have to define the respective port as being visible via the Add Input command.
The function of the following two commands can also simply be accessed for each Node using this icon:
Only the ports with connections will be shown for the selected Node. All others will be hidden. This can be undone using the Show all Ports command.
Several ports such as Op or Matrix can be opened via a predefined Arrow symbol to make additional sub-ports visible. This command closes all opened ports on the selected Nodes so only the top-most port hierarchy remains visible. This effect reflects that of manually clicking on the Arrow icon next to a Port Group.
On the left, for examole, you can see various sub-ports of an opened OP Output on the Mesh Primitive Node. After the command was executed, the Op Port Group on the selected Cube Node was closed automatically.
In the Material Node Editor, the Solo Mode works as follows (Nodes don't necessarily have a preview; these are, for example, useless for Nodes in the Scene Node Editor):
Different Nodes defined as Solo Nodes, rendered texture on a cube.
The enabled Solo Node mode omits all other Nodes. In the Node Editor view and for rendering, only the Nodes fed into the Solo Node and the Solo Node itself will be evaluated and displayed. This is, for example, very useful if your Node preview is too small because you can display or render the effect of individual Nodes at any scale.
Use this command for a selected Node (possibly with a selected output port: see also Solo port) or simply click on the Node's S icon.
Logically, only a single Node can be a Solo Node. To exit the Solo Node function, call up the Set Solo Node / Port command or simply click again on the S icon. A comparable function for Scene Nodes can be found in the Basic settings. The Bypass option makes it possible to deactivate a Node calculation in order to only check the function of the remaining Nodes.
The Start Node works as follows in the Material Node Editor: Node Materials can be made up of very complex networks consisting of hundreds of Nodes. If you want to make minor changes to a material without diving too deeply into the Node Editor, one Node - a single Node per Node Material - can be defined as a Start Node. This Node's inputs (and only this Node's inputs) will be displayed in the Attribute Manager or the Material Editor's Input tab when the material is selected.
If, on the other hand, you only want to display a few ports and you're working with groups, propagate the respective ports from the group and define the Group Node as a Start Node.
Start Nodes will be marked with a green frame if unselected.
In the following example, only the Spiral Node's Arms setting should be displayed as an externally controlled setting. Proceed as follows:
-
Place all Nodes in a group by selecting them and selecting Group Node from the context menu. Open the group (click on the Group Node's Folder icon).
-
Right-click on the Spiral Node's Arms port and select Propagate Port from the context menu.
-
Exit the group by clicking on Node in the Material or Group Name
- Select the Group Node and select Start Node (Node menu)
As soon as you select the Node Material, only the Arm setting will be displayed (image bottom right).
If you now click on the Group Node to select it and select Convert to Asset , the Asset will be created.
The Clear Start Node command removes the Start Node state.
Unused Nodes are Nodes without connections (groups are not included). They therefore serve no purpose and can be deleted using this command.
With this command, the selected Nodes, all ports without a connection will be hidden (these can be right-clicked on and unhidden using the Add Input or Add Output commands).
View menu
If Nodes lie outside of the Node Editor view, these can be shown simultaneously using this command. The view will be scaled accordingly to ensure that all Nodes are displayed.
Asset menu
Details about Assets can be found under Assets.
Similar to Edit Asset, only that a selected asset instance must lie in the node view.
When editing existing Assets, modifications made should be saved using this command. A dialog window will open that you should be familiar with from the Save Asset command (see above). Since the old Asset state is also saved, versioning will be implemented.
When editing existing Assets, a new Asset can be saved without the aforementioned versioning. A dialog window will open that you should be familiar with from the Save Asset command (see above).
Assets are most often created from Group Nodes (an example process is described here).
As soon as this command is called up for a selected Node, a dialog window will open:
Name
Define a name for the Asset. This Asset will appear with this name in the Asset list. This name will also appear in the Info area if you use it in the Node Editor view as an instance (i.e., you drag it from the Asset list into the Node Editor view). Even if you rename the Node, this name will remain unchanged.
Version Info
Assets can have several versions (versioning). Imagine you create an Asset, build a scene with it and save the scene. You then edit the Asset by, for example., changing a color or adding Nodes. If you now save the Asset (Save New Version) you can use the Version Tag to define a version (e.g., 1.1 or Version 2, etc.). The Asset will then contain both the original and the new version.
If you now load the originally saved scene or use the Asset anew, the newest Asset version will be used by default. You can, however, switch between versions in the Asset instance (i.e., the Group Node) at any time:
You can also imagine versioning as follows: Assuming you saved a primitive cube in Cinema 4D R15. A Fillet setting was added in R18. If you load the R15 scene into R18 you often had a compatibility mode that lets you load and older version. If the option is enabled, the cube is loaded without fillets, if disabled, with fillets. Sometimes the cube would be loaded without any prompt regarding its older state. If versioning were applied to primitives, you would be able to switch back-and-forth between versions.
Maxon can update the nodes it supplies in the application via the Online Updater. This is done in a manner that ensure that older scenes remain functional.
What you define here in the Version Info will subsequently appear in the Asset instance as the Asset version name.
ID
This is a unique ID (you don't have to enter anything) is assigned with which an Asset can be clearly identified by the application. This ID - supplemented by a random set of characters - is then displayed in the Info area of the Node Editor when the respective Node is selected.
Database
Assets can be saved in different databases.
Most often, the following will be offered:
- Preferences: Assets will be saved in the default directory userrepository
- Scene: An Asset copy will be copied in the scene file (this also happens if the scene is saved using the Save Project Including Assets option).
- + Databases that are linked in the Preferences menu under Files/ Paths/ Databases. Note that Assets linked as ZIP files in databases cannot be saved in these)
This menu is dynamic and will display all corresponding locations.
Category
If you take a look at the Asset list you will see numerous Assets in the alphabetically arranged categories. You can add categories at any time (these are themselves Assets by the way).
The Asset to be saved will be placed in the selected category. Custom Assets can be dragged and dropped to other categories.
Clicking on OK will save the Asset and add it to the Asset list and will make it visible in the Node Commander where it can be used.
Asset Nodes, which are mostly created from groups, can be converted back to Groups using this command. The Folder icon will then be displayed again.
Opens the groupAlternatively you can double-click on the Group Node to display its contents.
If an asset is encrypted, this command will be grayed out.
Debug Menu
Here, the evaluation of the relative calculation time for all Scene Nodes is calculated. All Nodes will be highlighted in color and a percent value will be displayed beneath the respective Nodes. This percent value shows how much of the overall calculation effort is required by each Node. This information can be very helpful if you want to improve the performance or calculation speed of the setup. Thanks to the Head Map, you can see at a glance which Nodes require the most calculation effort within your setup and where you can optimize. More in-depth information about Heat Maps and how to use them can be foun here.
Note that Redshift Node Materials are not supported by Heat Map evaluation.
Activating the Heat Map will cause the Nodes to be highlighted and a percent value to be displayed beneath each Node.
If the Relative mode is activated for the Heat Map, the percent values and the corresponding Node highlight will be calculated relative to the shown depth of the setup. For example, if you look at the Nodes within a Group, all values will only be based on the Nodes within that Group. If this mode is disabled, all values will be calculated absolutely, i.e., always based on the Nodes within the setup.
If you look at the entire setup as a whole, i.e., in the path set in the Node Editor in which the Scene Node is active, the state of this option does not play a role. The image below shows an example of this.
You can see the entire setup at the top that contains the Geometry Modifier Group. If you display the Nodes within this Group, their evaluation is dependent on the Heat Map (bottom-left the Relative mode; next to it on the right the Absolute mode).
The top part of the image above shows the complete setup. The calculation requirements of the Geometry Modifier Group is shown to be 50% based on the entire setup. In order to find out how this value came to be we will open this Group by clicking on the Folder icon in the Group's header. This can be seen in the image on the bottom-left. The Group contains two Nodes whose Heat Map values add up to 100%. We are in Relative mode here, which takes the currently displayed Nodes into consideration. If the Relative mode is disabled, we would get the result in the image to the right. The Heat Map of the Nodes within the Group will now be evaluated together with the remaining Nodes in the setup. Now we again have a value of about 50% within the Group, which was shown on the top layer of the setup for that Group.
The colored Heat Map and its percent values help to quickly locate parts of the Node setup or Capsule Asset that require more calculation effort. However, percent values alone don't say anything about the time needed for calculation. A cube primitive may show 100% in a simple setup but is in fact calculated very quickly. High percent values alone don't necessarily mean that a setup has to be optimized at that point or that it will take long to calculate.
This command can also be made to output solid time values and statistics for more detailed information. For this, the Heat Map should not be activated first. What this output means in detail as well as information about all debugging tools can be found here .
Ports can be marked for the Data Inspector in order to see the incoming and output values. Also, the values of simple data types can also be displayed with the Port Inspector directly next to the Node in the Node Editor. This marking can be removed again by clicking on the X symbol of the respective Data Inspector icon. Alternatively, this command can be used to remove all existing links from Ports to the Port Inspector at once. To do so, no Nodes have to be selected. More about using Data or Port Inspectors can be foun here.
The Data Inspector can list the values that are output or input at the Ports. Since the Data Inspector is a separate window, it can also be closed at any time and opened again when needed using this command. A newly opened Data Inspector always has the Interactive mode enabled, which means that the data of a selected Port will automatically be displayed. You can find out more about how to use the Data Inspector here.
Ports can be marked for the Debug Menu in order to read incoming and outgoing values. These markings can be deleted by clicking on the X symbol on the respective Debug Menu icon. Alternatively, this command can also be used to delete all existing links to Debug Menu ports at once. No Nodes have to be selected to do so. More information about using the Debug Menu can be found here.
The Debug Menu can list all values that are output or input at ports. Since the Debug Menu is a separate window, it can be closed at any time and opened again when needed. A new Debug Menu will always have Interactive mode enabled, which means that the data of a selected port will automatically be displayed. Here you can find out everything you need to know about using the Debug Menu.
Mode Menu
The Node Editor has various modes that will normally switch automatically- depending on which Node type is being used. If the Scene Manager is activated, for example, the Scene mode will be activated; if a Node Material is activated, the Node Editor will switch to Material mode.
You can also switch manually if you want. You then might have to select the fitting element (e.g., a Node Material).
The third mode is the Capsule mode and will be activated automatically if an element in the Asset Construction Node's group is selected in the Object Manager. The Node Editor will then display the content of the Asset Construction Node as long as it's not an Asset Capsule. If you've already added connections to an element in the Asset Construction Node Group, the Capsule mode will be activated but the content of the Asset cannot be displayed or edited directly in the Node Editor. To do so, the Asset would have to be converted to a Group.