If clashing objects have the same value of a specific property, the clash is ignored.

You can add any number of conditions of this type.

To add a condition:

1. At the bottom of the Ignore clashes window, click Add condition for ignoring clashes.
2. Select Both objects have the same property value, and then select a property.

To remove a condition:

• In the upper-right corner of the condition box, click .
  

If both of the clashing objects belong to the specified search set, the clash is ignored.

You can add any number of conditions of this type.

To add a condition:

1. At the bottom of the Ignore clashes window, click Add condition for ignoring clashes.
2. Select Both objects are in the same search set and select a shared search set.

To remove a condition:

• In the upper-right corner of the condition box, click .

If an object from selection A belongs to search set A and an object from selection B belongs to search set B, clashes with those objects are ignored.

You can add any number of conditions of this type.

To add a condition:

1. At the bottom of the Ignore clashes window, clickAdd condition for ignoring clashes.
2. Select Object A and object B each is in the specified search set and select two shared search sets.

To remove a condition:

• In the upper-right corner of the condition box, click .
  

The rule that defines what is treated as a clash.

• Hard clash. Objects clash if they touch or intersect.
• Clearance. Objects clash if the minimum distance between them is less than the clearance.
• Clearance horizontal/vertical. Objects clash if the minimum horizontal/vertical distance between them is less than the horizontal/vertical clearance.
• Tolerance. Objects clash if their penetration depth is greater than the tolerance.
• Tolerance horizontal/vertical. Objects clash if their horizontal/vertical penetration depth is greater than the horizontal/vertical tolerance.

The type of objects that are subject to clash detection, one of the following:

• Elements. Items of the object tree that represent physical objects.
• Geometries. Parts of elements.

If clashing geometries belong to the same element, the clash is ignored.

This option is available only for clash detection between geometries.

The physical object type (element or geometry) and clashing selection.

• Element A. Elements from selection A.
• Element B. Elements from selection B.
• Geometry A. Geometries from selection A.
• Geometry B. Geometries from selection B.

Clashes are grouped if the distance between any two clash points does not exceed this value. Some clashes that are close to each other might go to different clusters, as shown in the figure.

Clashes are grouped if the distance between adjacent clash points does not exceed this value.

If a chain size exceeds this value, the chain is split into shorter ones.

A chain size is the distance between the two opposite corners of the smallest box that surrounds all clash points.

• Element A. Elements from selection A.
• Element B. Elements from selection B.
• Geometry A. Geometries from selection A.
• Geometry B. Geometries from selection B.

Add all available location tags to clashes. This includes level, room, space, zone, area, and grid intersections.

For location tagging rules, see the descriptions of other checkboxes in this table.

Tag clashes with levels.

For additional options, see Level model.

• If a clash point is inside a room, the clash is tagged with the room.
• If a clash point is outside of a room but there are rooms directly under this point, the clash is tagged with the closest of these rooms.

Tag clashes with spaces.

• If a clash point is inside a space, the clash is tagged with the space.
• If a clash point is outside of a space but there are spaces directly under this point, the clash is tagged with the closest of these spaces.

• If a clash point is inside a zone, the clash is tagged with the zone.
• If a clash point is outside of a zone but there are zones directly under this point, the clash is tagged with the closest of these zones.

Tag clashes with areas.

• If a clash point is inside an area, the clash is tagged with the area.
• If a clash point is outside of an area but there are areas directly under this point, the clash is tagged with the closest of these areas.

Tag clashes with grid intersections.

Depending on the settings in the Grid models section, a clash is tagged with one or several grid intersections that are the closest to the clash point.

The colors of clashing objects.

• Selection A. The color of clashing objects from selection A.

• Selection B. The color of clashing objects from selection B.

• Resolved/Approved. The color of all elements of resolved and approved clashes.

  This color is used only when the Clash Colors option in the bottom part of this dialog is set to "3 colors."

This parameter limits the size of the clash section box.

For individual clashes, Revizto builds the smallest section box that includes both clashing objects. If the box width, height, or depth is more than twice this value, the box is cut to fit the limit.

For clash groups, Revizto builds the smallest section box that surrounds all section boxes of individual clashes.

If the Height is defined by neighboring levels checkbox is selected, the box height will be adjusted AFTER the limit is applied.

