Rhino.Inside.Civil3D
Embed Rhino and Grasshopper directly inside Civil 3D. Report bugs, request features, and help shape the component library.
Rhino.Inside.Civil3D embeds the full Rhinoceros 3D geometry engine and Grasshopper visual programming environment directly into Autodesk Civil 3D. Developed by Bimorph in official collaboration with Robert McNeel & Associates, this plugin brings computational design workflows to civil engineering.
This category is for reporing bugs, sharing workflows, requesting features, and discussing component development priorities. It is separate from the existing Rhino.Inside.AutoCAD category because Civil 3D introduces a distinct node library (Alignments, Profiles, Corridors, TIN Surfaces, Pipe Networks, and more) that requires its own dedicated component library and domain-specific discussion.
What’s being built
The component library will provide Query, Edit, and Create operations across core Civil 3D objects including: Alignments, Profiles, TIN Surfaces, Corridors (Baselines & Baseline Regions), Feature Lines, COGO Points, Property Sets, Subassemblies, Assemblies, Pipe Networks, Pressure Networks, and TIN Volume Surfaces.
What to post here
-
Bug reports with steps to reproduce (Civil 3D version, Rhino version, sample files where possible)
-
Feature requests - especially which objects and operations you’d prioritise
-
Example workflows and use cases from your projects
-
Questions about component behaviour or workarounds
What not to post here
-
General Rhino or Grasshopper questions unrelated to Civil 3D (use the main Grasshopper category)
-
Rhino.Inside.AutoCAD topics (use the existing AutoCAD category)