Great to see you last week. I’m following up with an issue we encountered in migrating panels from Rhino/GH to Revit. The script is similar to that of those posted to instantiate families in Revit. Screenshot Below:
The workflow we’ve opted out for is to categorise the rhino geometry by its material for revit. This would then be referenced to instantiate a family based on Material in the revit file. While doing this, we noticed that some of the geometry refused to transfer over to the revit space. See examples below:
Normally the rejected geometry has to do with breps not closing properly. If we can look at the geometry directly we are trying to learn what gets rejected by Revit.
Can you send me the GH definition you are using. I ran the attached definition and made a big single family Generic Model type and everything came in perfect.
I used a very similar definition to the one you’ve provided. Using the new attached definition you’ve sent, i’m still getting the same error. See screenshots here:
You can still see on the top row that the blades are missing. I’ve also tried to just set the missing blade as an individual brep and it seems to recognise it as a normal object.
As a summary - i’m taking the slab geometry and existing facade from revit to give me a position in Rhino. That coordinate is then used to translate the facade modelled in Rhino to then instantiate families in Revit.
Thanks Scott.
Is it worthwhile implementing a series of components to rebuild the geometry via GH as a standard practice then? Is that a better workflow moving forward?
Nice find. This seems like the standard limitation in Revit of edges that cannot be less then 1 mm. I am looking at thread and see if it helps in this case: Zero-Length Edges