I have attached a model showing what I feel is a bug. Basically I am expecting the display of detail views to be based on the view range where they are located, because that's the way other elements behave. If a detail is located in an area of a plan view where a plan region is located, it is my expectation that the plan region would dictate the display of the detail view. This doesn't appear to be the case. It appears that the display of detail views is solely based on the main view range and plan regions have no effect, even though they graphically display model elements differently based on the cut location. We have to do silly things like extend the bounding box high or low so that the views are cut by the main view range. It makes it very easy to have a detail disappear from the plan view drawings if another user changes the tall bounding box to a smaller size. The user changing the size of the view bounding box would have no idea the view disappeared from the view it was originally shown on.
I'm not worried about the roof. The roof behaves just as I would expect and is only partially shown due to the plan region. My question is aimed at the missing detail view that should be shown at the bottom of the roof. The plan region has a view range that should allow the detail to display, but it doesn't.
@bjur wrote:
I'm not worried about the roof. The roof behaves just as I would expect and is only partially shown due to the plan region. My question is aimed at the missing detail view that should be shown at the bottom of the roof. The plan region has a view range that should allow the detail to display, but it doesn't.
Got it.
I would have to place a section reference other view but I think you already know that.
...the Crop Boundary of the Target View is not captured in the Plan Region View Range. Uncrop the View and you'll see it. Or adjust crop boundary.
...or you could create another that references that view just for that plan region.
I know that uncropping the detail view would work as the uncropped view would then be cut by the main view range. I checked the cropped boundary of my target detail view and it's well within the view range of the plan region. The plan region has the same view range as the Level 2 floor plan but the detail view will only display in the level 2 drawing. Hense why I think this is a bug.
I guess then, in order to prove your "BUG" theory, you would need to prepare an exhibit that demonstrates how it is behaving differently from previous versions of Revit.
BTW: nice exhibit.
...Just tested with 2020. Same deal. I have the drop the Primary View Range Bottom and Depth. Unlimited works.
Just tried this with the 2020 version and it behaves the same way. So not technically a new bug but it behaves different than I was anticipating, and also different than the other elements in the plan region, which smells like a bug. The work around is to just make the crop box taller so that it cuts the main view range cut plane, but man I hate work-arounds. As I mentioned before, I could see some one else in our firm making the box smaller (because it looks dumb) and poof, the detail disappears from the plans. Not good. I know it might be a tricky software problem to solve. What happens if the detail view crosses the plan region? Should it obey the plan region or the main view range? But in this case where the detail view is entirely inside the plan region, it seems like it should obey the plan region.
It appears call-outs respect the view's range, not plan regions. It maybe an overlook or by design - only Autodesk can answer. You can post the question or what you think it should be on the ideas forum.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.