Experienced Navisworks Coordinators typically have a very solid workflow in place for grouping clashes into clash groups. Some prefer to do that part manually (with selection and filters), so they can observe and determine which items should be grouped together. Others will use an auto-grouping tool, like bim42 Group Clashes, or iConstruct.
If you are using iConstruct and you wish to use the Navisworks clash group data downstream, you may wish to preserve existing clash groups at each subsequent clash run, and only group the ‘new ungrouped’ clashes. The bim42 Group Clashes tool has a tickbox for this, and iConstruct 2019 provides a filter. If you are using iConstruct 2018 or older, you may be wondering how to preserve existing clash groups and only “push” the grouping rules for clashes that are currently not grouped.
Run the Clash Manager from iConstruct
Find the list entry without a name
iConstruct 2019 has a filter for “Show Ungrouped Clashes”
iConstruct 2018 – select only the ‘unnamed’ Clash Group: ,
Then click “Create Clash Detective Group”
iConstruct will immediately create the relevant groups from only the ungrouped clashes
You can then go ahead and Sync to Revizto, or use the data downstream in some other workflow
Here’s a video from Robert Gadbaw that clearly demonstrates this workflow:
This workflow will allow you to use iConstruct to group your clashes, and preserve those groups when Syncing with Revizto. Revizto has a very solid and customisable connection to Navisworks that includes the ability to sync the clash results with Revizto Issues in both directions.
Models change rapidly at various stages of the project, and it can be useful to review model status between different revisions of the models. What changed? Why?
There are a number of Model Compare tools out there, Navisworks has one built-in and there are addins for Revit. But what if you just want a quick visual check?
Here is one method using Revizto…
Using Two Instances of Revizto and the Issue Tracker to Compare Models
Open two instances of Revizto and put them side by side on your screen (large monitor will help)
On one of the instances, go to Project -> Revisions and open a previous version of your model
You can now navigate between two different versions in these two instances
The issue tracker data is always up to date, so you can use the Issue Tracker to co-locate yourself in each file and check the differences. Just click on the same issue in the Issue Tracker, and then click on 3D to visually compare the models. Obviously, you can also enter data and snapshots into the Issue Tracker as per usual, perhaps to comment on why a particular model changed between versions.
Essentially, this idea was to launch two instances of Revizto and use the Camera Share tool to navigate the same model between them. It was a bit more involved, and it requires you to have access to two different login accounts for Revizto, and two different login accounts for the current machine, and Revizto is installed ‘For Everybody’.
(needless to say that you should be careful to protect the password above)
Open Revizto normally and login
Run this CMD file, and in the new instance of Revizto you can login to a different Revizto account
Open the same Revizto project in each
You can now use the Camera Share tool to ‘drive’ both instances simultaneously. Pretty cool!
In one of the instances, open a previous Revision of the model
*This is where the idea fell down, as Camera Share no longer offered to share camera between two different versions of the model :)* Evidently, it won’t let you navigate non-similar models at the same time.
I re-tooled the steps above from my previous post about logging into multiple Autodesk logins at the same time:
Interesting little release by Dimitar Venkov on Github a few months ago. It is essentially a Python shell for Navisworks 2016. You install by unzipping as per instructions below. You may have heard about RevitPythonShell, but obviously this one is for Navis.
To install, simply extract the zip archive in the below folder:
I’ve had a mixed experience using the Nvidia GTX 980 card in Navisworks and Revit, but I have one particular tip that helped in Navisworks 2017: Turn OFF CPU Occlusion Culling
My CPU is an i7-6700K that I generally OC to 4ghz. But obviously there is some slowdown when both of the Occlusion Culling boxes are ticked.
Aside from the usual tips of using ‘Guarantee Frame Rate’, Automatic Clipping Planes, and playing around with the File Options – Frame Rate, I found that turning off CPU Occlusion Culling and leaving GPU Occlusion Culling on made a real difference for the better.
Navisworks works really well with Point Clouds, particularly in association with Recap. It will usually create ‘voxels’ – groups of points that you can hide or change colour or use in other Navisworks workflows.
However, sometimes the ‘point size’ seems too fine. To modify this, just open up Navisworks Options to Interface – Display, and change the Primitive size for Points to something that looks better. You can choose any size from 1-9.
Also, there are additional settings under File Readers – ReCap:
You can set an ‘interactive point size’ here, which is going to override the point display when you are zooming around or navigating the model.
I typically convert IFCs using the Link method, which results in DirectShape objects. It seems that one of the Architectural files that I converted this way from ArchiCAD to Revit and then to BIM 360 Glue was stopping the colours from getting baked into the BIM 360 Shared View.
To workaround this issue:
Determine what problem model/s you have (possibly those converted from IFC)
Open your Merged Model in Navisworks for BIM360
Hide these problem models in Navisworks scene
Run Appearance Profiler or otherwise apply colour overrides
In the BIM 360 Shared Views pane, click New to make a new Shared View on BIM 360 Glue with the colours ‘baked in’
Go to Glue desktop app and confirm the colours are working
Then, Unhide the problem model here…
And then make a new view in the desktop app
This new view should have all models you want showing, and the colour overrides working ok.
On a related note, you may have seen this warning:
View in model is still processing and some items may not be overridden
It seems that this might put your Glue merged model in a dirty state? Try deleting all views with this message before trying to create Shared Views from Navisworks with colour overrides.
Navisworks is pretty amazing at handling a huge set of properties across a large amount of elements. However, sometimes it can be hard to diagnose why a particular parameter, such as a Shared Parameter, is not displaying or grouping in a way that you might expect.
To figure out what is going on, go into Navisworks Options – Interface – Developer and tick the two boxes: Show Internal Properties Show Property Internal Names
Now, when you use the Properties palette you will see additional information in brackets, which essentially amounts to the Navisworks ‘internal parameter name’ for a given piece of data. Pretty cool!