A Guide to Editing Architectural Models with Selection, History, and Blocks in Rhino 8

This guide explores how to use the selection, History, and Block tools in McNeel’s Rhino 8 documentation in an architectural modeling workflow. The aim is to select the right geometry in crowded scenes, track design changes, and manage repeated components more efficiently. The command names and menu paths below are based on information in the Rhino 8 documentation.

1. Choose a selection method that suits the geometry

1. To work with a single object, click it to select it; click an empty area to clear the selection. To add multiple objects, hold Shift while clicking or draw a selection area. To remove an object from the selection, click it with Ctrl (CMD on macOS) or use a window selection.

2. Pay attention to the direction in which you draw a selection window. Dragging from left to right selects objects fully inside the window. Dragging from right to left creates a crossing selection, which includes objects inside the window or intersected by its boundary. When selecting among facade lines, floor plan elements, or furniture groups, this distinction helps reduce the chance of inadvertently selecting nearby geometry.

3. When objects overlap in the viewport, use Rhino’s Selection Menu. Select an object name from the list, or move through the options with the mouse wheel and confirm the current selection with a right-click. This lets you control which object is selected when several occupy the same apparent point.

4. Use Selection Filters when you need to select only specific types. The documentation describes filters for surfaces, curves, meshes, points, and sub-objects. For example, when working with surface edges or mesh faces, narrowing the filter to the relevant type helps exclude other nearby geometry. Sub-objects can be selected with the mouse either before a command starts or while it is running; the Rhino documentation specifies clicking, window selection, or crossing selection with Ctrl (CMD on macOS) + Shift.

2. Use area- and property-based selection

1. Use Lasso to select with a freeform area, or SelBrush to select with a brush stroke. In Lasso, Window mode selects only objects entirely inside the drawn area, while Crossing mode selects objects inside it as well as those intersecting its boundary. SelBrush uses crossing selection by default, capturing objects touched by the brush stroke.

2. Use SelBoundary to select objects within a closed curve used as a selection boundary in the viewport. This command also offers Window and Crossing modes, which select different sets of objects. The Precise option changes how the boundary is evaluated: with Yes, the test is performed in screen space using double-precision floating point; with No, a bitmap selection mask is used. Check this setting when it matters whether objects near the boundary are included in the selection.

3. You can select objects by their properties, not just their visual position. The Rhino documentation lists selection commands for layer, name, object ID, color, material name, and group. For example, use SelLayer to select objects on the same layer, or SelName to find objects with the same name. Select all objects with SelAll or Ctrl+A; clear the selection with SelNone or Esc.

3. Record History selectively

1. Clicking Record History on the status bar enables recording for the current or next command. For continuous recording, right-click the control and enable Always Record History. McNeel generally recommends leaving Record set to No and recording History only for operations that need it; the feature uses resources and can increase the size of saved files.

2. Create an output with a History-enabled command. In the example in the documentation, a surface created with the Loft command updates when the input curves are edited, provided recording and updating are enabled. Other commands that use History include Loft, Sweep1, ExtrudeCrv, Offset, and BooleanUnion. Keep in mind that not every command supports History recording.

3. To preserve the link, don’t delete the parent geometry, directly edit or move the result object, or move the parent and child objects together. Joining objects can also break their History links. If automatic updating is off, you can update the result manually with HistoryUpdate. Use HistoryPurge to remove unneeded records; this action cannot be undone.

4. Turn repeated components into blocks

1. To reuse the same geometry in a model, select the objects and create a block definition with the Block command. The command replaces the selected objects with a block instance, allowing you to create component libraries and update instances by editing the definition. According to the documentation, block instances can reduce model size compared with copying the same geometry.

2. To bring a block definition in from another file, choose Block Instance under the Insert as option in the Insert command. When editing a definition, reusing the same block name is the way to redefine the existing definition. Open the Block Definitions panel with the BlockManager command to view and manage block definitions.

3. Know the link type used for blocks linked to external files. Embedded stores the geometry in the model and does not update when the external file changes. Embedded and Linked keeps the geometry in the model and links it to the external file; the geometry in the model remains usable even if the source file is unavailable. Linked stores only a link to the external file; if the file cannot be found, the geometry is missing from the model.

Common mistakes

Overlooking the direction of a selection window can lead to crossing selection picking up partially intersected objects as well. Leaving History recording on for every command can increase resource use and file size. Directly editing History-linked result geometry or deleting input objects can break the link. With blocks, choosing Linked and then moving or losing access to the external file can leave geometry missing from the model.

Impact on architectural and visualization workflows

These tools can be useful for teams that isolate specific elements in multi-layered plans, manage repeated components such as doors, furniture, or fixtures, and modify input geometry for design alternatives. Blocks make it easier to manage repeated parts, while History links inputs to results for supported commands. However, the resource and file-size costs of History, as well as the external file link type used by blocks, should be taken into account when organizing a project. When sharing work within a team, it is important to check the location of linked files and avoid operations that break History links.