![]() ![]() Why manually chase moving doors through design iterations, with the align tool in elevations snapping light fixtures, when a simple nested light fixture can save you the hassle in one click? Precisely. Why? If they're lights for exiting safely, they WILL go above the doors. BUT, that said: Lights above doors are a PERFECT procedural reason for nesting a family. Now, i preface this issue with the following: I don't believe in the *super door family* theory of having every possible combination built in to one door family, with super adjustable frames, panels, sidelights, etc. Also, a pair of double doors, in the same configuration. The family has a Nested Light fixture constrained to the wall, with a visibility parameter that is type driven. ![]() A pair of Single Doors: They are the same family. Let us suppose: Project 1, with a few "openings" in a wall. This one, however, i hadn't thought about until i gave it a whirl last night while David and i were chatting about it. I think it has immense capabilities (not that anyone argues that), but it certain has its shortcomings. Amongst everyone i talk to, Copy Monitor is a pretty hated tool. One of the great things about exploring tools in Revit, is coming up with new ways to change your processes. Because while i could be relaxing, everyone knows the right way to spend an evening is arguing over the pro's/cons of Copy Monitor, LOL! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |