Moving the conversation from There is a block definition on layer X, delete it before deleting layer…
A solution that we’ve been working toward in that thread for bringing in nested assemblies from STEP files, and representing them in Rhino such that:
- Individual parts can be edited in Rhino simply.
- Unnecessary parts and subassemblies can be easily deleted
- The model can be exported back to STEP without losing any of the assembly structure
The strategy is to:
- read in assemblies as layers, with subassemblies on nested layers.
- Each assembly has a corresponding Named CPlane to mark its insertion location.
- Parts come in as blocks.
- ALL geometry lives on the Block Objects layer.
Here’s a model that demonstrates my prowess as a mechanical engineer, product designer, and color coordinator all at the same time:
This is a cabinet assembly with subassemblies:
A description of this assembly:
Cabinetassembly has a
Casepart and two
Doorassembly has a part named
Hingeassembly has three parts:
Hinge Plate 1,
Hinge Plate 2, and
Here are the block definitions, describing the parts. There are no nested blocks.
And, finally, the Named CPlanes, to describe the insertion location of each assembly (I’m not convinced this is the best way to define an assembly insertion point, but it’s workable for this discussion):
Here’s the 3dm file, too:
Cabinet Assembly.3dm.zip (1.0 MB)