I've recently been told by our new BIM manager that using too many view filters can lead to file performance issues. This was somewhat in response to the argument I was trying to make on not relying on worksets for visibility. I know view filters require some naming conventions and organization in order to keep them all straight, but I've never heard of them actually having any impact on file performance. I'm curious if anyone out there has ever experienced any issues with too many filters?
-
-
I've done projects with 100s of rule based and selection filters and have never noticed any noticeable slow downs because of them. When I did Levi's Stadium there were well over 500 view filters. Like you say, logical naming convention then becomes very importantOriginally posted by chris.macko View Post
I'm retired, if you don't like it, go around! -
I don't have any evidence one way the other concerning view filters and file performance, but I do know from personal experience that using worksets to control visibility in individual views is almost never a good workflow.Comment
-
Every file I've had for the last 6 years has AT LEAST 25 filters in every view, since they are in my view templates that are in my project template.
They may have an effect, but certainly not a bad enough one to warrant not using them. Filters are way better than worksets for visibility.
Takes more effort to set up though. Maybe your bim manager is lazy. Hahaha.Comment
-
defined or in use on a single view?Originally posted by Dave Jones View Post
With no evidence to support my claim I can confirm that too many overrides per view do slow view regen. times down. Again, not model performance - "only" view regen. time.
EDIT
What's "too many"? I dunno. And I think it also depends on what you're asking said filters to do - but again, rather unsubstantiated claims from me.Last edited by snowyweston; February 27, 2017, 04:59 PM.Comment
-
defined, and that project was before I was smart enough to understand the potential of using View templates with filters set therein...So, while there were a lot of filters they were applied helter skelter among views. So, maybe not the best project to use to prove a point?Originally posted by snowyweston View PostI'm retired, if you don't like it, go around!Comment
-
Sure, it slightly slows down view regeneration time. You know what else does? Having more stuff in the model. Maybe I should only model walls and doors and leave everything else out? Lol.Originally posted by snowyweston View Post
I'm being snarky, of course, but my point is filters serve a purpose that (in my template and workflows) is integral to what the deliverables look like.
The *goal* isn't to have the fastest view regeneration. The *goal* is have have the best project showing what we need, how we want it, in the right places. Worksets won't do that. Filters will.
The stats I mentioned (25 per view) are defined and in use I'm every view, some shutting off visibility and some with overrides.Comment
-
-
see, size does matter ;-POriginally posted by snowyweston View PostI'm retired, if you don't like it, go around!Comment
-
Part of it is he's coming in from an MEP environment and from what I've gathered from him and from this forum is worksets for visibility are much more of a way of life for them. I still don't agree with that, but I've never really worked on the MEP side of things so in some respects I don't care too much how they get their work done. I've probably got a dozen or so filters setup on my sheet views in the template and maybe 30 or so overall, but I also have them all listed out on the starting view with what they do and what their intended to be used for. I can see a lot more being needed in an MEP model.Comment
Comment