Suddenly Very Slow To Open NWF

daniel.klingspor
Advocate
Advocate

Suddenly Very Slow To Open NWF

daniel.klingspor
Advocate
Advocate

This morning I attempted to open a .NWF and it was very very slow.  Finally opened after maybe 20 mins.  If I perform an update on the .DWG and refresh the live model, again it is very very slow.  I've been working with these files for weeks with zero issues and have not had this particular problem with Navis before.  It is almost like it has to re-cache the model files, which themselves are not that complex or large. 

 

I can open the .NWD files no problem.

 

Navisworks Manage 2021.

 

All .DWG files created in AutoCAD Plant 3D 2021.

 

Suggestions?

0 Likes
Reply
Accepted solutions (1)
636 Views
4 Replies
Replies (4)

hmunsell
Mentor
Mentor

This should probably be in the Navisworks Forum, not the MEP forum.....

 

that said, i now this can be an issue when RVT files are used to make the NWF. Navisworks has to re-cache the file and update the NWC. Not sure how it works with Plant 3D models. Once the NWC I updated, and the RVT hasn't changed, the NWF opens fast.

Howard Munsell
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.



EESignature


0 Likes

daniel.klingspor
Advocate
Advocate

@hmunsell 

 

"This should probably be in the Navisworks Forum, not the MEP forum....."

 

This IS the Navisworks forum.

 

 

0 Likes

hmunsell
Mentor
Mentor

LOL... my bad... i was just in the MEP forum, forgot I switched over šŸ¤£šŸ˜‚šŸ¤£

Howard Munsell
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.



EESignature


0 Likes

daniel.klingspor
Advocate
Advocate
Accepted solution

Tested models on hard drive as opposed to network and there was no difference in performance.

 

Did a complete uninstall of Navisworks and add-ons like exporters and Plant 3D Object Enabler.

 

Fresh install seems to have resolved the issue.  I have no idea what the root cause was.