Edit
Blocks >
Insert Block Instance
File
Insert
| Toolbar | Menu | Shortcut |
|---|---|---|
|
|
Edit Blocks > Insert Block Instance File Insert |
|
The Insert command inserts an internally stored block object or an external file as a block, group, or individual objects. The Insert command lets you pick a specific insertion point and apply a scale and rotation to the objects when inserting.
Select a block name.
Click the file browser button 
to insert an external file as a block, group, or individual objects.
-Or-
Drag any supported geometry file format from File Explorer, and drop it onto a Rhino viewport. In the dialog box, click Insert file.
Insert options
Lists the names of blocks defined in the model.
Inserts the model as a block instance.
Inserts the model as a group.
Inserts the model as individual geometry objects.
Prompts to pick an insertion point.
Type the x, y, and z coordinates.
Scales the objects.
Prompts to pick a scale.
Sets the same scale for the x, y, and z directions.
Sets a separate scale for each direction.
Rotates the objects.
Prompts to pick a rotation angle.
Sets a rotation angle.
FileClick to insert an external file.
Block Definition Properties
The file name and preview.
If the external file contains linked blocks, these will be inserted.
Inserts geometry into the current file. This will not update if the external file changes.
Inserts geometry into the current file and maintain a link to the external file. Linked geometry can be updated when the external file changes. See: BlockManager. If the external file cannot be located, the geometry is still defined in the current file.
Maintains a link to the external file only. Linked geometry is updated when the external file changes. See: BlockManager. If the external file cannot be located, the geometry will not appear in the current file.
A linked block definition references an external file. Each time a model containing a linked block definition is loaded, Rhino reads the referenced file to create the contents of the linked block definition. When you create a linked block definition, specify one of two linked block definition layer styles.
All layers for the linked block definition are saved in the active model. All layer attributes, including rendering material, can be edited and are saved. For each layer in the linked model, if there is a layer in the current model with a matching short name, that layer is used, otherwise a new layer is created.
The layer tree from the linked model is added to the current model as reference layers under a "grandparent" layer with the same name as the linked file. All of the added layers are reference layers. Only the on/off, locked/unlocked states and the layer color can be modified.
The description attached to the block definition.
The description of the URL.
The URL attached to the block definition.
Check that the URL is valid.
Rhino detects material, environment and texture name conflicts in the following file operations:
When a render content item name already exists in the current model, but the content settings are different, the conflicted item will be imported with "[imported]" appended to its name.
When a conflicted block is inserted, imported, or pasted into a model, you will be asked to resolve the conflict. A block conflict happens when two different blocks use the same name.
The block already defined in the model will be used instead of the block defined in the file being inserted.
All instances of this block in the model will be updated.
The block you are inserting will be renamed as you specify.
The Block Name Conflict dialog box will not be displayed again.
| Toolbar | Menu |
|---|---|
|
|
File Import |
The Import command merges all objects from file into the current model. When you import a file into the current document, the objects of that file are merged into the current document as they are in the other file.
Click the button.
-Or-
Drag any supported geometry file format from File Explorer, and drop it onto a Rhino viewport. In the dialog box, click Import file.
Rhino detects material, environment and texture name conflicts in the following file operations:
When a render content item name already exists in the current model, but the content settings are different, the conflicted item will be imported with "[imported]" appended to its name.
When a conflicted block is inserted, imported, or pasted into a model, you will be asked to resolve the conflict. A block conflict happens when two different blocks use the same name.
The block already defined in the model will be used instead of the block defined in the file being inserted.
All instances of this block in the model will be updated.
The block you are inserting will be renamed as you specify.
The Block Name Conflict dialog box will not be displayed again.
| Toolbar | Menu | Shortcut |
|---|---|---|
|
|
File Open |
Ctrl + O |
The Open command opens a specified Rhino or other supported format file in the current Rhino window.
Click the button.
-Or-
Drag any supported geometry file format from File Explorer, and drop it onto a Rhino viewport. In the dialog box, click Open file.
Paste
Insert objects from the Clipboard.
Work with blocks, groups, and worksessions
Index of import/export file types
Rhino Wiki: Imported and linked block layer names
Rhinoceros 6 © 2010-2020 Robert McNeel & Associates. 11-Nov-2020
