Updateing Clash Detection Matrix
-
Hi everyone,
I have a question regarding the updateing Clashdetection Matrix. During the lifetime of a project the models grow and sometimes new classes are introduced. When I update the Clashdetection Matrix all collisions reset and i loos all accepted / rejected markings.
Is there a way to prevent this? On larger projects I can’t predict what classes will be added and I don’t want to recheck all clashes.Any thoughts?
-
i figured this out the other day also. However, i do feel that it should be smart enough to recognise any new and added ifcTypes and update the list to suit. Its okay if you know what your adding but if you need to add it yourself how are you ever going to know whats been added in unless your consultant side
-
I agree, its workaround to add the new classes yourself. It should be great if there is a refresh button that looks if there are new classes has been added or something.
-
For me, this solution only works when using the standard clash matrix hierarchy. In some cases, I include classifications within the hierarchy, and when those classifications are updated, the matrix is not updated automatically.
-
I use classifications in the matrix and it works fine. BUT!: If you change something, or add an new model to the matrix, you lose ALL markings and issues in the results, for the models / classification right and below the change in the matrix! So you potentially lose a lot of work!
-
To update it auto, you need to break it by selecting a new hierarchy and then reapplying the hicherarchy you want. This should auto-update the matrix, but you will lose all of your severity items and spacing items. Everything will revert to G
Copyright © 2025 Solibri Inc. | Powered by NodeBB