Without seeing exactly what you are doing, it sounds like your nested access setback families are all of a fixed size, with multiple families/instances to get the four widths you need. I would probably make the nested families parametric, with an instance-based property for the width that could then be tied to the width property in the door family. But if you would prefer not to do it that way, or other considerations make that not possible, what you will need to do is create a separate yes-no parameter for each nested family instance (or possibly each width; I am not clear as to whether a given width could have multiple instances assigned). Tie the visibility of each instance to the associated yes-no parameter. Then in the types for the door family, only turn on the one(s) that apply to that width.
If you have multiple options per width, then you will have to either describe in more detail what you need, or, better still, post a sample family file that shows your progress so far.
What I would do, assuming that your clearance families are either different types of the same family, or are all constructed in a similar fashion such that the insertion point and method of locking to the door/opening are the same and that they are all the same family classification, would be to create two type-based family parameters in your door family, one for the pull-side clearance family and one for the pull-side clearance family. (I am assuming that the push and pull side clearance families are different. If these are the same, one family parameter would do.) These would then be set up to the classification type of the clearance families, and for each door family type, the appropriate clearance family types would be assigned to the push and pull family parameters for each door family type.
In the door family, you would then only need one instance of the pull-side family and one instance of the push-side family. Place the type that goes with the currently active door type for both the push and pull sides and do what needs to be done to lock the families to the door/opening/wall. Then select each of the clearance families in turn and assign the appropriate family type parameter in the Label property. That way, when you change door types, the clearance family type set in the family parameters will be applied, so you get the desired cleance family for each door type.
Now you can add an instance-type yes-no parameter to the door family, and tie the visibility of both clearance families to the yes-no parameter. You can set the initial (default) visibility to Yes in the door family. In a project, when you add your door, assuming that the category used for the linework in your nested clearance families is set to be on in the view in which you insert the door, the clearance families should be visible, and you could then use the instance-based Yes-No parameter to toggle the visibility of the clearance families on a door-by-door basis.
You may also want to consider creating a unique subcategory for the linework in your clearance families, so that you can turn them all off in a view at the subcategory level, rather than having to go to each door and turn them off. Whether or not you need to do that depends on your workflow and how many doors you have in a typical project.
Thanks for the great help David. All sorted now. Using type based family parameters was the trick I needed to get my head around.
Many thanks.
Hi David,
I have provided a link to my family as it stands. I seem to be almost there but when I import the door family, I am unable to get the disabled access setback linework to change with the varying wall thickness across the 4 door widths.
To be honest, I'm a little lost.
Is there any chance you could take a look to see what can be done?
https://app.box.com/s/50bfv79ts0uwdmmc90ro
Thanks
B
I've tried to do what you say and align to the reference line 60mm from the wall centreline but when I change family type within the parent family I get a "Constraints are not satisfied" Error.
Can't find what you're looking for? Ask the community or share your knowledge.