Most Revit clash workflows involve exporting to another application and losing the thread between the model and the issue. Nexar Docs runs geometric conflict detection inside Revit, across the host model and any loaded links, and keeps the results attached to the elements that caused them.
A single test handles a quick check between two category sets. Named multi-test sets hold an entire coordination matrix, run in one pass, and import and export so the matrix travels between projects rather than being rebuilt each time.
Host against link and link against link are both supported. Non-physical categories such as grids, levels, lines, text, tags, rooms and views can never be included, and that is enforced in the engine rather than left to the user to remember.
A 3D view with a section box can be created for each clash, and a 2D plan view with a crop region, so a clash is something you can open rather than a row in a spreadsheet. A completed run can be undone from operation history, which removes the clash views and view filters it created.
Detection runs can be saved, listed, reloaded and re-run later. That is what makes a weekly coordination cycle possible without reconfiguring the tests each time.
The Navisworks page compares the Revit clash result with Autodesk Navisworks Clash Detective. It requires an installed and licensed Navisworks Manage, since Simulate and Freedom do not contain Clash Detective, and it runs the bridge in a separate process so Navisworks API assemblies are never loaded into Revit.
Results are grouped as matched, Revit-only, Navisworks-only, or outside the compared scope. That last group matters: rather than quietly dropping pairs neither engine evaluated the same way, it reports them, so a disagreement between two engines is explained instead of argued about.
No. Clash detection runs natively inside Revit across the host model and loaded links. Navisworks is only needed for the optional comparison against Clash Detective, which requires Navisworks Manage.
Yes. BCF 2.1 import and export are supported, alongside Excel, PDF and HTML reports. BCF export asks for the coordinate base so it matches how the model was published as IFC or NWC.
Yes. Host against link and link against link are both supported.
They are non-physical. Categories such as grids, levels, lines, text, tags, rooms and views are excluded by the engine rather than left to the user to deselect.