So we have a dilemma in the office. We need to create a separate core and shell (CS) set and an architectural (A) set all in one model. We need to be able to have both the CS and A set show the same information but also be able to turn on and off certain things such as revision clouds and a linked interiors model. We need the sheets to show up as CS A100 - OVERALL PLAN and A100 - OVERALL PLAN. We started doing this by creating a whole new set of CS sheets from the A set and duplicating the views with detailing. We ran into many problems. First is the fact that changing anything in the new CS sheets in terms of annotations won't be reflected in the A series and vice versa even with detailing. The other problem is all our A tags would have to be hidden in our CS sheets and all the CS tags would have to be fixed. We ran out of time and had to resort to keeping the A set (and deleting all the CS sheets because of all the new tags that were appearing from the CS sheets) and just changing the title block and using a filter to hide the interiors in all our views. What would be the best way of achieving what I described in my first few sentences? Ideally we just have one set of drawings that we can magically turn something on and switch it from A set to CS set and vice versa.
Gelöst! Gehe zur Lösung
Gelöst von ToanDN. Gehe zur Lösung
As I write all this I realize we should have used duplicate as dependent rather than duplicate with detailing. Sadly, I was not involved in the decision making of this process at the beginning so I'm trying to figure it out now. Would this have solved our problem. LOL
If you use duplicate as dependent and you need some elements to show on one view and not on another then you need to manually hide them using Hide Element in View. Any other hiding methods such as via Categories, Worksets, Filters don't work because they affect all dependent views.
If you want to bring annotation (text notes?) from one view to another and keep them updated, group them and copy paste the group. By the way, my general rule is not repeating information, so the annotation of the Core Shell drawings shouldn't be repeated in Architecture drawings if they are two separate packages.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.