2010
Table Of Contents
- Contents
- Welcome to Autodesk Navisworks Manage 2010
- Installation
- Quick Start to Stand-Alone Installation
- Prepare for Installation
- Install and Run Autodesk Navisworks Manage 2010
- Move to Autodesk Navisworks from a Previous Release
- Install Autodesk Navisworks for Multiple Users
- Quick Start to Network Administration and Deployment
- Set Up a Deployment
- Installation Troubleshooting
- General Installation Issues
- How can I check my graphics card driver to see if it needs to be updated?
- When performing a Typical installation, what gets installed?
- Why should I specify the Project Folder and Site Folder?
- How do I share the Autodesk Navisworks settings on a site and project basis?
- Where are my product manuals?
- How do I register and activate Autodesk Navisworks?
- Deployment Issues
- Licensing Issues
- Networking Issues
- Uninstall and Maintenance Issues
- When adding or removing features, how can I tell what features get installed by default?
- Is it possible to change the installation folder when adding or removing features?
- When should I reinstall the product instead of a repair?
- Do I need my original disk to reinstall my software?
- When I uninstall my software, what files are left on my system?
- General Installation Issues
- Quick Start to Stand-Alone Installation
- Quick Start
- Get a Whole-Project View
- Work with Files
- Native File Formats
- Compatible CAD Applications
- Use File Readers
- 3DS File Reader
- ASCII Laser Scan File Reader
- Bentley AutoPLANT File Reader
- CIS2 File Reader
- DWG/DXF/SAT File Reader
- DWF File Reader
- DGN File Reader
- Faro Scan File Reader
- IFC File Reader
- IGES File Reader
- Inventor File Reader
- JTOpen File Reader
- Leica Scan File Reader
- MAN File Reader
- PDS File Reader
- Riegl Scan File Reader
- RVM File Reader
- SketchUp SKP File Reader
- STEP File Reader
- STL File Reader
- VRML File Reader
- Z+F Scan File Reader
- Use File Exporters
- Manage Files
- Explore Your Model
- Control Model Appearance and Render Quality
- Review Your Model
- Use Viewpoints and Sectioning Modes
- Record and Play Animations
- Work Within a Team
- Share Data
- Work with Files
- Animate Objects
- Create Photorealistic Visualizations
- Simulate Construction Scheduling
- Locate and Manage Interferences
- Autodesk Navisworks Reference
- File Options Dialog Box
- File Units and Transform Dialog Box
- New Link Dialog Box
- Edit Link Dialog Box
- Edit Viewpoint Dialog Box
- Options Editor
- Default Collision Dialog Box
- Collision Dialog Box
- Convert Object Properties Dialog Box
- Culling Options Dialog Box
- Customize Dialog Box
- Customize Keyboard Dialog Box
- Edit Key Frame Dialog Box
- Publish Dialog Box
- Background Settings Dialog Box
- QTVR Object Movie Settings Dialog Box
- Export Rendered Image Dialog Box
- Image Export Dialog Box
- Animation Export Dialog Box
- Glossary
- Index
NOTE If the Type is set to Hard, lines and surfaces will actually need to intersect with any points to register a
clash.
Select Clash Test Options
There are four default clash test types for you to choose from:
■ Hard. Choose this option if you want the clash test to detect actual intersections between geometry.
■ Hard (Conservative). This option performs the same clash test as Hard, however, it additionally applies a
conservative
intersection method.
NOTE This clash test type is only available when in Developer profile. See “Profiles” on page 83 for more information.
■ Clearance. Choose this option if you want the clash test to check for geometry within a specific distance
from other geometry (see “
tolerance” on page 452 for more information). You can use this type of clash when,
for example, pipes need to have space for insulation around them.
NOTE Clearance clashes are not the same as "soft" clashes. Clearance clashes detect for static geometry coming
within a distance of other geometry, whereas soft clashes detect potential clashes between moving components.
Clash Detective supports soft clash checking when you link it to Object Animation.
■ Duplicates. Choose this option if you want the clash test to detect for duplicate geometry. You can use this
type of clash test to check a model against itself to ensure the same part has not been drawn, or referenced
twice, for example.
To select the clash test options
1 If the Clash Detective window is not already open, click Tools ➤ Clash Detective.
2 On the Select tab, select the test you want to run from the Type drop-down list. Any custom clash tests that
have been defined (see “
Create Custom Clash Tests” on page 383) appear at the end of the list.
3 Enter the Tolerance required, which will be in
Display Units. See “Clash Tolerance” for more information.
4 If you want to run a time-based or soft clash test, select the appropriate option in the Link box. For example,
selecting TimeLiner will make Clash Detective produce a clash report based on the Clash Detective settings,
TimeLiner simulation settings, and the project data contained in TimeLiner. For more information and
usage examples, see “
Time-Based and Soft Clash Testing” on page 387.
Time-Based and Soft Clash Testing
Linking to a TimeLiner schedule integrates the features of Clash Detective and TimeLiner together, allowing the
automation of interference checking throughout the lifecycle of a TimeLiner project.
Similarly, linking to an object animation scene integrates the features of Clash Detective and Object Animation
giving you the ability to automatically check interferences between moving objects.
Finally, you can link to an animated TimeLiner schedule (a schedule in which some tasks are linked to animation
scenes), and run automatic time-based soft clash tests.
Time-Based Clashing
Project models can include the static representation of temporary items, such as work packages, ships, cranes,
installations, and so on. Such static objects can be added into the TimeLiner project, and scheduled to appear
and disappear at particular locations, over specific period of time.
As these static package objects 'move' around a project site, based on a TimeLiner schedule, it is possible that
some static package objects could, at some point in the schedule, take up the same space, that is 'clash'.
Select Clash Test Options | 387