Welcome to Forma for Construction Ideas! View the Forma for Construction Product Roadmap here. Top-voted ideas may be considered for future development. Learn more about the feedback process here.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
It would be helpful if you could also view deleted collisions in a matrix. Perhaps in different colours (e.g. blue and magenta) to distinguish them from the actual collision list. This would make it possible to understand / check whether the deletion of the collision is correct. A filter option by user, date and reason for deletion would also helpfully.
It would be helpful if you could also view deleted collisions in a matrix. Perhaps in different colours (e.g. blue and magenta) to distinguish them from the actual collision list. This would make it possible to understand / check whether the deletion of the collision is correct. A filter option by user, date and reason for deletion would also help.
I am looking for a document that shows how the re-clashing happens and even if I delete an issue will it come back if I haven't specifically flagged it as not an issue. Then I can delete the issue and it would have to come back as a clash. Not being able to organize clashes in any way let alone similar to Navisworks is really slowing down the process of coordinating.
Something that I have found to be problematic on several projects is that clashes understandably leave the clash pool upon being assigned to an issue. This behaviour is fine and logical until a project member goes full tilt creating issues from clashes, or you realise just after creating the issue that something was incorrectly included/excluded. In these cases depending on how widespread the impact is the only real workaround is to set up a whole new coordination space or reuploading the affected models-both being unideal solutions.
What would be greatly helpful is to basically have an option where by in these situations the issue can be deleted/deactivated and all those clashes return back to the clash pool for future review. As it stands, when clashes are marked as 'not an issue' we have the option to restore the clashes to the pool. It seems logical to have this exact same functionality for clashes that incorrectly or prematurely get assigned to an issue.
