I am trying to find out how I can export the crop region (some are polygons in our files) to show up in the AutoCAD file in model space. Currently, when I export to dwg the viewports export but when I switch to model space the crop regions that I have modified or have on in Revit do not export at all. Is there a solution for this?
Since they don't show in Autocad, they won't show in a Revit Export.
Draw a line around the crop region in Paper space and use the CHSPACE command to move the created line to model space.
You would have to best guess this method in Revit, but it will show up on your prints unless you are using the "no plot" add-in.
Go to Revit-Export-CAD, then click the little box with three dots next to the "Select Export Setup" drop down list. Go to General tab, uncheck "Hide Scope Boxes"
I was excited to see that the mystery would be solved. Alas..... it is not solved. I tried exporting a sheet that has a lot of views with lots of different shaped crop regions in revit. Checking and unchecking the "hide scope boxes" produced the same result. No crop regions were exported with either....
Thanks for the suggestion!
We have drawn a detail line in the view to represent the crop region (only when absolutely needed) thereby eliminating the need to use the change space command..... but... thanks for replying!
@Anonymous wrote:
We have drawn a detail line in the view to represent the crop region (only when absolutely needed) thereby eliminating the need to use the change space command..... but... thanks for replying!
You may already know this but you can edit the view crop region, select the sketch lines and CTRL+C to copy it. Go back to the view and Paste Aligned.
Thanks but I am looking for a solution not a workaround. I don't think this should be a difficult ask from Autodesk. Why it just doesn't export and have it's own export settings is beyond me.
I know this is years later but I am also having the same issue. I tried this option to uncheck "hide scope" but it looks exactly the same.
Same issue again. Came to look for a solution and find out there's none. Autodesk should really check this out and this is not the only strange small issue need to be fixed