I have a NWD model file that I am trying to import for use in a Power BI visual. It loads to the space quite quickly, but times out when trying to process. I have used the same model with VCad without any issues. Looking for some pointers to a least get the model loaded into the project. The file is 192 mb
Hey @Andrew_Harper,
Can you share the problematic Navis file with us? I’ll send you a link in the DM where you can upload it.
1 Like
Apologies, forgot to mention the project files are synced from ACC
Hey @Vangel_Kukov ,
Can you share the Speckle model url? You can send a DM if you don’t want to share it publicly.
I cannot share itas it is a confidential project. The project is synced with ACC, RVTs that fail to sync up to 1GB, NWDs that failt o sync up to 4GB.
A post was split to a new topic: Receiving Revit models as Solids in Rhino
Understood. At the moment, our Navis importer can struggle with very large NWD files in the ~4GB range, which is likely contributing to the sync issue you’re seeing.
Improving support for larger Navis files is something we’re actively investigating, and cases like yours are helpful for guiding those improvements.
That said, without access to the model URL, it’s very difficult for us to properly investigate or identify where the sync is failing. If possible, could you send the model URL via DM or reach out to us through Intercom so we can take a closer look privately?
Hi Bilal, the file is not problematic as such, it processed in VCAD without any issues and imported into PowerBi and is now functional. This is a proprietary file and shouldn’t be shared. Sorry I don’t know you from Adam! The is same Issue as Vangel the timeout is after 1200 for NWD files in general, as mentioned this file is less than 1GB.
Thanks for the additional context.
At the moment, the behavior described broadly aligns with current expectations for large NWD imports. Our documentation notes that processing Navisworks datasets larger than roughly 200MB is not guaranteed, particularly given the variability and complexity of aggregated NWD files. Based on the information provided so far, this does not currently appear to indicate a confirmed regression or platform fault.
Bilal’s offer to review the source file directly was made as a courtesy to see whether there was anything unusually pathological in the dataset or import path that could be reproduced or improved internally. We are routinely willing to investigate files under NDA where required.
Without access to the source dataset, however, there is a practical limit to how far meaningful debugging can proceed.
Fair enough; however, given that you, @Andrew_Harper, and @Vangel_Kukov are registered here with Gmail, we don’t know you either. It is worth noting that community forum support operates differently from our dedicated enterprise support and escalation channels. Team and Enterprise customers have access to more direct support pathways for handling production-critical workflows, investigations, and escalation scenarios.
We nevertheless appreciate the feedback and the comparative testing information shared here, as it helps inform our ongoing improvements in handling large Navisworks models.