base-node (.bn) v0.13.1

Idioms

Ways of writing a graph that come back in most libraries of node groups. Each is a paragraph and a graph you can build as it is.

Read an attribute that may be missing#

A named attribute does not exist on every geometry. NamedAttribute says whether it found it: switch to a value of your own when it did not, rather than reading zero.

Offer a choice with a menu#

A Menu input and a MenuSwitch give the user named choices instead of an integer to remember. One menu often chooses where the geometry comes from: the modifier's own, or an object's.

Keep a value across a change of the geometry#

A field is read on the geometry of the node that uses it. To use a value of the geometry as it was before a change (here, the height of each point before the mesh is subdivided), capture it first; this is also shorter than storing a named attribute and reading it back.

Change one part, keep the rest#

SeparateGeometry gives both the part it selects and the rest. Change the first, then join them again.

One seed, several random values#

Two RandomValue nodes with the same seed give the same numbers. Add a different constant to the user's seed for each, so that one seed still changes them all.

A lighter preview in the viewport#

IsViewport is true while Blender draws the viewport and false when it renders: use it to keep the viewport fast and the render detailed.

Say what is wrong#

A Warning node shows its message on the modifier when its condition is true, and passes the condition on: the graph can tell the user and fall back in the same step.

Repeat a step on its own result#

In a repeat zone each turn reads its fields on the geometry the turn before made: here the normals are those of the inflated mesh, not of the first one.

A factor goes from 0 to 1#

An input that weighs or mixes is a factor: say so, and give its range. The modifier then shows a slider that stops at the ends.

Share constants and helpers through a module#

A value used by many graphs (a scale, a unit) is a graph without input; graphs shared by a library go in a module. use brings them by name, and the module's name keeps them apart from the user's own graphs, which prefixes in group names (.MN_, O ) only imitate.