600 mb NWD file size issue
The relationship between RAM usage and size of the NWD on the hard disk is not linear, as the NWD file format employs compression. As such there is no single maximum size; however as you have discovered, a 64-bit operating system enables much larger models to be handled, along with enabling larger quantities of RAM.
I hope that helps,
Jeff
Senior Software Engineer
Navisworks
Autodesk Ltd.
I hope that helps,
Jeff
Senior Software Engineer
Navisworks
Autodesk Ltd.
The limiting factor is generally address space rather than physical memory - you must have enough address space, you can get by without enough physical memory (with some loss of performance). So, you will be able to load much bigger models with 64bit workstation with 2GB (8TB address space) than a 32 bit workstation with 4GB (2GB address space).
It's difficult to say what maximum size of NWD is on a given workstation because it depends a lot on the structure/content of the file. You should have both physical memory and address space greater than between 2 and 20 times the size of the NWD depending on content. Around 5 times bigger is a reasonable guess for most files.
Tim Wiegand
Software Architect
It's difficult to say what maximum size of NWD is on a given workstation because it depends a lot on the structure/content of the file. You should have both physical memory and address space greater than between 2 and 20 times the size of the NWD depending on content. Around 5 times bigger is a reasonable guess for most files.
Tim Wiegand
Software Architect
Accepted solution
Hi Milton,
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?