The appearance that is applied to the 3D model when a clash issue screenshot is taken.

• White. The 3D model becomes white.
• No appearance. The 3D model keeps its original colors.
• <appearance template name>. The selected appearance template is applied to the 3D model. You can only apply shared appearance templates.

This parameter defines how clashes are highlighted.

• 3 colors. One color for active clashes from selection A, another color for active clashes from selection B, and a third color for resolved and approved clashes from both selections.
• 2 colors. One color for selection A, and another color for selection B.
  You can select the colors in the Clash colors field at the top of this dialog.

This parameter defines whether clashes are isolated.

• Isolate in transparency. Nonclashing objects are visible and transparent.
• Isolate. Nonclashing objects are hidden.
• Show all. The appearance specified in the Appearance field of this dialog applies to nonclashing objects.

The transparency of clashing objects.

• A transparent. Elements of selection A are transparent.
• B transparent. Elements of selection B are transparent.

This works best when the bigger of two clashing objects is transparent.

For example, if selection A contains pipes and selection B contains walls, we recommend that you make selection B transparent.

Defines whether the section box from the clash viewpoint is applied to the 3D model when the screenshot of that clash is taken.

If you clear this checkbox, no section boxes are applied.

We recommend that you select this checkbox for faster screenshot generation.

Defines whether clash test grids are visible on clash issue screenshots.

To learn how to configure clash test grids, see Grid models.

This parameter defines which issue screenshots are updated during the clash detection.

• All. Screenshots of all issues generated by this clash test are updated.
• For changed clashes. If a clash changed since the last clash detection run, the clash issue screenshot is updated.
• Changed except manual. If a clash changed since the last clash detection run and the clash issue markup was not changed in the issue tracker, the clash issue screenshot is updated.
• None. No screenshots are updated.

Keep in mind that screenshot generation takes time. "None" is the fastest option, while "All" is the slowest one.

This parameter defines which issue viewpoints are updated during the clash detection.

• All. Viewpoints of all issues generated by this clash test are updated.
• For changed clashes. If a clash changed since the last clash detection run, the clash issue viewpoint is updated.
• None. No viewpoints are updated.

This parameter defines whether unreviewed clash groups are synced with the issue tracker.

• Ask each time before sync. Before each sync, you are asked if you want to sync unreviewed clash groups. Reviewed clash groups are always synced.
• Reviewed and not reviewed. Both reviewed and unreviewed clash groups are always synced.

The stamp template to apply on issue generation.

You can override the stamp template priority, assignee, and deadline by setting Priority, Deadline, and Assignee in this dialog.

The watchers and tags specified in the stamp template are always added to the issues. You can specify additional watchers and tags in the Watchers and Tags fields in this dialog.

To clear this field, open it for editing and click Reset.

The priority of new issues generated by the clash test.

If this field is blank, the priority is inherited from the stamp template. When the priority is inherited, this field is marked with the following icon: .

If a stamp template is not specified or has blank priority, the priority is set to  None.

To clear this field, open it for editing and select Reset.

The deadline of new issues generated by the clash test.

If this field is blank, the deadline is inherited from the stamp template. When the deadline is inherited, this field is marked with the following icon: .

If a stamp template is not specified or has a blank deadline, the deadline is not set.

Note that the weeks and months that you specify here are calendar weeks (starting on Monday) and calendar months. For example, if you specify a 1-week deadline here, the actual deadline is set to the next Monday.

To clear this field, open it for editing, delete the value, and then click Apply.

The assignee of new issues generated by the clash test.

If this field is blank, the assignee is inherited from the stamp template. When the assignee is inherited, this field is marked with the following icon: .

If a stamp template is not specified or has blank assignee, the assignee is set to the user that runs the sync with the issue tracker.

To clear this field, open it for editing and select Reset.

The clash issue tags.

This includes the tags inherited from the stamp template and the tags that are explicitly added here.

• To create a tag, type it and select the checkbox next to it.
• To add existing tags, select the checkboxes next to them.
• To remove tags, clear the checkboxes.

Switches the clash test to Advanced issue automation.

This adds the option to add multiple issue generation rules. Each rule includes a condition that defines when the rule is applied.

The issue generation rule that you configured in the simple automation mode becomes the default one. It is applied when none of the conditions are met.