[MStn CE U15] Bug: Raster + vector displayed differently than in V8i

Hi,

I tried to search whether this bug was reported in the past. Maybe it's the same as issue discussed here (plus I found a few more similar discussions), but because it's more than a year old discussion and the bug still exists, I wrote this post.

The problem was discovered by by customer, but original data cannot be shared, so I created very simple test case to illustrate the bug. Unfortunately, it's critical issue, blocking migration to CE (they use MicroStation and ORD). I informed my other customers working with similar data (literally, all civil customers) about this threat, because data are displayed differently.

Problem description

There is 2D model, referencing another 2D DGN and DWG (3D, but with 2D elements at Z=0 in tested case). In the root model, there is a raster attached (tested with WMS, but raster file attached from disk has the same problem). Because the raster is at background plane, in V8i is correctly displayed behind all elements. But in CE U15, it hides elements from DWG:

Problem analysis

I guess the problem itself is clear: Even when the raster has to be always at background, it's not. And because the results are different in CE U15, it's very dangerous (and migration blocking) bug, because some geometry can be hidden without any notification. And there is no chance, when typical civil design consists from tens of DGN and DWG files, to check every file whether everything is correct or not.

Quite accidentally I found a dependency: When references Update sequence dialog is used and root model is changed to be first, hidden elements are displayed. But it cannot be used as a workaround in many situations, because such change would break something else.

I will create also Service Ticket for this issue.

The test case is attached (used WMS is public). Can somebody from Bentley confirm the issue, whether it's defect #1064558 or a new one, and if its fix is planned for U16?

With regards,

  Jan

test-case.zip

Parents Reply
  • We need to understand

    I agree. It's long term problem with MicroStation documentation: Even when CE documentation is much better than was in the past in my opinion, it's primarily "how to" oriented (which is fine). But technical reference with deep detail information is mostly missing (wiki does not represent systematic approach to this topic).

    To don't be negative only, there are exceptions: e.g. Configuration Concepts chapter is the nice example of "technical reference" approach, included into "how-to" doc ;-)

    E.g. Divio documentation framework explain nicely the difference and documentation types and tries to standardize the approach (even when still some types of documents are not covered ;-).

    I would like to suggest that you include the following

    There should be much more variants covered, e.g how these concepts (priority + planes + update sequence) work together when 3D is referenced to 2D, vice versa 2D to 3D, and also combination of formats (because of difference features are supported in 2D DGN, 3D DGN and DWG). It leads to many (tens?) variants, but probably based on just a few rules, unfortunately not clear from outside.

    I often see outputs, composed from complicated mixture of 2D and 3D files and different formats, when especially deeply nested settings cannot be changed easily. And it's not simple to find the right solution without knowing the rules at background.

    With regards,

      Jan

Children