I have a problem inserting a closed polysurface created in rhino in Revit. I try exporting as a dwg and importing it in a generic model family but when I explode it the object disappeared.
I also tried rhino inside where I see an error of short edges. But how I will find these short edges. It looks fine to me in rhino environment. No naked edges, no manifold edges.
Is there a way inside rhino to find these short edges?
short_edges.3dm (1.1 MB)
99% is human mistake while modeling.
I attached the corrected file which has no problem importing in revit.
I am thinking that even if I don’t need to import a model in Revit, modeling from Revit inside environment, is easier to find when you make a modeling mistake.
In my case, I found one mistake where two endpoints that should have the exact coords, had a distance of 0.00043 m. I know that continue modeling from this point is going to produce more problematic areas.
Is there any plugin in grasshoper, able to find sort edges without modeling from rhino inside?
What i still dont understand is that if i explode the fist model, which i am unable to import in revit, set the tollerance to 0.000001 m, and then join again the result is a closed surf without naked or manifold edges. How its possible? The result should be an open polysurf in this tollerance. Else revit should have no problem importing it.
The model i think is closed polysurf only in 0.001 tolerance.
corrected_model.3dm (1006.3 KB)
Thank you very much.
That’s what I was looking for.
Thank you for sharing this tool. I ran into the same error when sending some geometry to Revit.
However, when I tried using your tool, I got strange results. You can see it reports 4 edges in the panel, but has arrows everywhere in the viewport. If you look at the bottom of my Rhino you will see that I have selected all the geometry, and it is only the polysurfaces you see highlighted. So why are the arrows pointing in empty space?
Is there another way for me to find exactly where those 4 problematic short edges are in the model?
Thank you for your help.
Best
Brian
Can you post the problematic geometry?
Yes, thank you. It is geometry provided by a colleague so I am not as familiar with how it was constructed.
Problem Geometry Short Edges.3dm (1.4 MB)
I’m not seeing the extra error issue. Perhaps download Kike’s definition and try again.
Something like this would work as well…
Reloaded Kike’s definition and it is working, as is the one you offered. Thanks
What is the range of lengths that Revit defines as a short edge? What should I set min edge length to with this tool to filter just the problematic edges for Revit?
They recommend 1/32" but it depends on what situation you are in. You can create smaller, and you can also have conditions that when imported create the small edges.
Thanks, this is useful. What sort of conditions are you thinking of?
The situation is geometry (polysurfaces) being converted to Family Forms and added to a new family.
Attached is a sample of the geometry
ShortEdges.3dm (6.1 MB)
I have set min edge length to just smaller than 1/32":
Here is the result, at all 4 corners:
Closer inspection of one of the problem edges, length command gives me 1/64":
This is a window manufacturer’s rhino model. Is the conclusion, then, that I cannot send this Rhino model through to Revit as Forms in a Family?
Brian
If the translation is erroring out the Family Form component it will need to be simplified.
The revit tolerance thing is really quirky. You can have perfectly good geometry in Revit (by Revit’s rules), send it out with their export and it will come back in with errors.
Sounds like Revit tolerance is going to be a sticking point for these workflows.
I am not getting erroring on the Family Form, but instead on New Component Family. I have also observed a massive Revit slowdown, after sending these windows through into a family. The slowdown seems related to graphics, as it is when zooming in and out of drawings–I think Revit is struggling to calculate the 2d projections of these micro-edges etc.
One bad family can slow up Revit view regen substantially. If the family is saved out is it bigger than 4mb? Ideally you would want all families below 1mb.
I will check the size. Good to know.
In the meantime, for another set of geometry I was able to remove any micro edges (min. edge length of 0.0026 feet, approx. 1/32") and naked edges. Yet I still receive this error:
I can’t understand what this means.
See attached for the grasshopper and rhino files.
24 0731 Naked Edges Problem.gh (13.6 KB)
Naked Edges Problem.3dm (7.8 MB)
Sorry to be dense, but how do I identify the geometric problem with these two beams? I am looking at it with Show Edges, looking for micro edges with Kike’s script, it is a closed polysurface, and a visual inspection shows no weird isocurves suggesting strange geometry.
And how did you identify these two beams? Using the Add Direct Shape error message?
The direct shape is a great tool for a quick check. The beam on the right has highlighted edges, the one on the left gives a complete fail. I can take a closer look later this afternoon at the specific geometry conditions.