-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Element.Geometry inconsistency #6394
Comments
thanks @rbosborne , looks like this has been the behavior at least since 0.8.2, @aparajit-pratap It looks like Dynamo doesn't like to deal with 2 different situations. One is elliptical extrusions and I think the other issue is conical elements, or maybe a sweep to a point? |
KroNz did you try this on 1.x after We made changes to the cone face converter ? Sent from my iPhone
|
It looks like you are using nested revolved edges (sweeps). There was an earlier issue with them described here: I don't believe that was ever resolved. This is on 0.92 stable: Seems to be a bit better in the 1.0 dailies. Curved faces are still a big challenge: So one way to circumvent this, is to make the curved face inside your family faceted. |
@dimven Thanks for the tips and the issue link. @rbosborne I'm closing this issue as the one that @dimven linked covers it. @mjkkirschner can you please confirm this is the same issue? |
Using 0.9.2. I have lately noticed many elements that are not working with Element.Geometry. Attached is a file containing 3 elements. Only one of the 3 (the rectangular beam) will work with element.geometry in Dynamo. If the rectangular beam is connected and joined to the elliptical column, it will not work with element.geometry.
I have looked at all 3 elements using RevitLookup. For the Rectangular beam, the geometry only shows "Solid". For the Ellipse Column it shows "GeometryInstance" and "Solid". For the cable loop it only shows "GeometryInstance".
I am wondering
Element Geometry fails.zip
The text was updated successfully, but these errors were encountered: