Utility Levels with _3D: WTF? (Why This Furcation?)

I missed the memo.

Bentley delivers, and others copy, utility levels bifurcated into a nominal (2D) and a 3D with a "_3D" suffix.

This offends my instinct towards data normalization.

I reflexively think "but the 2D graphics are in the 2D Model, and the 3D graphics are in the 3D Model!".  They stay separate and segregatable (like the McDLT) without having to have special containers (like the McDLT).

So, is it simply a matter of being able to Level Filter (say, for Conflict Management (I'd go a different (more complicated) route, but Easy is more handoffable))?

What other benefits are there to this duplication?

Parenthetically yours,

-jeff

Parents Reply Children