A reminder to myself (and a tip to anyone else who has not run into this yet): A View that has a revision cloud for a revision sequence that has been marked as "issued" cannot be deleted, as that would change the revision. Assuming that the revision clouds are "incidental", you have to temporarily uncheck the box in the Issued column of the Sheet Issues/Revisions dialog for the revision sequence(s) associated with revision clouds in that View.
In my case, a view for exporting a plan view to CAD was created as a duplicate with detailing, from a view which already had revisions clouds from issued revisions. Duplicate with detailing was chosen because we wanted to include the room tags, and the revision clouds were never removed from the duplicated view. I now want to delete the view completely. It is not necessary to clear the check mark in the Issued column, turn on the display of clouds and tags and delete the revision clouds; simply making the relevant revision sequences unissued is enough to be able to delete the view. Be sure to change the revisions back to "issued" when you are done.
Showing posts with label revision cloud. Show all posts
Showing posts with label revision cloud. Show all posts
February 20, 2012
December 12, 2011
Multi-Sheet Plans and Revisions in Revit
Many projects have floor plans that end up being too large to fit on one Sheet. Revit makes splitting a single Level onto two or more Sheets fairly easy by setting up a Dependent View for each sector of the overall floor plan. Revit even includes a Matchline tool to make it easy to designate the extents that each Dependent View documents. Each Dependent View is then placed on its own Sheet.
When choosing where to break up your plan, and how far beyond the matchline each Dependent View should depict (model and annotation), keep in mind that Revit will automagically add a revision to the Sheet if a View on that Sheet contains the full extents of a revision cloud in that View. If you only place revision clouds on the Sheet itself, you have no worries. But for plan revisions, I prefer to place the revision clouds in the View, so there is no need to worry that the View will move on the Sheet without the revision cloud also moving.
If you show large areas of the model beyond the matchline or if the annotation crop extends well beyond the matchline, you are increasing the odds that a small cloud drawn on the View of one Sheet, but near the shared matchline, will also fall completely within the adjacent View's annotation area. If you are issuing both Sheets, that is not a big deal. But if you are only issuing the Sheet that actually has the revision, you would not want the revision to show up on the adjacent Sheet. Keeping things as tight to the matchline as possible will minimize the chance that this will occur.
Sometimes the way the project is laid out makes it difficult to establish a clean matchline to which you can closely crop the Dependent Views. Other times, a revision is relatively small and right next to the matchline. Here are a couple of ways to avoid having the revision show up on the adjacent Sheet.
When choosing where to break up your plan, and how far beyond the matchline each Dependent View should depict (model and annotation), keep in mind that Revit will automagically add a revision to the Sheet if a View on that Sheet contains the full extents of a revision cloud in that View. If you only place revision clouds on the Sheet itself, you have no worries. But for plan revisions, I prefer to place the revision clouds in the View, so there is no need to worry that the View will move on the Sheet without the revision cloud also moving.
If you show large areas of the model beyond the matchline or if the annotation crop extends well beyond the matchline, you are increasing the odds that a small cloud drawn on the View of one Sheet, but near the shared matchline, will also fall completely within the adjacent View's annotation area. If you are issuing both Sheets, that is not a big deal. But if you are only issuing the Sheet that actually has the revision, you would not want the revision to show up on the adjacent Sheet. Keeping things as tight to the matchline as possible will minimize the chance that this will occur.
Sometimes the way the project is laid out makes it difficult to establish a clean matchline to which you can closely crop the Dependent Views. Other times, a revision is relatively small and right next to the matchline. Here are a couple of ways to avoid having the revision show up on the adjacent Sheet.
- If you have additional revisions in the same View, you can combine the cloud of the revision near the matchline with one that is farther away, and beyond the annotation area of the adjacent Sheet's View.A revision cloud does not have to consist of a single, closed loop of revision arcs. It can be open, and can also have multiple, unconnected runs of arcs. If any part of the graphics of a revision cloud is beyond the annotation area of a View, it will not show in that View, and will not result in a revision line on the Sheet on which that View is placed.
- If you do not have additional revisions, you can edit the revision cloud to include a very small arc that does not fall in the annotation area of the adjacent View, in a discreet location in the View with the revision. If the graphics this generates disturbs you just as much as having a revision line on a Sheet that was not issued, and you turn off the display of revision clouds from previous revisions when making the next revision, you can wait until after you have printed the drawings to be issued, and then go back and add the small segment just before marking the revision as issued and turning off the display of the revision clouds for that revision.
Subscribe to:
Posts (Atom)