URSA

Use Rhino® curves and points to place Autodesk® Revit™ families and adaptive Components

URSA places adaptive components or family instances in Revit using polylines and points exported from Rhino with BEAM.

Polylines and points can be grouped into sets for easier selection with F, and each element can carry its own parameters to drive instance parameters of the placed components in Revit.

When curves or points are created in Rhino, a unique Mark is automatically assigned, which URSA uses to track and update components across Rhino and Revit.

From the URSA panel, you can choose which .beam file to use and what Revit family type to place. Only adaptive components and level-based families are supported.

Since URSA only works with points, lines, and polylines, it is good practice to check your geometry with Rhino’s What command to confirm compatibility.

Placing adaptive components

To place adaptive components, create polylines in Rhino with the same number of vertices as the adaptive points of the target Revit component. If the component requires two points, use a line; if it requires a single point, use a point. Elements that do not match the adaptive component’s structure will be excluded during import.

URSA places the components using the coordinates of the vertices and assigns instance parameters accordingly. These parameters are driven by values you assign to curves or points in Rhino through the Panel, ensuring consistency between Rhino data and Revit components.

Updating components

URSA can update components already placed in Revit by matching their Mark values. This means that even after changes, the correct components are updated instead of duplicated. Marks are generated automatically in Rhino, but they can also be edited manually.

With RAY , adaptive components can be imported back into Rhino with their Marks, modified, and then updated in Revit using URSA.

Placing families

Families can also be placed in projects using points. URSA identifies the closest Revit level below each point’s Z-coordinate and assigns the family to that level, including the proper offset constraint.