Hi ShapeDiver team,
We are building a STEP export for a shelving configurator and would like to preserve its assembly structure and repeated parts.
Our environment:
-
Rhino 8 SR35: 8.35.26251.13001, Windows, .NET 8
-
ShapeDiver plugin: 1.33.0
-
Download Export with STEP Export Options, schema
AP214AutomotiveDesign
Our Grasshopper C# builder creates native Rhino 8 ModelObject blocks / ModelBlockInstance objects containing BReps, including nested block definitions. It does not bake objects or modify the Rhino document. All placements come from a JSON manifest.
The intended hierarchy is:
Configuration → shelf bays / supports → part instances → BRep bodies
When connecting the root Model Block Instance directly to Download Export D, with the standard STEP Export Options connected to O, “Export locally” fails with:
No objects match the types supported by the selected export format.
The configuration exports successfully when the builder outputs the placed BReps directly. However, this loses the intended block-based assembly structure and shared part definitions.
Our inspection of the installed 1.33 SDK suggests that the STEP/STP object-type filter excludes InstanceReference. We tried extending the export options, but script review rejected this and advised us to file a support request. We have removed that workaround and are requesting an officially supported solution.
McNeel describes Rhino blocks and instances being converted to STEP parts and assemblies here.
Is there an approved workflow for exporting Rhino 8 ModelObject block instances to STEP through Download Export?
If this is not currently supported, could you add support for nested assemblies, preserving part and instance names, transforms, colours and references to repeated part definitions where supported by the STEP schema?
Automatic expansion to BReps would resolve the immediate export error, but our main requirement is a STEP file containing selectable parts and a meaningful assembly tree.
Thanks!