# AdapterForNavisworks
**AdapterForNavisworks** captures 3D graphics and attributes from Autodesk Navisworks sessions and stores them in a `UPVC` file. This file is then used as input for the **Builder** to generate UPV models.
## Working with **AdapterForNavisworks**
## Prerequisites
**AdapterForNavisworks** works with Navisworks Simulate or Manage, versions 2020 to 2027.
After installing **AdapterForNavisworks**, check in Navisworks that the **CAXperts Adapter for Autodesk Navisworks Plugin** is available under **Tool add-ins**.
## Interactive Mode
Start **AdapterForNavisworks** and select either one **input file** or multiple **input files**. All file types supported by Navisworks are also supported by the adapter.
**Output file:** Defines the path to the `UPVC` output file. This file contains all required information, such as graphics and attributes, needed to generate UDiTH or 3D PDF output using CAXperts **UDiTH Builder**.
If the `UPVC` output file already exists, **AdapterForNavisworks** works in update mode and recaptures only those files whose last modified date has changed.
**AdapterForNavisworks** includes a built-in mode for parallel processing of input files.
For faster processing, it is better to use multiple smaller files rather than one large file containing the same model.
## Advanced Features
### Advanced configuration for capturing graphics
There are two types of `.ini` file: `User.ini` and one `.ini` file per project.
`User.ini` contains general settings that are valid for all projects. `Project.ini` contains only project-specific settings.
## 1. Ignore objects (Project.ini)
The size of the generated `UPVC` file is directly influenced by the number of captured objects. To reduce overall UDiTH model size, you can exclude non-essential objects such as welds, bolts, or washers.
#### Define Custom Object Types
Custom object types are defined in the `project.ini` file using the following syntax:
```ini
[ObjectDefinition]
=
```
**Parameters:**
- ``: Freely chosen name for the object type
- ``: Must match an existing attribute in the UPVC
- ``: Supported operators:
- `=` (equals)
- `<>` (not equals)
- `like` (supports wildcards, e.g. `*`)
- `not like`
- ``: Attribute value to match
Default Configuration
The `Project.ini` file is automatically created in the %appdata%\CAXperts\Navisworks Adapter directory when the input files are processed.
This file contains predefined rules for ignoring objects related to welds. Since this is only an example, the value for [ObjectsToIgnore] is set to 0. The rule is activated with the option 1.
## 2. UseHierarchy (`User.ini`)
Only applicable for the converion of .vue-files of .svf-session files
`UseHierarchy` is a user setting that reads the content of hierarchical labels in SPR.
`UseHierarchy=1` means that all hierarchical SPR labels are read from a `*.vue` file.
### 3. Backup-UPVC
Back up the `UPVC` file before processing in update mode.
In the `user.ini` file, located by default in `%AppData%\CAXperts\Navisworks Adapter`, add the following entry:
```ini
[Settings]
BackupUPVC=1
```
### 4. Primitive Detection for Autodesk Revit Models
Based on specific attributes, **AdapterForNavisworks** can detect pipes and elbows in Revit-based models and replace them with lightweight primitive geometry. This helps reduce the overall triangle count in the model and is especially useful when UPV models are used on devices with limited graphics memory.
### 5. Collection of Attributes from Navisworks Models – default method
Navisworks can store attribute values at different levels in the Selection Tree. In UPV, all attributes are stored directly on the graphical element itself. By default, **AdapterForNavisworks** collects the attributes from the last three levels and stores them on the graphical element in UPV.
You can choose how many levels are used for attribute collection.
This behaviour can be controlled with an additional `user.ini` The `AddParentAttributes` parameter supports values from `1` to `15`, with a maximum of 15 levels for attribute processing.
> Higher settings than `3` can produce a very large number of attributes in many Autodesk-based files and can also increase model conversion times in **AdapterForNavisworks**.
### 6. Collection of Attributes from Navisworks Models – advanced method
There is another way to import attributes from NWD files. Using the “CategorySeparator” option, all attributes from the tabs in Navisworks are imported into the UDiTH model as separate categories.
CategorySeparator=/
### 7. Capture with Navisworks only
AdapterForNavisworks includes a built-in mode for converting SPR files for .vue and .svf formats. However, if you want to convert these file formats using the Navisworks Capture method, you must enable this option.
CaptureWithNavisworksOnly=1
### 8. Excluding .vue files from an SVF session
When converting SVF sessions, you can exclude individual .vue files from the conversion process without having to recreate the SVF session file. This makes it easy to leave out any 3D content that is not relevant to the UDiTH model.
How it works: Place a plain text file named svfprojectname_ExcludeVues.txt into the same directory as your .vue files, where svfprojectname is the name of your SVF project file. Inside that text file, list the names of the .vue files you want to exclude, one entry per line.
Wildcard support: The file naming convention supports wildcards, giving you a flexible way to exclude multiple files at once.
For example: *vendormodels*.vue
This excludes every .vue file whose name contains vendormodels, without having to list each file individually.
## Command line mode
**AdapterForNavisworks** can also be used in command line mode.\
Use the following command to show the command line arguments:
**C:\\\>** **C:\\Program Files\\CAXperts\\Navisworks Adapter\\Navisworks Adapter.exe" /?**
Command line arguments:
**Example:**
`"C:\Program Files\CAXperts\Navisworks Adapter\Navisworks Adapter.exe" -input:C:\data\example.nwd -output:C:\UPVC\example.upvc`
## Log files
The software creates log files in the local `TEMP` directory, for example `C:\Temp\Navisworks Adapter\`. You can also open these files by double-clicking the CAXperts **AdapterForNavisworks** status bar:
