I am building a complex component based framing family and in some cases I need nested families to be "Null". So far I managed to implement it with an empty family, but this results in the identical instances error. I could shift them apart with more formulas, but the component is already heavier than I'd like. Is there a way to implement nested null families? Sorry i can't share the component for various reasons.
-
-
I'd either use a <family type> parameter, if that makes sense, or use a formula to turn off the family's visibility (which would still generate the error). In some cases the error is unavoidable (such as when I have one instance that is is for when array count = 1, and another that is arrayed for when array count is greater than 1) I figure that the warning is more to remind users that the components overlap, and it's up to me to manage the graphics. I have never tried to move something out of the way to prevent the error, nor have I noticed issues in family performance when that error is present.Julie Kidder
Architect + BIM Director
Hartman + Majewski Design Group -
There's a post on the Revit Ideas page about allowing Arrays of 0 or 1
https://forums.autodesk.com/t5/revit.../idi-p/6352220
it's marked as "Under Review", so there's chance it might happen.
Please go vote it up to give it a better chance.Dave Plumb
BWBR Architects; St Paul, MN
CADsplaining: When a BIM rookie tells you how you should have done something.Comment
-
-
It depends on how you are making it *null.*
If its simply an empty family, but it IS set to be visible, that warning WILL carry through to the project, if its a Shared Family.
If its set to NOT be visible, then- as Greg said- you can leave it, it wont cause any issues.
There are several ways to make families null, including a third FT parameter that is reporting only, simply using a formula to report one FT parameter or another. But, since you cant share the family, were all just guessing as to what the real problem is. Sorry!Comment
-
Thank you all. Solved! I simply needed to set the null family to not be empty, but a simple primitive, visibility hard off and hey presto, no more error.Comment
Comment