We have a serious issue that I believe is related to TR#68884 which I found in Cell dissappears at drawing scale 1:100. We currently have door tags created with the Place DataGroup Annotation tool because we use Drawing Extractions. Because of the issues we've been having, we started placing the annotations in the same file as the 3D doors. We extract the plans with walls, doors, windows, and annotations without incident typically to 1/8"=1'-0". We then reference the extracted file into a drawing model which is 2D. Then we reference the drawing model into a sheet model which is also 2D. If the scale is always 1/8"=1'-0", then all is fine. The problem occurs when we get to enlarged plans where we want to scale up a partial plan to something like 1/4"=1'-0". The cells disappear in the sheet model completely (nest level 2). They only disappear in the drawing model (nest depth 1) of the sheet model if we zoom in (a little).
Has anyone else experienced this? I'll create a support ticket next.
Mark Mates - BIM Manager - Mason & Hanger
Ustn since 1988SS4 - i7-3.45Ghz-16 Gb-250/1Tb/1Tb-Win8.1-64bEric D. MilbergerArchitect + Master Planner + BIMSenior Master Planner NASA - Marshall Space Flight CenterThe Milberger Architectural Group, llc
Update: That didn't help Steve although I think you meant to change the priority from 0 to a higher positive number. I also tried to adjust the reference setting "Attach Level" to a level and set it's priority, but that didn't help either. One thing that is showing promise is going back to extract with the option of "Preserve 3D Data". This allows the files to be tagged via references such as 2D as Eric suggested. So far the 2D file tagging is working and some of the other 3D file tags are not. I don't know why, but we've been tagging doors and windows for extractions in 3D models and mostly the 3D master model for some time now. I believe it was so that the designers only had to tag them in one place instead of 2 or 3 FP drawings, but I can't remember. It also drastically reduces the file size. For example, one of our floor plan extractions is ~36MB with preserve 3D data versus 1.5MB without. I can live with that. Another workaround and maybe this could be useful to Bentley programmers, is after extracting a file (we use the "Transpose XY Plane" option), open the extraction file run SetZ on all of the elements and set their value to 0... even though they appeared to be 0. For whatever reason, this worked too, but it is a work around.
Thanks for the help and I'll post updates to the progress.
Answer Verified By: mmates