The following changes have been made to Interference Checking.
Hot Fix and Service Pack Updates
-
Added the UpdateModifiedClashStatus rule to the Rules evaluating two clashing objects section. This rule is used to update the clash status of the modified clash marker whenever there is a change in the clash marker type. (P2 CP:383217)
-
The maximum server lag time limit is now changed to 60 minutes in the Number of Transactions in Cache dialog. Previously, the limit was 5 minutes. See Server-based interference checking (Database Detect). (3638932)
-
Reorganized the table of contents to create the following new sections:
Version 13
-
The software now considers the As-Built subscribed projects for clash detection. See the Interference Checking for Subscribed Projects section in Getting Started with Interference Checking. (P1 CP:366680)
-
Added information about the IFC Diagnostics tool for tracking and monitoring the interference checking (IFC) process. (P2 CP:335042)
-
The 64-bit Smart 3D Interference Detection Service now supports the processing of CloudWorx-based point clouds for maximum performance. (P2 CP:307977)
-
The software now considers claimed and unclaimed Smart Interop Objects (SIOs) for interference checking based on the scope definition. See the Interference Checking for Smart Interop Objects (SIOs) section in Getting Started with Interference Checking. (P2 CP:358727)
-
The software does not consider the demolished Smart Interop Objects for interference checking. Any existing interference markers identified on demolished SIOs are deleted once they are re-processed by IFC. (P3 CP:363748)
-
Interference Checking now supports creating interference markers between Smart Interop objects in a Change Management model. (P3 CP:349714)
-
You can now track the IFC rules that exceed the pre-defined time limit using the time logging mechanism. See Track rules based on time limit. (P3 CP:362029)