Clash Detection Changelog#

[107.3.10] - 2025-06-20#

Added#

  • A row limit has been introduced in the Clash results table to restrict the number of rows displayed. The current limit is set to 1 million rows.

  • Introduced a per-clash outline triangle limit setting for the clash detection engine.

  • Added a new clash detection engine setting to ignore redundant overlaps.

  • Clash Baking feature:

    • Added new options to enable / disable per polygon bake, wireframes and outlines.

    • Added new display opacity mode to improve runtime performance for large meshes.

    • Added support for baking meshes animated through animation curves.

Improved#

  • The clash detection engine can now process more clashing pairs than before, allowing it to run on even larger stages.

  • The clash report exporter now uses row numbers instead of clash IDs.

  • The currently edited query is now automatically saved when the window is closed.

  • Clash Visualization: Enhanced outline transform computation for clashes far from the origin and boosted performance by leveraging FSD.

  • Clash detection pipeline now runs asynchronously, not blocking the UI.

Fixed#

  • Certain “2D meshes” that were previously flagged as invalid during the clash detection process are now processed correctly.

  • Fixed an issue that occurred when assigning a person (PIC) in the Clash results table.

[106.5.0] - 2025-03-07#

Added#

  • Contact Depth: A new experimental feature that measures the local depth of contact between two objects. It also includes an adjustable Depth Epsilon value to differentiate between hard clashes and contact cases.

  • Clash Query settings were reorganized for better understanding.

  • Clash Query searchsets now support multiple object paths.

  • Improved viewport visualization for dynamic clashes, now capable of displaying animated clashes as actual animations.

  • Consumes considerably less RAM while processing clash detection results and manages out of memory conditions more effectively by halting clash detection and releasing all allocated memory.

  • Faster stage enumeration (first step of clash detection process).

[106.4.0] - 2024-12-05#

Added#

  • Duplicate Mesh Detection and Management: This feature identifies and manages duplicate meshes. It specifically targets static, identical meshes that overlap completely due to having identical transformations.

  • Clash Classification: The system now supports clear classification of clashes into soft and hard categories. This is achieved by measuring the minimal distance between clashing objects.

  • Static Clash Detection Timing: Users can specify a specific time for static clash detection, which previously defaulted to the current time on timeline.

  • Clash Query Export/Import: Users can now export and import clash queries using JSON files, streamlining data exchange.

  • Per-Frame Transformation Tracking for Clashing Objects: Transformations of both clashing objects are now saved for each frame where a clash occurs, rather than only at the first frame. This enhancement helps users determine if an object in the scene has moved at any time since the last clash detection run.

  • Different colors on the progress bar now represent various stages of clash detection:

    • Green indicates the conversion of curve animations to time samples.

    • Orange signifies the clash detection engine’s activity.

    • Blue denotes the result-fetching process.

[106.2.0] - 2024-09-25#

Added#

  • Support for curve animations has been added. Works seamlessly as a part of clash detection process.

  • The Clash Query combo box now displays the start and end times for dynamic queries.

Improved#

  • The retrieval of results at the end of the clash detection process is now five times faster.

  • Improved internal processing of clash detection files to ensure proper support for larger files (approximately 2GB and more).

Fixed#

  • The search set picker was not updating properly after a stage change.

  • If only a single search set was configured, no clash detection results were returned.

Removed#

  • The feature that indicated outdated transformations (an orange square) has been disabled, as it is no longer relevant. This change is due to our support for curve animations, which require conversion into time samples—a process that only occurs when the clash detection process begins.

Next Steps: Clash Detection UI