Export settings can affect how Navis files import to Sitelink
If NWC or NWD files exported from Navisworks are not successfully optimizing in Sitelink, there are a couple likely causes.
Sitelink automatically monitors error reports within our processing pipeline, so if we detect issues like this occurring in your project we will reach out to suggest resolutions.
If you notice an issue before we can respond, feel free to contact us directly at support@sitelink.ai or via your account manager for prompt support.
- Resave is Disabled
- "May Be Resaved" must be checked when exporting from Navisworks in order to import the models to viewers like Sitelink and ACC. By default, this box will be unchecked.
- For more details, please see Autodesk's corresponding support article.
- Coordinated Model Complexity/Density
- It is recommended Navisworks models be imported as individual view layers for ease of use in the field and for processing capacity. We suggest splitting by trade and by level, ie "Level 1 - Structural" "Level 2 - Electrical".
- Export NWCs of each view
- Or export NWDs after hiding all content except the relevant content for that view .
- Coordinated models containing multiple trades may be too complex to successfully process through our pipeline. In very rare cases, this may even occur with individual trades or levels within a very large project. In such cases you may choose to split your model into further sections.
- If you believe this is occurring please reach out to Sitelink Support at support@sitelink.ai or via your account manager. This kind of issue is often caused by one or a few elements saved in a very high triangle complexity and can often be resolved without splitting the model further.
- It is recommended Navisworks models be imported as individual view layers for ease of use in the field and for processing capacity. We suggest splitting by trade and by level, ie "Level 1 - Structural" "Level 2 - Electrical".