I have a single level in a nested reference in an existing survey motif that is plotting above design, all 2D files
I have the priority of the level set to -200 in the nested reference, then I have the motif referenced in the sheet file with "never" overrides. I have the motif at the top of the sequence order in my references.
I then have my pentable set up so that the nested reference logical name is plotted at -200, the design motif is plotted at 200, and even wrote in the pentable to have the level in the nested reference plot at -200.
It STILL plots on top. I have tried enabling "non-rasterized priority sort mode" and it results in all my survey being plotted above my design. I am stumped. Is there anything else that can screw with the priority when plotting?
To summarize, I have used the following methods to make survey plot behind:
Yes nesting can cause grief .. I found that transparency really screws with the layering priorities especially when you have a file with hatch patterning in the mix... the only solution for me that worked and i tried everything even now .. was to remove the hatched areas from the nesting and add it as a separate ref on top so it forced the priority how I needed it .. but this defeated the benefit of a nested file as one source of truth for attachments.. but heck when you just have to get it out to client as a deliverable by 430 pm on a Friday and its 4 pm now and you just " have to fake it till you make it"
.. by the way this is always when bad things always happen in MicroStation..
Currently Using V8iss10 (8.11.09.919)
and dabbling in CE update 16 (10.16.00.80)
Pwise Administrator ( yeah I passed the training course!)
MicroStation user since 1990 Melbourne Australia.click link to PM me