Hello,
I have this balcony-family, made from about 250 different nested families.
Every nested family is controlled by a visibility-parameter. (yes/no).
Problem is, that the family is very slow! I can wait minutes before the parameters will change. Especially if I have put on materials first.
Is there a way to speed it up? I have tried to make a schedule, but I can get it to work.
Please see attached picture.
Kind regards Morten
250 nested components...That is a lot of families
Did you try to use <Family Type> parameter instead of Y/N? This way
Type catalogs and lookup tables might also co in handy in your case
PS: What I do not get is why would you compile a family which is basically easier to model using a Railing and a Floor element
YOUTUBE | BIM | COMPUTATIONAL DESIGN | PARAMETRIC DESIGN | GENERATIVE DESIGN | VISUAL PROGRAMMING
If you find this reply helpful kindly hit the LIKE BUTTON and if applicable please ACCEPT AS SOLUTION
Hello,
Thank you for reply.
In the family, there is aprox 160 "railings types", (Not made as railing in Revit thoug..), 25 different handrails, 30 different kinds of floor-setups ect. Many differend way to set up the attachtment on the floor and so on.
There a many thousands of way, to combine the balcony.
When I made the families, I thought the most easiest way, was to control every single object using Y/N parameter.
But truely, it is not the fastest way - unfortunately.
All in one families can be a good challenge to produce in practice, but you've figured out why they are impractical in actual models.
If you need more than a handful (my personal limit is 2) of Yes/No tick boxes in the main family then use a Family Type parameter to create a selector list from types in a nested family.
Who will be using those families?!
Families are not always a solution..if they get too heavy to handle and too confusing for other users to understand how to configure and use then they lose their purpose....Elements such as these (floors/rails) are much easier to configure and set up in the project template as types and later on users simply place them using the OOTB tools rather than staring and scrolling through 160 yes/no parameters and wondering which to use
If you insist on families:
You do not really need any yes/no in the above process
YOUTUBE | BIM | COMPUTATIONAL DESIGN | PARAMETRIC DESIGN | GENERATIVE DESIGN | VISUAL PROGRAMMING
If you find this reply helpful kindly hit the LIKE BUTTON and if applicable please ACCEPT AS SOLUTION
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.