CLIP ALL SIDES not displaying properly in OBD CE06

We have started the transition from CE03 to CE06 and have one workstation running CE06.

We typically set our BV clip volumes to CLIP ALL SIDES. They end up looking like this in an iso view, notice  both the horizontal and vertical portions of the walls are clipped and resymbolized-- this is the view in CE03.

However the same file opened in CE06 is clipped , but only the primary cut plane is resymbolized.  In the following view, notice that the vertical cuts are not resymbolized--inside the red loop

  

Is there now a setting that must be activated to resymbolize all clipped faces?

Please advise--

dmg

Parents Reply Children
  • We clearly have two use cases to ensure that we are addressing:

    1. The 2D drawing views where we have designed a solution to meet user requests to eliminate not existent and potentially misleading lines created by clip planes

    2. The 3D view where the edges need to resymbolise in the same way as the primary cut plane.

    It not clear what has changed, still investigating

    Marc

  • Hello Marc--

    thanks for the configuration variable changes, they worked perfectly and all my cut planes are now showing.  I have no idea how we would have discovered those obscure settings without your deep understanding. 

    Regarding the two use cases you mention above:   We often will use a 3D saved view attached to a sheet for notation, so it presents as an perspective type view.  Having a cut clip display on every face is crucial, see below:

    Yet-- we also do a lot of interior elevations, etc. where it would be great if the side cuts were suppressed.   

    So --  in your investigation and service request, I think you should put the clip suppression capability as an attribute of the saved view, rather than the whole application, that way one could turn it off for elevations, and leave it on for 3D work.

    Thanks again for  your help!

    David Griffith

  • Hi Christian,

    You may have been told about this via other communications, but for the record:

    Section symbology will be correctly displayed if _USTN_SUPPRESS_CROPPLANESECTIONGRAPHICS = 0. The default value is 1 which is intended to omit unwanted non-existent lines that clip volumes may otherwise add to drawings.

    The objects in this screengrab are:

    1. OBD wall
    2. OBD slab
    3. MicroStation slab solid with part data attached
    4. MicroStation slab solid without part data

    This can be changed on the fly using the Configuration Variables dialog (1), which will add the changed value (2) to a user's UCF. To revert select the variable and click Delete (3) to remove it from the UCF.

      

    Once the variable is changed, use the view refresh tool to see the changed dynamic view.

    This content has been added to wiki: Missing section symbology at clipped Clip Volume boundaries

    Marc

  • Hi Marc, 

    Was this ever addressed for situations where you need to see the side plane cuts in certain views in drawings, but not in all?

    We have the same issue David Griffith highlighted where we use 3d axonometric views cut by a clip volume in drawings, but if the _USTN_SUPPRESS_CROPPLANESECTIONGRAPHICS variable is set to 0 globally (through our managed configuration), it will affect other views in other drawings. If we set it at a user level, when the drawings containing the axonometric 3d view are opened by another user (or by the iCS rendition server) they will look wrong.

    In your message you clearly say that for drawings it should be set to 1 (to eliminate confusing lines, as requested by users), and to see the 3d object correctly clipped in all sides it should be set to 0, but since the variable is either globally applied, or user-based, instead of per view, we can't achieve it for the project, and we are forced to "embellish" the side cuts of the axonometric view.

    Any ideas?

  • Hi Enrique,

    I'm no longer in this team so am not up to date with this feature, although it has not changed as far as I can see. The best approach would be to file a service request to discuss in more detail. The ability to change behaviour between the 2D and 3D contexts would clearly be useful.

    Marc