I have unit plans with complex crop regions. When I place them on sheet, model elements (except rooms and room bounding lines) disappear. They still show on the drawing if I open it separately from the sheet, and they print correctly. They also show when the crop region is reset. I attached images of the 3 scenarios.
I can think of several workarounds, but I think this is a bug. Can someone at Autodesk help me out? I'm using Revit 2017.
This is very strange indeed - especially the part about it printing correctly. In other words, it's printing MORE than WYSIWYG.
Anyways, first thought went to worksets. Could it be correlated?
Are are the disappearing elements part of a group or a linked files?
If yes; add a scope box and make sure a line of the scope box runs through that/those view(s) / cropped regions. That should do the trick regardless how complex or funny the region is...
PS: someone told me I shouldn't write too long text so that's as short as I can make it
Cheers,
YOUTUBE | BIM | COMPUTATIONAL DESIGN | PARAMETRIC DESIGN | GENERATIVE DESIGN | VISUAL PROGRAMMING
If you find this reply helpful kindly hit the LIKE BUTTON and if applicable please ACCEPT AS SOLUTION
Hi @melissahRSS8X,
We have had the same issue at the practice.
Basically after trying and trying again to find a logical answer to the problem, we cropped just a little bit larger / off the walls/objects/alignments (we were strictly aligned with the walls), and it worked.
Wasn't a temporary bug though as it would happen again if cropped strictly following wall boudaries.
Maybe this little trick can solve your issue as well.
François-Gabriel
Francois-Gabriel Perraudin
BIM management and coaching
I have seen instances where custom crop regions result in some views not printing even though the views are visible on sheets. I have seen this in both 2016 & 2017, less so in 2017 though. Are you up-to-date with all your service packs?
Removing the custom crop always resolves the issue for me. Your problem seems to be a weird hybrid. The fact resetting the crop resolves this issue in both instances, I feel indicates that custom cropping may still be a bit buggy.
It's definitely not worksets. Resetting the crop region makes it reappear.
Some elements are part of a group and others aren't. Adding a scope box doesn't resolve the issue/
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.