Uploaded by youtube user BIMcoach:
“When working with Autodesk Navisworks you may run into mapping errors or omissions. This is due to the limitations of property mapping in Navisworks 2014. This video provides a solution to workaround this issue by creating a new property mapping definition.”
Also, remember this if you want to import MasterFormat catalog: at the very end of the Quantification Workbook tab there’s the import/export catalog icon (on top).
In the past, some users have automated Revit to NWC export to happen overnight using customized journal files. Kyle Morin has now created an addin that monitors model changes and automatically keeps your NWC up to date, essentially in “real time”.
You can download it for Revit 2014 here, and view / contribute on the open source page here.
Check out his post at:
Revit to Navisworks: Auto NWC View Exporter – kylemorin.co Blog
Thanks to Michael Priestman, over at this link:
The problem is actually a bit deeper than that. In 2014 release, we added an optimisation whereby we only stored GUIDs when required in order to perform some internal path-matching operations.
However, this broke functionality in some models where GUIDs were re-generated each export. So, we attempted to fix this in the 2014 Service Pack. So whilst we fixed it, we also introduced serious performance problems and a memory leak. Some of those problems were addressed in the hotfix we released, but this didn’t address everything.
The other complicating factor was that when we released 2014 Service Pack, we changed what data was stored in the NWD files, which meant that files saved with 2014 Service Pack would not load properly in vanilla 2014 release. This was mentioned in the release notes for the Service Pack.
We hope to address all the issues around this area for our upcoming release.
I hope this helps to explain the issue a little.
This hotfix resolves three issues:
– Problems resulting from operations that involve clicking in the first column of the Clash results grid, such as collapsing/expanding groups, dragging clashes and resizing columns.
– Issues with material and transparency inconsistency when importing FBX files.
– Issues with the automatic selection of the correct Rendering engine (Presenter or Autodesk)
Navisworks/BIM 360 InfoCenter: Navisworks 2014 Hotfix 3