Place Repeating Architectural Elements on Points with Blender Geometry Nodes

What will you learn in this guide?

You’ll use the Instance on Points node in Blender Geometry Nodes to place a repeating architectural element on points. Examples include facade components, light fixtures, or furniture repeated throughout a layout. The basic idea is to create instances on points rather than add multiple real copies of the same geometry to the scene.

The guide also covers what the Selection, Rotation, and Scale inputs do; how attributes from points can be passed to instances; and how to derive rotation from direction vectors. The goal isn’t to set up a specific project file, but to adapt the node’s workflow to architectural visualization scenarios.

Requirements

You’ll need Blender and a file that can use Geometry Nodes. The source documents come from the “latest” pages of Blender’s online manual. As those pages don’t specify a particular Blender version, no version requirement is stated here. The manual also doesn’t specify account or license requirements.

You’ll also need geometry to instance and geometry containing the points on which to create the instances. Points can come from a mesh, a point cloud, or curve control points. Instance on Points works with geometry types that have a Point domain. In an architectural model, the target might be existing points along a facade line or within a furniture layout; the node doesn’t create these points automatically, but uses points on the supplied geometry.

Step by step: placing elements on points

1. Identify the point geometry and the instance geometry. Connect the geometry carrying the instance positions to the Points input of Instance on Points, and connect the element you want to repeat to the Instance input. For example, you could use the points of a mesh for Points and a single lamp geometry for Instance. Each point’s position affects the transform of the resulting instance.

2. Control which points receive instances. The Selection input determines whether an instance is created for each point. Instances are created at points where the value is true; points where it’s false are skipped. This lets you place elements on a subset of points rather than all of them. Since the source manual doesn’t explain how to generate Selection values, this guide doesn’t prescribe a specific selection node or method.

3. Set rotation and scale. The Rotation input determines each instance’s Euler rotation, while Scale determines its size. Use these inputs to give all instances the same orientation and size, if that’s what you need. You can also provide suitable values when you want the orientation or scale to vary from point to point. The manual notes that rotation outputs from nodes such as Distribute Points on Faces and Curve to Points can be used for Rotation; setting them up is outside the scope of this guide.

4. Align orientation to the normal. The Normal node returns a direction vector for each element, depending on the evaluated domain, and its output is a normalized unit vector. On surfaces, this vector points in the face’s “up” direction. You can use Align Rotation to Vector to use this direction when generating rotation. Keep in mind that the Normal result depends on the geometry type and domain; a mesh vertex normal is the average of the normals of its connected faces.

5. Select from a list of instances. If the Instance input contains multiple instances, the Pick Instances option lets you select one from the list for each point, rather than adding all the geometry to every point. This option uses the Instance Index input and is described in the manual as intended especially for use with the Collection Info Node. By default, the index uses the point’s ID value, or its index if there is no ID. Negative values or values greater than the number of items in the list wrap around to the other end of the list.

6. Keep the output instanced or convert it to objects. The node’s Instances output returns instances. Instance-based results let the scene use the same geometry many times without repeatedly duplicating its data. When needed, the Make Instances Real operator can create objects from the instances produced by this node. Consider this option only if you actually need to convert them into objects.

Where does it fit into architectural and archviz workflows?

Instancing can be especially useful when working with large numbers of repeated elements, such as facade modules, lights, groups of chairs, or layouts made up of similar components. Using references to the same geometry, rather than duplicating the source geometry for every point, makes it possible to add instances efficiently. However, no specific performance or memory savings are provided for real project scenes; results should be evaluated based on the geometry and scene setup.

The key points to check in the workflow are the geometry connected to the Points input and the Rotation values. For example, when using curve control points, the Normal output depends on the curve’s evaluated direction and twist method. With NURBS and Bézier curves, the Normal node’s values at control points may not match the visible evaluated points. In this case, the manual notes that Resample Curve can be used to create control points for each evaluated point.

Common issues

• Expecting an instance at every point: Points where Selection is false are skipped. First check that this input isn’t preventing point-by-point instancing.

• Unexpected instance orientations: The Normal output varies depending on the geometry type and domain. With curves, control points can differ from visible evaluated points.

• Seeing all the geometry instead of one instance from a list: If Pick Instances is disabled, all the geometry in the Instance input is added to every selected point. If you need to select from a list, consider using Pick Instances and Instance Index.

• Unable to instance a light object directly: The manual says the Object Info Node can be used for object types without geometry, such as lights. It also notes that some objects, such as Metaballs, aren’t supported for instancing.

Next steps

Start with a small number of points and simple geometry, then change the Selection, Rotation, and Scale inputs one at a time to see how each affects the placement. If you need to control orientation, try the Normal output and Align Rotation to Vector. Remember that nested instancing can occur if the point geometry already contains instances: new instances are affected by the transforms of their parent instances as well as their own.

Attributes from the point geometry can be used in the instance domain of the created instances. If the point geometry has an ID attribute, it’s transferred to the resulting instances. This can help you track how point data relates to instances in more advanced setups.

Sources and license

This tutorial was adapted into Turkish based on the “Instance on Points Node” and “Normal Node” documents in the Blender Manual. Both sources are licensed under CC BY-SA 4.0. The example explanation and architectural application context were created originally.