Using MicroStation Connect 10.16.02.34
I am not sure if I am missing something. I have a file structure with a combination of a 2D Sheet referencing a 2D master file that references 3D model containing a raster reference (display off).
The file is set to use "Use File Order" in the Display Wireframe settings. And the update sequence in the sheet to display active file last.
The text (with background masking) in the sheet should display above the hatching from the master model. It does not. If you delete the raster reference in the base 3d model, the display order is then corrected in the sheet.
Wrong display
Correct display after deleting raster attachment in "3D Design" model
Really simple example files attached. I would be interested if others experience this same issue or I have missed a setting that will correct this.
Thanks.
File Ordering Problem.zip
Is the 3d model referenced to the 2d master model, then the 2d master model is Live Nested to the sheet?
Which file contains the text & which file contains the hatching? I am assuming they are both in the 2d master model.
Microstation CONNECT - 10.17.2.61
ORD - 2021 R1 10.10.1.3
ORD 2022 R1.1 - 10.11.3.2
ORD 2022 R3 - 10.12.2.4
Microstation v8i SS 10 - 08.11.09.919
Power InRoads v8i - 08.11.09.615
ProjectWise - 10.0.3.453
Bug, Connect is loaded with them. New ones with each revision. Real Bull Stuff.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
Text is in the sheet. Hatching from the first reference file. I can get even wackier results with some nested elements above and some below the text. But I wont make this example even more complicated.
Note if I export the file to 3D everything works as expected. Might be the solution for now.
StirlingH not sure what is going on here. I can replicate what you're describing in MicroStation CONNECT Edition and V8i. Can't see any particular option with the attached 3D model containing the raster that should affect this display. Checking with my colleagues first but I suspect it may be a Bug.
RegardsAndrew BellTechnical SupportBentley Systems
I have discussed your issue with a colleague and found there is a workaround that may assist. We initially though changing the Visible Edges to Cached in the referenced "Model", that the 3D model is referenced, and then changing the Priority of the text to 500 was going to work but it did not achieve what we were expecting. The only method we found was to look at the Properties of the referenced "Model" and change the Visible Edge Display to Cached.
**Just to note also. It is not specifically related to the Raster attached in the 3D model but any elements in that model produce the same result.