Solved! Go to Solution.
I know this topic is over a year old however, I also have been running into similar issues. I'm questioning how some of these files are being put together. For more of my BIM files, I barely reach 500"KB" because I try to keep my 3D drawing simple.
On a project where we are working with several trades, I've notice file sizes that easily are 10"MB" or higher. As a result, when the final assembly files is being reviewed we are in the 100+MB file range.
In my effort to "reduce" the file size, I've found simple AutoCAD files just "NEEDED PURGING" to bring the size down below a megabyte. Has anyone looked into this, or maybe talked about this as a "CAD Standard"?
It's an interesting subject, how far back should you strip your files before bringing them into Navisworks? Purging Models is one answer but there may be unexpected consequences if you strip back too far. You have several places where the bulk of the model size may come from.
Geometry - Particuarly detailed models, if you have lots of pipes and rounded objects in the model then you can simplify how these come through to Navisworks by reducing the facetting factor, this reduces the detail on the model and may make the pipes look angular rather than round, but can massively reduce the number of triangles saved in the model, reducing file size. Depending on what you are doing with the models this may have a detrimental effect on the accuracy of Clash tests and the quality of Presenter renders.
Properties - Again depending on what you are doing, these may be essential for the Search Sets you use in Timeliner, Clash detective and other review functionality. You need to think about where else might this model be used further down the line, will these properties be needed then. If they won't then purging the properties from the model or Publishing with 'Prevent Object Property Export' switched on (make sure the model can be resaved) will strip the model back.
Additional items - Obviously different file formats have different quirks. For example in the DWG options below, you'll see a range of things you can convert or not into Navisworks, Items that are Off, Frozen, Groups, Text and Views amongst others. This applies to most file formats and can be found in the Exporter Options or if Importing under Options > File Readers. Be careful what you switch off though, if you might need those x-refs later then it might be more difficult adding them as an afterthought.
Navisworks Data - As a recommended workflow we would suggest having a geometry and properties NWD or NWC referenced by a master NWF which contains all the Navisworks specific data, allowing easier changes to the native model and more manageable file sizes. Obviously the more, views, materials, clash tests, comments and Timeliner Simulations you have, the more your file will grow, if size is an issue, do you need multiple Master NWF's for different jobs? Does the person who looks after clashes on Level 1 of your building really need the Presenter materials and lighting for the entire model?
In the project I'm working on, I'm seeing drastic slowdowns in my models opening. I've been opening the .nwf files so I can work on selection sets, rules, and clash reports. My .nwd sizes on this project are 92mb, 90mb, 4mb, 131mb, 37mb, and 20mb.
I also have a combined model I created from the .nwd files that's sitting at 375mb.
All of them open pretty fast in NWS, even the 375mb. If I'm opening the .nwd, it's on the screen in about 45 seconds.
I'm running a Dell Precision Quad Core M6500 with 16gb of ram on my laptop and a Dell Precision T3500 on my desktop where i have my models regenerating in the background on an hourly basis. I actually have two of those computers, the regen routines are split between the two. The first T3500 has 24gb of ram and the second has 12gb..
When opening one of my 131mb .nwf models on my laptop, it can take up to half an hour to go through all the files. It contains 285 drawings from Revit and Autocad MEP.
On my 88gb model, I have 235 drawings from Autocad MEP, Revit Structure, and Revit Architecture.
I definitely think the amount of Ram is a big issue. My desktop will run circles around my laptop on some models. The 131mb model is a good example of it. On the Desktop, the .nwf will open in less than 10 minutes where on the laptop, that same .nwf can take over a half hour to open..
On the 88gb model, they're a lot closer to the same amount of time.
RAM is a huge issue in general performance, as alluded to in this blog post.
You should find that most of the time spent will be converting the DWG files into a form Navisworks can easily handle. Files from Revit will have already been converted to NWC's. Effective use of cache files can reduce this conversion process as much as possible.
Another setting that has to be attended are the
"convert References" in the DGN section and the "convert xrefs" in the DWG version.
Switching this off and appending the CAD files one by one, and only attach the ones you need will increase the RAM needed and the time needed to open an NWF a lot, and the file size of the NWD you are going to create also.
Also, there is a difference in file size beween version 5.0, 2009 and later if you create an NWD of the same CAD files.
2009 creates smaller NWD,s
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.