Revit Plugin

Revit Plugin

The LocusBIM Revit Add-in covers three workflows. (1) Export to GLB — convert the active Revit model (plus optional linked models) into a single GLB the desktop loads natively. (2) Live Sync — re-export silently every time the user saves, so the LocusBIM 3D viewer mirrors what they see in Revit without a manual export step. (3) Issues panel — same dockable Issues panel that ships in the AutoCAD and MicroStation plugins, hosted as a WPF dockable pane.

Supported Revit versions

Installing

1. Close Revit if it's open.
2. From LocusBIM Desktop, open Help ▸ Install CAD Plugins….
3. The dialog probes HKLM\SOFTWARE\Autodesk\Revit (with WoW6432Node and RegistryVersion fallbacks) and lists every detected Revit year. Click Install — LocusBIM deploys the right TFM (net48 for ≤2024, net8.0-windows for 2025+) to %APPDATA%\Autodesk\Revit\Addins\<year>\ for each detected version.
4. Restart Revit. A LocusBIM ribbon tab appears with three panels: Export, Live Sync, Issues.

Manual GLB export

Click Export GLB in the LocusBIM ribbon. The plugin converts all visible 3D elements (and linked models if you opt in from the selection dialog) into a single GLB. Each mesh carries:

1. Mesh geometry per element with material colours from Revit graphics overrides
2. Element metadata as glTF "extras" — category, level, family, type name, Revit element ID (the stable UniqueId, not the per-session integer), source file, and physical dimensions (area, length, volume, height, width, thickness) in metric units. As of May 2026 the extras also carry workset, phase created, phase demolished, design option,type mark, and type comments — so a coordinator reviewing an element in LocusBIM sees the same field set they would in Revit's Property panel. Fields the source model doesn't populate (e.g., Workset on a non-workshared file) are omitted from the GLB to keep the payload compact.
3. A companion .lbim-ifc.json sidecar for IFC element matching (see the IFC Element Matching chapter)

Live Sync

Live Sync keeps the GLB in LocusBIM up to date as the user works in Revit. Click Live Sync: Off in the ribbon to enable it for the current session.

Issues panel (dockable pane)

The Issues ribbon panel opens a dockable pane on the right side of Revit by default. The pane is a WPF host wrapping the shared WinForms control used by the AutoCAD and MicroStation plugins — so the four- column issue list, status-tinted rows, Refresh button, and double- click-to-focus behaviour are identical across all three.

Revit remembers the dock position across sessions via a stable DockablePaneId GUID. Drag the pane to the left, dock it to the bottom, or tear it off entirely — Revit will restore the same position next time.

Create a LocusBIM issue from inside Revit

Click the green + New issue button at the bottom of the dockable Issues pane. The modal collects Title / Description / Priority (Low / Medium / High / Critical) / Category. If you have an element selected in the active view when you click, the issue auto-links to it by Revit UniqueId — stable across saves, export/re-import cycles, and IFC round-trips, so the link survives any normal project lifecycle. The element label is the Revit Mark (when set) falling back to the family / type name, then to the category. Linked models are supported: an element you select from a linked .rvt is auto-attributed to that linked file by basename.

Click Capture screenshot to grab the active 3D view via Revit's ImageExportOptions — the plugin writes a temp PNG, reads it back as bytes, and the temp file is deleted automatically (no orphaned files in %TEMP%). The captured size is shown next to the button. Submit posts everything to LocusBIM and the new issue appears in the panel on the next refresh.

How it talks to LocusBIM

Same loopback HTTP API as the AutoCAD and MicroStation plugins. Token + port come from %APPDATA%\com.locusbim.app\cad-api.json. The Issues panel is the only Revit-side feature that depends on a running LocusBIM; Export to GLB and Live Sync work standalone (they write files; LocusBIM reads them later).

Troubleshooting