Needing Help again!!

[aretap]

This should be a simple one! I just don't know what little thing I am doing wrong. I have a door family with a nested frame and door panel. I need the frame to be able to move (offset) via the thickness of the wall. I have everything working great however when I had my symbolic lines for the door sweep and use the offset it is over constrained. I can get it to work perfectly with out the vertical Width labeled dimension. However, with that off the door swing height will not flex in relationship to the door width. Am I attaching to the wrong ref plane or something else.

Thanks everyone in advance!!!!

[The Sweg]

dpatera,

I was having difficulty getting your door to flex between the different types, I kept getting constraint issues. After looking deeper into your family and nested family components, I realized that we have different approaches to family creation, however, I'm sure that's pretty common amongst us Revit users. If you get everything to flex OK, except for the door swing, I would suggest making the door swing a separate annotation family and nesting it into your family. This worked well for me on doors that were giving me fits.

Hope this helps,
--Derek

[nosslok]

I thought I might suggest a slightly different approach to this family. Please take a look at the attached door family and see if it would work for you. You can do this without nesting anything.

The door family that I have attached uses two extrusions instead of a sweep for the frame--one for the frame and another for the rabbets. These two extrusions can be joined with the join geometry command within the family and they will appear as one object. This allows the frame dimension to be completely ajustable at each jamb and head (i.e. for a 4" head frame at masonry openings). Each door panel can done in the same family file and switched on or off by using a visibility parameter with a simple formula. By entering an integer type parameter and calling it "Door type" you can control the visibilities of each panel in the family with the formula "Door Type=1", "Door Type=2", etc. I noticed that your door family file was quite large--over a meg. I'm not quite sure why this is unless the nesting could be causing it.

The drawback with this, however, is that your door panels will pile up in the file, but you can use the hide feature to isolate the door panel you want to work on. Personally from my experience so far, it is usually best to keep things as simple as possible. Trying to make things too parametric or "one-size-fits-all" is usually more of a headache than it's worth. It is usually easier and quicker to have a few more families that are simpler to edit and manage than one extremely complex family that becomes a "rubix cube" to figure out.

I'm not sure what your needs are exactly but perhaps this may offer you another alternative.

KCO