Hi everyone,
Whenever I want to get an element shape, I use the Element.Geometry node (i.e. when I want to get the contour lines of the base area of column). But, I noticed when I execute this node, it takes too long to process (looks like it’s a heavy task to display geometry). I want to verify the following statements.
- Does a script where the node “Element.Geometry” is in visible mode take the same time compared to another that has that node in hidden mode? Do they take the same time?
- Is any workaround to get the Element wireframe lines (like base area) without using that node (geometry)?
Thanks everyone.
It depends on time. Usually the geometry will be calculated in n units of time, and the display will be calculated in an additional n units. Sometimes this happens concurrently though as the display can calculate out of sequence.
Sort of… You can pull the solids instead of the geometry, and then process the data effectively using topology. I covered the specifics of this and some alternative methods for getting to the geometry which may interest you in a recent Dynamo office hour - The Stairry Story - which was posted here: https://m.youtube.com/watch?v=oj7M-F0nkvQ&list=PLdlF7MirPEC2yNFTGymESd3t7Xosfk9c2&index=1
Thanks for replying, but I didn’t quite get it. I’m not such an expert using Revit API.
But it looks like that there is no other wayaround to get an instance geometry without using that Element.Geometry node (that will consume time to get all faces of any element). Too bad.
This is unlikely to be a significant delay processing time wise. Do you have a sample that you can share so we can identify why it’s lagging? Also, any indication of how long this node is taking to execute (the TuneUp view extension can report this for you - available on package manager)?
