Rhino is where a lot of geometry is designed and Revit is where it has to be documented. Moving between them usually means exporting a mesh and losing everything that made the geometry useful. Nexar Plan imports Rhino 8 3DM files and Grasshopper GHX definitions as native Revit elements, and keeps track of what came from where.
Rhino 8 3DM geometry and Grasshopper GHX definitions are both supported. Grasshopper definitions can be parsed, evaluated, or parsed and then evaluated, with a fallback mode for definitions that will not evaluate cleanly. Rhino 8 must be installed for import to be available.
The difference between an import and a conversion is what the geometry becomes. Each Rhino layer is mapped to a Revit category and a representation, so geometry arrives as the right kind of element rather than as an undifferentiated lump.
Imported elements stay linked to the Rhino objects they came from. A sync check reports how many Revit elements are still linked and what has changed, so a revised Rhino file can be synced rather than reimported and re-mapped from scratch. Tracking can be cleared when a link is no longer wanted.
Results are broken down into native elements, loadable and adaptive families, DirectShapes, fallbacks and failures, with a timing breakdown. A conversion that partly failed says so rather than silently producing less than you asked for.
Yes. Rhino 8 must be installed on the same machine; the import tab is disabled without it.
Yes. GHX definitions can be parsed, evaluated, or parsed then evaluated, with a fallback mode for definitions that do not evaluate cleanly.
It falls back to a DirectShape, and the run reports how many elements took that path alongside native elements, families and failures.
Nexar Plan supports Autodesk Revit 2025, 2026 and 2027 on Windows.