Join Jim Cowan for an in-depth discussion in this video Navisworks options and settings, part of Navisworks Advanced.
- So I'd mentioned in the product, that, under the application button, and under options, this is where you control the settings. And the ones that have changed that are important are under the display options, 'Feet and Fractions' of a foot. Under the selections, I can define a color so that when I select an object it will show as that color.
Under the Viewpoint Defaults, it's important that you have switched on Save Hide and Required Attributes, and Override Appearances, otherwise when you turn off the display of part of a model, say I've got a structural model appended and an architectural model appended in a particular view point it won't remember what was hidden if these buttons aren't checked on when you create the view in the first place, you'd have to go to individual view and change it, this is the default that these are switched on for each viewpoint.
If I tell Navisworks that something is required, it means it doesn't drop out when I navigate through the model, and that's typically done where you want to maybe make the structural model always visible as a priority to other objects that are in the model as you navigate through the model. Override Appearance would be if I change something, I want to remember the changes. Just going to show the main ones here, so not everything that's on this. Under 'Model' and 'Performance', I had turned on this option that says Close NWC/NWD files on loading, this would mean that if other members of the team are producing, cash files, say, that's being linked or appended to my file set, it won't give them a message that the file is locked, because it's been closed as soon as I attached it, making it available for editing while I'm continuing to work with it.
Under 'Tools', this will be where you can change settings for anything that you're using. We're going to look primarily at the clash detective, so when I do clashes, you'll see that there's two columns where the clashing items are highlighted in a particular color, if you didn't like the red and the green, maybe you're color-blind, you have a problem seeing these colors distinctly, you can change it to whatever color you want it to be. You can tell it how closely to move to the clash, this would be your location for changing any settings to do with Clash Detective.
The major option here that I want to show you is the file readers, so let me close this to give me some space. File readers control how the data and the graphics of the authoring file are translated into surfaces, triangulated surfaces, with data attached to them. We're going to be using primarily drawing files, So if I looked at dwg, what I had done was change this value that said one, which means that there's a mesh around a duct, and by changing it to eight what I'm saying is there will be eight facets for every quadrant of the rounded duct.
Trying to find a balance between keeping the files as small as possible but as accurate as needed for things like clash tests. Typically best practices don't bring in frozen layers, don't bring in XRefs, you typically want to attach all your model files one at a time. That's the rationale behind the settings that I have there. If you have, for example text in an autocad file, I would want to bring in that text, you'll see at this point we bring in some grids that are autocad grids.
And, the other type of file that we're using, the file reader for Revet projects, so Revet projects I want the data to come in, if I don't bring in that data I won't be able to do things like in my search sets say look for this system type of supply air. If there's data in the model I won't be able to use search sets to find the objects that have the data attached to it.
Project Internal Points, I don't want to bring in lights or URLs in say Revel families that are links to maybe a pump might have a link to a specification on a website, and I can bring them in and they would become links inside Navisworks, at the moment I'm saying don't do that. Don't bring in any linked Revet files, don't convert my cad files. Levels is an important one to have on, typically the levels correspond to each floor of the building.
What this is doing is making sure that I'll be able to look at the selection tree and drill down to where I'm looking at individual levels inside the file. I have turned off convert room geometry as also applies to space geometry. These are invisible objects in Revet and I don't want them at the moment inside my Navisworks file. This one is a very important one, this means that when I attach a Revet file, if there is a view in that file with the word 'Navis' in it, then I will get the content from that view, and then I'll show you how in Revet you can control categories like is that view displaying walls, furniture, roofs, ceilings.
So what this lets you do is have one view, that you can use to dictate what you want to have when you bring it in to Navisworks. Those are the options that we'll use in the project.
- Navigating the Navisworks user interface
- Creating Navisworks files
- Revit view templates
- Creating and reusing search sets
- Scene animation using search sets
- Exporting a viewpoint animation and a render animation
- Using grid plan views
- Appending and creating a clash view
- Updating the clash test
- Visualizing clashes