Yeah, it’s not bad - but I have to rearrange all these objects by hand, and so having a simpler nested assembly saves me some effort. Plus, since that STEP file was kind of a random smattering of parts, it didn’t make visual sense to me about how things should be arranged.
I see where you’re heading with this. The idea is that the named CPlane marks the insertion point of a subassembly, allowing the subassemblies to be reencoded in the STEP file on export. I’ll have to think more about that - there may be other ways of storing this information in a more durable way. If you imported a model with two subassemblies, and wanted to add a third, I guess you’d duplicate the layer structure, move the objects and the named CPlane around, and export? Clumsy, but workable, maybe.
That seems reasonable to me, too - so there’d really only be one imported layer 5 assembly - v1 with a bunch of objects on it. The bolts would all be named “bolt” instead of “bolt:1” … “bolt:4”.
I’m going to try to put together a Rhino model that looks like a mechanical model with subassemblies next…
@chuck is on vacation for the next couple weeks, so we won’t see any immediate movement.