The Settings tab of the Enhance window controls how your clash titles are written: the naming standard, the language, where the text goes, and which clashes are included. This article walks through every option.
Choosing a naming standard
Under Select Naming Standard:, the Naming Format dropdown offers six standards. A live Preview panel shows each one — use the Show Example / Show Structure toggle to switch between a real-world example and the underlying template.
| Standard | What it produces | Example |
|---|---|---|
| Basic | Simple format showing the names of the clashing elements | Wall-101 vs. Column-A2 |
| Detailed Descriptive | Comprehensive format including element types, categories, and their locations | Wall-101 (Basic Wall) at Level 1 clashing with Column-A2 (Structural Column) at Level 1 |
| Component ID Information | Focuses on element types and their unique identifiers | Basic Wall (W-101) clashing with Structural Column (C-A2) |
| By Discipline | Organizes clashes by the disciplines of the involved elements | Wall-101 (Architectural) clash with Column-A2 (Structural) |
| AI Preferred | Lets the AI decide the most relevant information for each clash | Varies per clash |
| Mixed | The AI varies freely across all the other standards | Varies per clash |
Which should you pick?
- Basic — quick reviews and simple coordination.
- Detailed Descriptive — formal documentation and comprehensive reports.
- Component ID Information — tracking specific elements across revisions.
- By Discipline — coordination meetings and discipline-based workflows.
- AI Preferred or Mixed — when you would rather let the AI judge what matters for each clash.
Agree on one standard with your team so titles stay consistent across models and publishes.
Scope: which clashes get processed
- New Clashes Only (Default) — only clashes with the New status are processed. Untick it to include clashes in other statuses too.
- Apply To: — choose what gets renamed:
- Individual clashes only (default)
- Individual clashes and group titles — also renames clash groups
- Group titles only — renames groups and skips the individual clashes inside them
- Include Previously Updated Clashes — by default, clashes you have already named with ClashWise are skipped on later runs. Tick this to re-process them (for example after changing your naming standard or language). Re-runs are matched against your own previous updates.
Output: where the text is written
Under Update Option:, choose one:
- Title (default) — replaces the clash result's display name. This is what most teams want.
- Description — writes the generated text into the clash's description field and leaves the title unchanged.
- Comments — adds the generated text as a comment on the clash, leaving both title and description unchanged.
Extras
- Include Original Clash Title — keeps the original name (for example
Clash847) as a prefix, so you never lose the original reference. - Include Clash Test Name — prefixes each title with the name of its clash test.
With both enabled, a title looks like: Clash847 [Test name]: {AI title}.
Language
The Language dropdown defaults to Current Culture (your Navisworks display language) and offers 11 languages: English, German, Spanish, French, Italian, Japanese, Korean, Portuguese (Brazil), Russian, Chinese Simplified, and Chinese Traditional. Titles, descriptions, or comments are generated in the language you pick — regardless of the language of the plugin's own interface, which always follows Navisworks automatically.
AI Model
The AI Model panel shows which local AI model will do the naming (or No model selected if none is active). Click Manage models... to open the AI Models window, where you can download, activate, test, or delete models — see the Local AI Models article.
Tips
- Your settings are remembered between sessions, so you only need to configure them once per preference.
- If titles come out in the wrong language, check the Language dropdown before anything else.
- Larger AI models generally produce more polished phrasing but run slower — see the Local AI Models article for the speed/accuracy trade-off.
Related topics
- Getting Started with Enhance
- Local AI Models
- Running and Reviewing