Why does NavisWorks sometimes start treating updated files as new files in clash detective? Old clashes showing up as new clashes instead of showing as active.
The best answer that I can give is that Navisworks has assigned a new Element ID to the objects in the updated files. Navisworks then sees the objects as entirely new and different objects than the objects involved in the old clashes, and it assumes the old clash was cleared and this one is different.
This can depend on the source files and what is done to "update" them. Some software doesn't modify the object but instead erases the original and adds a replacement. This might also result from exporting to NWC, again depending on the product. From the user's point of view the components are only modifed but as noted technically its a new object and will produce a new clash.
I've looked at the issue as well and I can't really come to any other solution which allows for Navisworks to uniquely identify any object as being the same, even if it is replaced.
I use dwg files and overright the coordination files each week. Is there a way to up this to Autodesk to see if it can be fixed of get a work around?
Hi HankMerkel,
Are there resolved clashes listed with missing items in the Item 1 or Item 2 boxes of the results tab that correspond to these newly found clashes? This would suggest that the item from the old clash is no longer identified by navisworks, and therefore are missing from the result which resolves the clash. A new clash result is then created with the item that has the new identification.
Are you deleting files and appending new versions in Navisworks? If you delete a file any clash results that have items from that deleted file are lost. Even if you were to append the same file back in, the items would be missing from the Item1 or Item2 panels in the result.
If you are simply overwriting the file, the results should remain unless the item in the model is modified in such as way that it is no longer identified by Navisworks as the same item. Some lisp routines that modify items delete them and replace items with new ones.
If you check the entity handles of the items that no longer show up as results and are resolved in the two versions of the DWG, are they the same? You can view the entity handle value by selecting the item in Navisworks and checking the Entity Handle tab in the properties window.
If you open both the previous version and updated version in Navisworks, select both items in the selection tree, and click Tools > Compare, it should show you the differences in the file. Are the entity handles different for the same items in the file? If so, this suggests that the items were replaced and their identifiers used in Navisworks no longer exist in the updated version.
Best regards,
John Lipp
Support Specialist
Product Support
Autodesk, Inc.
Item 1. No they are the same
Item 2. No I over-Wright to old dwg file with a new one, that way it keeps the same name and location.
Item 3 Yes the entity handles are the same.
Item 4 Can not do as I over-Wright the files with new ones so the coordination model stays updated at all times.
I am a General Contractor pulling models in from my subcontractors.
Hi HankMerkel
For Item 4, you stated that you can’t check this because the files are overwritten. Do you have the older versions of the DWG files or is a matter of them having the same filename?
If you open a new session of Navisworks and rather than open the NWF, if you append both versions of the DWG and run the compare checking only for differences of Unique ID and have the “Save each difference as a set” is there an unmatched set listed? Are the items in the sets the same items that are appearing in the new clash results?
Would you be able to log a support request through the subscription center linked below and I’ll have a look at the DWG files to see what the differences are that may be causing the issue?
http://subscription.autodesk.com/sp/servlet/public/index?siteID=11564774&id=11607975
Best regards
John Lipp
Support Specialist
Product Support
Autodesk, Inc.