My most used workflow is to receive 3D data mostly as STEP files (which originate from different CAD systems, such as Solidworks, Catia, Think3, ProE) and importing them into Rhino for Mac.
I then have to re-order items into a strict standard layer structure to prepare the data for work.
During import I often end up with having Block definitions in my Rhino file.
I do not like block definitions, as they have messed with me separating certain subjects onto different layers and that way having caught me badly on few occasions.
How does the process work, that triggers these block definitions?
Are these already defined within the STEP file data originating from the CAD system of creation?
Are these blocks created during Rhino’s import?
Can I define a different standard behavior that say these are not created as block definitions but instead behave differently (separate on unique layers)?
These blocks do cause me now a bit of extra work.
If there are only a handful of blocks created this is no big deal, I will just:
- select all block items
- explode block definition
- delete block definitions (unfortunately this can only be done manually one at a time in the block properties window (right pane, bottom) as I see it.
When I receive complex files it can be that I have dozens and dozens of block definitions in a single file which causes a big amount of redundant preparation work.
So far I have not used block definitions with 3D data (I do understand and see their use when working in 2D drawings though, which I do not do in Rhino).
If I could entirely prevent blocks in 3D work with Rhino, it would be fantastic.
How can I handle this more efficiently?