Automatic Hatching / Patterning in Dynamic Views

                When you place a dynamic view as a reference attachment on a sheet, you can set up your solids to automatically generate hatching / patterning on the section plane. This is a big relief because you no longer need to manually apply hatching / patterning by using the Hatch / Pattern tools and selecting specific areas.

                Just so you know, the graphics displayed on the section plane are not real elements. They are drawn by MicroStation at run-time. They are called Section Graphics.

                 Various types of Hatching / Patterning can be used for section graphics by making use of various parameters of Hatching and Patterning supported by Element Templates. Element Templates are like super-styles. They provide a flexible container to collectively apply several types of styles and settings to an element. In this example, we are going to set up a template with hatching / patterning settings.

Example below gives the step by step procedure to use Hatch /Pattern for Section Graphics...

  1. Create Element Template Group TG1 and create Templates Hatch, CrossHatch and Pattern inside it. Delete unwanted Template properties and add required property as shown below.

Template Name: Hatch (and description of Hatching properties used)

Template Name: CrossHatch (and Description of Hatching properties used)

Template Name: Pattern (and description of Patterning properties used)

Note : Pattern Cells used are Shared Cells available in native DGN file

2.    Keep three different solids ready for which we want to assign these Templates



3.     Select each solid and assign respective Element Template to it by keeping ‘ Active Element Template' button in pressed state


4.    Generate Clip Volume and check the appearance of the section graphics

Solid-1 (using Template : Hatch)

Solid-2 (using Template : CrossHatch)

Solid-3 (using Template : Pattern)

More blogs are coming up, So be there:



  • @Phil.  Thanks for the tip. I realized that myself after I had posted the reply, and noticed the date for the last activity. I have posted it on

  • @Jens... you might want to start a discussion about that topic in a forum post -- go to the product community that most relates to the product (and release) you are using, select the Forum tab in that community, then click the "New Post" pushbutton and post your inquiry there.

  • Hi Mark

    Great post!

    Since you seem to know your way arround theese sections, do you know of a way to maybe use Annotation Scale with patterns on sections? My problem is, that I want use an Element Template on an element in my model, and I want to use this model on drawings in different scales. Is that possible?


  • >The present limitation of Hatch/Pattern styles indexed only in Templates

    >could be overcome by having independent Hatch/Pattern styles similar to

    >the way we have 'Material' library. Later these styles can be conveniently

    >used in Levels by existing MicroStation practices.

    This statment generally covers what I thought would be an easy workflow. Although, I thought the Hatch/Pattern styles would actually be a part of a new 'Material Manager'. I would envision the ability to assign a Material to a Level or Template. The Level or Template would have a default Section Graphics (Hatch/Pattern Properties when cut as well as a definition to define the attribute "Overrides" for the Cut Edge). I am not sure of how the Hatch/Pattern would be oriented; my guess it would be relative to the View's display plane & orientation. I would see the management of this as being like combination of Level Manager & a Template Manager in that Levels and Templates would be targets like Levels in Level Manager. These targets would allow wildcards, like filters, which would allow the settings to be applied to many Levels/Templates at once. If the Level or Template were explicitly stated that defination would override any filtered defination. Within this 'Material Manager' there would be a column with a button setting forSection Graphics. This button would open a dialog and allow for setting all of the attributes of the Section Graphics. This 'Materal Manager' could also have a "flat mode" which would expose all settings directly in columns. The "flat mode" would allow the library defination (delivered via. dgnlib) to be "Overridden" in the active File (or perhaps Model).

    Maybe this could become a new master 'Level / Template Manager' in which headdings  (ByLevel, Material, Section Graphics, etc.) would group attributes and be arranged as columns of "Buttons" when collapsed. When one of the 'Buttons' is pushed a daughter dialog would be presented to modify all of the attributes grouped under that heading. The 'Heading' could be pushed to open the "flat mode" for that 'Heading'. In the current organization of MicroStation the 'Buttons' could actually be Templates and name the 'Button' as such.

    - Roy

  • Mark,

    >Template_1 – (Level : Lev2,  Color : ByLevel)

    >Template_2 – (Level : Lev1,  Color : ByLevel)

    Is this a typo? Should it read?

    Template_1 – (Level : Lev1,  Color : ByLevel)

    Template_2 – (Level : Lev2,  Color : ByLevel)

    >ByLevel) to Lev1 then the question arise is in which colour that element

    >should appear?

    Which color will it appear?

    >As ByLevel properties are overridden by property defined in Template,

    >it's a problematic situation if such cross reference is formed. Hence it is

    >not advisable to make Template a Level property.

    I have not introduced templates as of yet and still trying to grasp the "rules" of how templates should be defined. It appears that templates in gereral would deviate from many of the defined Standards (NCS, A/E/C, & etc.). If I understand correctly, elements would not be created with ByLevel properties but with applied Templates. These Templates would have specific attributes assigned and not ByLevel attributes. I understand the the attributes of the Template may be modified and this effects all element placed with that template. The problem I have is how this workflow would translate out of MicroStation and how it is possible to create drawings which conform to the required Standards?

    - Roy