-
Notifications
You must be signed in to change notification settings - Fork 3
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
Improvement: Element.Geometry Detail Level #233
Comments
Personally, I'd like a dropdown node for the detail level. And while you're at it please add a |
Interesting, I wasn't aware of this behavior. I had assumed that it took the detail level based on the view settings. We'll take a look |
Thanks for looking into it. I think this would be appreciated by a lot of users. We have grown accustomed to only having Medium, but there are errors there that some might not be aware of (like pulling geometry volumes from Medium - which might not be correct). Category - All Elements of Category - Element.Geometry. No specification of which view here at all since the idea is data mining the entire model (or linked model), not just a specific view. That said, i have tried in the past to get fine and coarse geometry to show in Dynamo using the Revit View settings, but it never worked for me. The only thing that worked was to mod the families and switch the med/fine geometry visibilities. |
Work is being done on this issue now 😊 |
Currently - Element.Geometry pulls the "Medium" level of detail geometry from an object as best I can tell. I think it would be useful to give users the option to get the level of detail geometry they need (for instance - pipe fittings only display as solids in Fine)
So Element.Geometry would have a second input for the desired detail level. This could function either as a single value (much like the bool inputs in many nodes) or take a list input (allowing the user to input a mixed lists of Coarses,Mediums, and Fines that correspond to the desired level of detail of each element in the first input).
The text was updated successfully, but these errors were encountered: