Manage Prism engine components and repair
Understand the signed components Prism activates for each plan, inspect their health and repair or add optional components safely.
- Applies to
- Current Prism release · Navisworks Manage 2025–2027
- Availability
- Component set follows the verified plan and deployment policy
- For
- Prism users and desktop administrators
- Last reviewed
Why Prism uses components
Prism keeps the Navisworks integration small and activates signed export, validation and target components according to the verified plan. Updates activate a compatible component set after verifying the files and licence access.
What the component groups mean
| Component group | User-facing purpose | How it is managed |
|---|---|---|
| Navisworks integration | Adds the Neobuilt ribbon entry and extracts the selected live model state. | Installed for the detected supported Navisworks years; a connector update can require restart. |
| Prism interface | Renders the format home, workspaces, settings, progress and account states. | Loaded for each new Prism window from the active verified set. |
| Export and validation engine | Resolves profiles, capabilities, jobs, reports and target validation outside the Navisworks process. | Required for licensed export and checked during repair. |
| Native geometry core | Writes IFC, OBJ and STL and provides shared geometry/validation functions. | Required signed component; unavailable native paths stop instead of silently changing the target. |
| Pro target formats | Provides FBX, glTF/GLB and DXF writers. | Activated only when the entitlement and physical component both allow them. |
| Ultra 3D Tiles | Provides 3D Tiles/3TZ writing and the embedded offline coordinate runtime. | Downloaded and probed with the Ultra target set. |
| Ultra OpenUSD | Provides the isolated official OpenUSD runtime and writer. | Available after the installed component passes its compatibility checks. |
| Ultra Fast reader | Decodes an eligible saved NWD into the normal snapshot path. | Used only when Fast is explicitly requested and all eligibility checks pass. |
| Desktop shell | Optional external Tauri host; WebView2 remains the supported fallback. | Optional and never silently opted in by the updater. |
| CUDA | Optional acceleration for byte-identical instancing geometry hashes on very large meshes. | Explicit install only; CPU remains authoritative and available. |
Inspect and manage components
Open Settings
In Prism, open Updates, then Engine components and Manage.
Read the component state
Check which groups are active, required, optional, downloading, verifying, unavailable or waiting for restart.
Repair when needed
Choose Repair active components only after an explicit missing/damaged-component state or support guidance.
Let the full operation finish
Prism downloads, verifies, extracts, probes and activates a complete candidate before it replaces the active set.
Restart when requested
Save work and restart Navisworks when the connector shell changed. Opening another UI window is not enough for an in-process connector update.
Download and repair failures
- A failed candidate does not partially replace the verified active set.
- An export already running uses its original component set until the job finishes.
- Repeated startup failures after an update can trigger a verified rollback to the previous component set.
- A recovery-required or reinstall-required state is different from ordinary repair; follow the exact action Prism shows.
- Do not copy component directories from another user or machine. Local state and entitlements are machine/user bound and copied files do not grant access.
Optional CUDA component
- Install it only through the component manager when the entitlement, device and deployment policy allow it.
- If the compatible CUDA path is unavailable, Prism keeps the CPU result as the authority.
- Measure the relevant large-model workflow before treating the optional module as a deployment standard.