Rhino inside Revit importing nested geometry object type naming bug

Objects imported from Revit are being named as a type in the convention below. Looks like a layer and then guId from revit. It looks likes its a block but it doesn’t show up in the block manager It causes issues further on down in the line.

Simple fix is to just explode this mystery object.

image

Hi Benjamin,

Can you provide your About info and a small example of the Revit Element that is the issue? Thanks

image

I believe it happens when there is a nested family. This then becomes a block, but the block has that naming convention in the type field instead of type block and then a name. The block does not register in the block manager. Exploding, purging and then putting everything on a new layer and deleting the old layers solves the issues. It gets rid of the “ghost” block.

Are you baking the parent or the nested Elements? Are they Shared Families? Please post a small example.

Will try to duplicate and post. I brought geometry in from a Revit family that had nested families. Geometry came in as blocks, named as shown in the screen shot above. The blocks are a new type of block that is hidden, or maybe this a feature I never knew about.

If you try to select these blocks with grasshopper you get the error above.

The reason i ask for an example is there are a lot of ways that families can be setup. If you are in the parent with no geometry & shared nested families you would get an empty block.

Understood, need to recreate the error then will post.