![]() ![]() Now imagine buying a car, only to realise that the driver side door cannot open, so you have to enter from the passenger side door, struggle over the centre console, finally get in, buckle-up and drive off. Imagine buying a car, and you’d expect to get into the car via the driver side door, buckle-up and drive off… Simple right, that’s what you paid for. Someone once asked me why a plausible workaround is so bad, and I went on to us the following example: I've used your proposed workaround before and have a few things against it, which is why I find this idea to be valid. I've been a bit wrapped up over the past week, but managed to find a couple of minutes. They don't have a relationship with each other across other drafting views, they merely assist to speed-up and control your crop regions and consistency across various schematics.īelow is a revised image from my original post. This way your Dependant Views of your Drafting Views can be controlled by the "2D Scope Boxes". Now that I have that information, I generate my "2D Scope Boxes" on that Drafting View and copy them over to the other schematics. Let's say I started with the worst-case (largest schematic) to inform me of the number of sheets which would be required. (Scaling down the drafting views is not an option for obvious reasons!) Due to the size and length of each, they need to be separated on a different amount Let's look at a practical example where this will be useful: The Building below has 11 Floors, which requireġ1 Schematics for each floor. I included a few additional samples below, along with updates to my original images - picked up a typo or two! This way, the consistency of Crops can be controlled. These can then be used and copied over to other Drafting Views, Models (or Projects). To clarify what I meant is where there is a possible introduction of "2D Scope Boxes" which can be used on Drafting Views. I used "scope box" as a bone which is being thrown to spark some functional solutions relating to how they can be used in Drafting Views to control the Crop (and Annotation Crop) of the views, as outlined in my steps, which will essentially mimic the same functions which end-users are used too. As you mentioned, mechanical specifically has huge I agree and understand the function of the current Scope Box command. The problem is still the same for both scenarios where schematics need to split into multiple sheets. There are however some firms, especially smaller firms (but some larger ones too) who still link CAD files into drafting views to issue everything out of Revit etc. Hopefully, this workflow & requirements get the necessary traction for consideration in future releases.Ĭompletely agree with you If you've done a schematic / single line diagram in Revit once or on one project from start to finish, you won't revert back. The consolidated post which I'm referring to can be found HERE. Similar requests have been made without any major progress from 2016. As soon as there are updates, you need to start from the top again (to avoid discrepancies across multiple Drafting Views), followed by separating the Drafting View again. It's extremely time-consuming and error-prone to split elements from a single Drafting View into multiple views. It is required to separate the Drafting View on Multiple Sheets on just about every project. ![]() There are various use cases, one of the biggest ones for all MEP Engineers on just about every project is the use of Schematics in Revit, be it from an AutoCAD file linked into a Drafting View or where the Schematics / Single Line Diagrams are drawn out directly in a Drafting View. Drafting View Scope Boxes should also be able to be copied from one project to the next, once again, there are use cases for this too. Scope Boxes can be copied from one Drafting View to the next as there are use cases for this.ĥ. Scope Boxes can be assigned to the Drafting View and the Dependent Drafting Views can be cropped according to the assigned Scope Boxes.Ĥ. The ability to create Dependent Drafting Viewsģ. Ability to Add Scope Boxes to Drafting Views which will easily control Crop Regions which is also required as a controlling function within Drafting Views.Ģ. SEE THE IMAGE BELOW FOR FURTHER REFERENCE: (workflow requirements are outlined below)ġ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |