Change Clip Volume Settings for individual reference files within Reference Presentation

Hello

This is my first post. I hope someone can help me please?

I have a file with 2 models referenced in. I need to produce a section callout showing one referenced model as solid hatched fill, the other to be wireframe and greyscale:

The image below shows the desired outcome (reference 1 on the left solid hatched fill, reference 2 greyscale wireframe) but I could only achieve this by creating 2 section callouts and overlaying these on top of each other. If I try and do this using only 1 section callout, they both either hatch, or greyscale (depending on the Clip Volume Settings I choose). Is there a way to achieve the desired output using only one section callout?

It's not a big problem using 2 callouts, but it makes the drawing file untidy. Any help would be greatly appreciated.

Kind regards 

Graham

Parents Reply Children
  • Hi Graham,

    Since it looks like both sets of elements cross the cut plane, essentially you need two different sets of Section resymbolization if a single Callout is used.   The simplest method would be to choose parts that display exactly what you are looking for; e.g., heavier lineweight and fill/pattern for the Piles and a lighter grey color with no fill/pattern for the Culvert.   That is, if this is how they are to appear in all drawings.    Is the example above a one-off or the norm?

    If it is the latter, another option could be to Cache the drawing, use the Copy/Hide Cached Elements command, and then recolor those copied elements.  https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/27802/hide-unhide-cached-elements



  • Hi Steve

    Thank you for your reply. Yes your wording is exactly what I need - I need 'two different sets of resymbolization within a single cut'. As far as I can see, presentation/clip volume settings can only be set for the reference, not for individual ‘nested’ models within that reference.

    Your solutions are great, but unfortunately do not work for my problem. Here are the reasons:

    The Connection culvert that needs to be greyscale is from a different contractor. We are showing their model ‘for information’, but it needs to be greyscale to differentiate between our work and works 'designed by others'. In their drawings, the other contractor will need to show their design with solid fill / hatching pattern, so we cannot ask them to change their parts / families as it would not display correctly in their drawings.

    The 2nd option would work, but because of CAD compliance / CAD QA we are not allowed any 2D linework in the section cuts, so we cannot copy cached elements and then change them, as you suggested. Also, because it is a collaborative and evolving design, the other contractor's model is constantly changing, so we need to keep the reference live or 'dynamic' to ensure we pick up these changes.

    The way I have it set up at present, passes our CAD compliance and maintains a dynamic section cut to automatically update when changes to the models are made. I just don't like having 2 sections in the same position showing the same thing, just for the sake of greying out other contractor's models / designs.

    To clarify, the example is the norm. Anything 'we have designed' needs to be solid fill / pattern. Anything 'designed by others' needs to be greyscale.

    I hope this makes sense? Any solutions to change individual 'nested reference' presentation or clip volume settings would be greatly appreciated.

  • Hi Graham,

    I fully appreciate that you are working with V8i so the solution I can offer is currently out of reach...

    However, for those working with CONNECT Edition we have Display Rules:

    The screenshot below illustrates the steps:

    1. Create a Display Rule called Grey, in this rule create a condition specifying the Reference Logical Name = the target reference's Logical Name.
    2. Create a Display Style called GreyColour and set the Element Override to a suitable shade of grey (use an RGB colour to avoid any issues with varying index coluor tables). (Lots of other things can be changed using Display Styles in this way, see Colour your models Heat Map style for another suggestion)
    3. Amend the Cut Display Style (or create a new Display Style for this purpose) to use the Grey Display Rule.

    The reference with the specified name will then be shown in grey.

    This is a very quick and simple example just working within one file, for this technique to work across a project it would need to be thought through in more detail. Reference logical naming would need to be carefully considered (see the note below); the display Styles and Rules would need to be in DGNLIBs at project, department or company level as appropriate.

    Those of you who have started looking at Display Rules may have noticed the absence of a 'Contains' option for rules involving object names or other text strings, if this is something you would like to see please file a Service Request referencing 'Enhancement 961030:Display Rule Conditions using names and other text strings must have the 'Contains' option'.

    Marc

  • Yes, Display Rules do offer that extra level of control.    Graham, any chance CONNECT Edition is an option?    If not, using two separate callouts with differing resymbolization settings probably is the best/simplest option available in V8.



  • Marc

    Thank you for that information, it is very interesting to know this can be achieved. Unfortunately CONNECT Edition cannot be implemented on this project. Also, to add another Display Style would mean going through the 'red tape' that is Client driven ProjectWise - the project will have finished before the new DGNLIB is approved haha.

    Steve

    Thank you again for your comment, yes it seems due to the constraints I have, my method is the most suitable way to proceed. It seems like CONNECT Edition offers more than v8i so this is good to know for future projects. Also ensuring suitable DGNLIBs containing Display Rules are put in place at the outset of new projects is also very useful to know.

    Thank you to everyone who has contributed to this post. I really appreciate your help.

    Kind regards

    Graham