See the Supported Files topic for information on the types of files supported for aggregation and clash detection.
File types which are supported for uploading to Docs but which are not listed in the Supported Files topic are not displayed in Model Coordination.
Models not updating can happen for different reasons depending on whether the coordination space has automatic clash detection turned on or off. You can check what might be causing this by looking at the information shown by the coordination space picker in the top right of the screen in Model Coordination.
In coordination spaces with automatic clash detection turned on, uploading new files or file versions to the corresponding folder in Docs will trigger a new automatic clash check. Once the clash check has finished, the new models or model versions will be displayed in Model Coordination, along with their clash results.
If you can't see the latest models, this could be due to the following:
Reason | Details | Solution |
---|---|---|
The files are still processing in Docs | Before Model Coordination can start a new clash check, the files must finish processing in Docs. If you've uploaded new files and a clash check hasn't started after a few minutes, check the files in Docs. | If the files have failed to upload or process in Docs, you can retry the processing or you may need to upload the files again. |
The clash check on your latest models is still processing | Clash checks can take from between a few minutes to a few hours, depending on the coordination space version you are using and the amount of model content being checked for clashes. |
If you have a clash check that is processing for more than eight hours, consider reducing the amount of model content being checked by deleting or moving files out of the coordination space folder in Docs, or opting models or objects out of clash, or creating multiple coordination spaces with fewer models in each in Model Coordination. If the problem persists, contact support. |
The latest clash check was unsuccessful | See the Clash FAQ topic to learn more about unsuccessful clash checks and how to address them. | |
You've reached the limit of 1000 models* in a coordination space | Clash checks can't run when there are more than 1000 models* in the coordination space. This applies to all models, including those not supported for clash and those that are turned off for clash. When there are more than 1000 models, Model Coordination will display the same models as before the limit was exceeded. If there were more than 1000 models before the coordination space was created, no models are displayed. |
Reduce the number of models in the coordination space by deleting or moving files out of the coordination space folder in Docs, or creating multiple coordination spaces with fewer models in each. For example, create a coordination space for each building in a project, or for each level of a building, or phase of a project. A new clash check will trigger automatically when there are fewer than 1000 models in the coordination space. |
* Note: Each 3D view in a Revit file is considered as one model in Model Coordination. There may be more than 1000 models in a coordination space even though there are fewer than 1000 files in the coordination space folder in Docs.
In a coordination space with automatic clash detection turned off, new models or model versions will show in Model Coordination once the files have finished processing in Docs. If you have uploaded new files or file versions and they are not showing in Model Coordination even after waiting a few minutes, this could be due to the following:
Reason | Details | Solution |
---|---|---|
The files are still processing in Docs | Before Model Coordination can display your models, the files must finish processing in Docs. If you've uploaded new files and your models aren't displayed after a few minutes, check the files in Docs. | If the files have failed to upload or process in Docs, you can retry the processing or you may need to upload the files again. |
There are too many models in the coordination space | Coordination spaces with clash turned off can't display models corresponding to more than 5000 files. This limit refers to the total number files in the included folders. Only file types that are supported for aggregation in Model Coordination count toward the limit. Model Coordination will display the models corresponding to the first 5000 files from Docs (by alphabetical order of file name). | Reduce the number of models in the coordination space by deleting or moving files out of the coordination space folder in Docs, or creating multiple coordination spaces with fewer models in each. For example, create a coordination space for each building in a project, or for each level of a building, or phase of a project. |
Any coordination spaces that are inactive for 60 days or more are automatically deactivated. This reduces resource usage on projects with limited activity. When a new model or version is uploaded to the folder associated with the coordination space, it is automatically reactivated.
A coordination space can also be manually deactivated by project administrators.
Coordination spaces are configured against folders in Docs. If a folder in Docs gets deleted, and it was the only folder in the coordination space folder selection, the space still exists but appears empty. If you want to rename, or activate or deactivate the coordination space, you can edit the folder selection for the space.
See the dedicated Clash FAQ help topic for specific questions and answers about clash detection.
See the Administration help topic for general information about administration in the Autodesk Construction Cloud.
The Manage Account Members topic describes how to add a member as an administrator for your project.
Project administrators can then control project member product access.
Project administrators and project members with Manage permission can also control access to individual folders. Project members need at least View permissions for the coordination space folder or any of its parent folders to be able to work in Model Coordination. To check the folder for a coordination space:
Model Coordination makes API calls to developer.api.autodesk.com. If this domain is blocked by your firewall, your models and clashes might not load. For Model Coordination to work correctly, you'll need to add developer.api.autodesk.com to your allow list.
When you open Model Coordination and select a coordination space, your project and model-set IDs are shown in the page URL:
Provide the whole URL when reporting problems using the online Contact Support form to give our team a starting point for investigation.
This issue may be caused by shared coordinates either not being published to the linked files, or not being saved into the exported file.
For example, an architectural Revit model (Arch.rvt) has a linked structural model (Struct.rvt) and MEP model (MEP.rvt). The architectural model has shared coordinates including a rotation to True North. The linked models all appear aligned in Revit. The structural model is exported to DWG (Struct.dwg) and the MEP model is exported to IFC (MEP.ifc).
When viewing Arch.rvt, Struct.dwg, and MEP.ifc in Model Coordination, both the structural and MEP models are rotated in relation to the architectural model. This is due to the shared coordinates being respected in the architectural model but not existing in the DWG and IFC. In this example, the misalignment can be resolved by publishing the shared coordinates in Revit from Arch.rvt into the linked files Struct.rvt and MEP.rvt.
The following are technical and system limitations in Model Coordination:
Maximum models that can be displayed in the clash grid: 100.
Maximum contents of a coordination space:
With automatic clash detection turned on: 1000 models.
With automatic clash detection turned off: 5000 files.
Maximum models in a view: 1000.
Maximum active coordination spaces with clash detection turned on at any one time (combined across Model Coordination and Design Collaboration): 20.
Maximum number of unique folders that coordination spaces can be configured against: 150.
Maximum number of classified clashes: 250000. A classified clash is a clash that is either marked as not an issue, or has an issue create against it. See the Classify and Manage Clashes help topic for more information.
Maximum number of models open in the viewer when creating an issue: 200.
Maximum number of model object exclusions: 50. This includes active and inactive exclusions.
There are a few items that have been reported as issues by customers, which are either expected behavior or are not currently planned to be addressed:
If you notice any other issues, you can report them using the online Contact Support form.