I need some help. I’m trying to reduce the range of the action of a script, focusing only on a portion of the project, in order to reduce the runtime.
I really would like to filter all the elements (already filtered by category and contained in a linked file) that are visible in the active view. I already saw and read lots of similar post but none of the solution founded seems to work.
currently Revit API does not allow this (get link elements from active view)
a workaround is possible with a search for LinkElements by boudingBox or SolidIntersection (CropBox and ViewRange from HostView) without taking into account the different filters that there may be in the view or view template
you can try this node from Data-Shapes
this is great! but if I understood well… it works only with plan views… not with 3D view…
I would have to run the script floor by floor… or does it takes the volume of the section box?
Could it be possible that it doesn’t work if you run this node in a central cloud model with different workset?
If I run it in a deattached model everything is fine without workset…
if I run it in a cloud central model, the filter of elements doesn’t work properly…
Some nodes could be disturbed but I don’t currently have a cloud project and therefore can’t verify that it is working properly.
How do you select the linked document ? Can you show a screenshot with previews enabled under the nodes ?
The script is not compatible with IndependentTag, a workaround will be to collect the physical elements of the linked model (via the script above) then to find the keynote tags attached to them.
as a reminder the script is already a workaround because currently Revit API does not allow get link elements from active view
Thanks for the quick reply.
I adjusted your workaround in order to collect all the pipes from a link model, filter them by a parameter (Revision comment) and place a revision cloud on them. I tried other ways to get them but only yours worked so thank you for that. Every time I run the script on another view or level it refreshes it and removes the already placed clouds from other views. I’d like to keep them. The problem might be from the SpringsUI.Refresh node that I’m using (it’s a bit crashy and weird) but I don’t have another refresh button due to mix of version of dynamo and versions of packages that are barely holding up.
Would a workaround in the python script remove the need for a refresh node?