Jump to content
  • 1

Rhino Imports need to retain Classification of Rhino Objects


shorter

Question

2 answers to this question

Recommended Posts

  • 0

We are working with a number of companies who prefer to model and coordinate their work with engineers also working in Rhino.  They don't use Revit for obvious reasons.  They could use Vectorworks but most students are born with an inbuilt ability to model in Rhino, it seems.

 

We do indeed separate the rectilinear from curvilinear, by using DWG and allow for the geometry to assume attributes of previously defined Rhino classes.  We do not use DWG for importing the curvy stuff because you know what happens with 3D DWG.  It's the same as the stiff we get from Revit.  Heavily triangulated.  So we prefer the curvy stuff to come from Rhino directly as 3DM.

 

Currently the workflow to import and use 'as found' the Rhino geometry is labourious because we have to classify it ourselves.

 

We would like the workflow to be far more linear.

 

Into a previously configured project template...

 

Pour in one Rhino model

 

Section Rhino model using previously prepared section lines

 

Place section viewport on sheet

 

Render

 

Print/Export/BIM

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...