Changeset View
Standalone View
manual/editors/node_editor/node_parts.rst
| ************* | |||||
| Node Parts | |||||
| ************* | |||||
| This page explains the standard parts of any type (Material, Composting, Material) of node. | |||||
gandalf3: Mentions material twice. I'd suggest just skipping the list of types here entirely. If really… | |||||
| .. figure:: /images/editors_nodeeditor_nodeparts.png | |||||
Done Inline ActionsImage seems to big. You can crop it and scale it down, instead if setting width. Blendify: Image seems to big. You can crop it and scale it down, instead if setting width. | |||||
| Title | |||||
Done Inline ActionsThat brings up the question, should we have a standard for screenshots of nodes? gandalf3: That brings up the question, should we have a standard for screenshots of nodes?
e.g. always… | |||||
Done Inline ActionsI was using 150px however anything in the 150-200px range seems good for nodes Blendify: I was using 150px however anything in the 150-200px range seems good for nodes | |||||
gandalf3Unsubmitted Not Done Inline ActionsI wrote up a proposal here: T46543#342614 gandalf3: I wrote up a proposal here: T46543#342614 | |||||
| ----- | |||||
| The *Title* shows the name/type of the node. It can be overridden by changing the value of Label in the *Node* section of the *Properties Panel* :kbd:`N`. | |||||
| On the left side of the title is the *collapse toggle* which can be used to collapse the node this can also be done with :kbd:`H`. | |||||
Done Inline ActionsOne = typo? gandalf3: One = typo?
If it's not already mentioned elsewhere, perhaps you could mention H here (the… | |||||
Done Inline ActionsI will mention it GiantCowFIlms: I will mention it | |||||
| .. figure:: /images/editors_nodeeditor_nodecollapsed.png | |||||
| How the node shows above appears when collapsed. | |||||
| Sockets | |||||
| ------- | |||||
Done Inline ActionsWatch spacing Blendify: Watch spacing | |||||
| The *Sockets* input and output values from the node. They appear as little yellow circles. Unused sockets can be hidden with :kbd:`Ctrl-H`. There are two kinds of sockets: | |||||
| Inputs | |||||
| """""" | |||||
| The *Inputs* are located on bottom left side of the node, and provide the data the node needs to perform its function. | |||||
Done Inline ActionsPrefer not to make title apart of the sentence , just include the word twice. Same goes for next section. campbellbarton: Prefer not to make title apart of the sentence , just include the word twice. Same goes for… | |||||
Not Done Inline ActionsI recently remember reading that it was supposed to be a part of the sentence, has this changed? GiantCowFIlms: I recently remember reading that it was supposed to be a part of the sentence, has this changed? | |||||
| Each input socket, except for the green shader input, when disconnected, has a default value which can be edited via a color, numeric, or vector interface input. | |||||
| In the screen shot of the node above, the second color option is set by a color interface input. | |||||
| Outputs | |||||
| """"""" | |||||
| The *Outputs* are located on the top right side of the node, and can be connected to the input of nodes further down the node tree. | |||||
| Each socket is color-coded depending on what type of data it handles. | |||||
| Color (Yellow) | |||||
| Indicates that **color** information needs to be input or will be output from the node. | |||||
| This may or may not include an alpha channel. | |||||
| Numeric (Grey) | |||||
| Indicates values (**numeric**) information. It can either be a single numerical value or a so-called "value map". | |||||
| (You can think of a value map as a grayscale-map where the different amount of bright/dark reflects the value for | |||||
| each point.) If a single value is used as an input for a "value map" socket, all points of the map are set to this | |||||
| same value. Common use: Alpha maps and value options for a node. | |||||
| Vector (Blue) | |||||
| Indicates **vector/coordinate/normal** information. | |||||
| Shader (Green) | |||||
| Used for **shaders** in :doc:`Cycles </render/cycles/index>` | |||||
Done Inline ActionsSuggest include useful info as follows. Color (Yellow)
....
Numeric (Grey)
....
Vector (Blue)
....
Shader (Green)
....You can see more easily. at a glance whats what. campbellbarton: Suggest include useful info as follows.
Color (Yellow)
.... | |||||
Done Inline ActionsThis was copied form the previous page, but I will fix it. GiantCowFIlms: This was copied form the previous page, but I will fix it. | |||||
| Preview | |||||
| ------- | |||||
| On some nodes this shows a preview image of how the output data for a certain channel will appear. Usually it shows color data. | |||||
| The preview can be toggled using the icon on the very top right hand corner of the node, next to the title. | |||||
| .. figure:: /images/editors_nodeeditor_nodepreviewless.png | |||||
Done Inline ActionsSame here however this image is not as bad Blendify: Same here however this image is not as bad | |||||
| How the node shows above appears without the preview. | |||||
| Controls | |||||
| -------- | |||||
| The controls provide different options for each node. These vary greatly and are specific to each node. | |||||
| Some nodes may have no such options at all. | |||||
gandalf3Unsubmitted Done Inline ActionsWhat are the "controls"? What is this section referring to? gandalf3: What are the "controls"? What is this section referring to? | |||||
Mentions material twice. I'd suggest just skipping the list of types here entirely. If really needed, link to http://blender.org/manual/editors/node_editor/introduction.html#node-tree-types instead to minimize the number of pages which will need updating when more node types are added.