All about Rhino
Everything you need to know about the Rhino-Finch Plug-in
Finch Layers in Rhino
Layer Structure
When you load a Finch project in Rhino, the layer structure for exchanging geometry is automatically imported as well. Make sure to place your geometry on the right layers for Finch to recognize and import everything correctly.
Finch acts as the parent layer and should be left empty.
Below is an overview of the layer structure used:
building mass
Stores closed building masses (mesh, polysrf, extrusion, brep)
centerline
Stores lines which controls the placement of generated corridors.
grid lines
Stores multiple open polylines that affect the Custom Core algorithm
building interior block
Interior parent layer, empty
programs
Stores interior program data / geometry
structure
Stores interior structural data / geometry
custom geometry
Overwriting Layer Geometry
When a different Finch variant is loaded into Rhino, the previous geometry in the Finch layers is overwritten and replaced with the new geometry. The sync does not affect any geometry outside of the Finch parent layer.
Building Location
Updating the plug-in
Plug-in settings
Auto-receive changes
If Auto receive changes from web app is checked, any updates made in Finch will be automatically synced to Rhino. If it is not checked, after working in the web app the Rhino file will need to be synced before making any further edits in Rhino. Otherwise, the Finch and Rhino versions of the project will contain different data and the user will be prompted to choose which version to override when syncing new changes.
Centerline Positioning
If you are uploading or adding a centerline, be sure that it is one joined line that does not intersect itself or stick outside of the building.
Override geometry check
Last updated
