I am writing to report critical bugs in the Trimble Connect 2.0 Extension and highlight severe functional regressions in the new SketchUp Native Trimble Connect integration.
Currently, our workflow relies heavily on Reference Models (Xrefs). While the legacy Trimble Connect 2.0 Extension has bugs, it contains essential features for our work. However, the Native Integration lacks the management tools necessary for professional projects (e.g., managing 40+ reference models), rendering it unusable for our team.
Below is a detailed comparison and report of the issues:
1. Trimble Connect 2.0 Extension (Legacy Version)
Status: Buggy but functional for complex workflows.
| Category | Issue / Bug Description | Impact |
|---|---|---|
| Bug (Critical) | Tag Visibility & Hierarchy Reset When publishing a model containing visual references, the Tag (Layer) visibility settings often malfunction. Tags may “explode” (expand fully) or lose their visibility state in the published model. (Please see the attached video for a demonstration of this bug) → Must use the Save to Trimble connect in Native Version instead of Publish Model in Legacy version 2.0 | disrupting model presentation and documentation workflow. |
| Bug | Standard Import vs. Linked Model Panel If a file is imported using the standard “Import File” function (instead of “Import Visual Reference”), it does not appear in the “Linked Models” management panel, making it impossible to track or update. However, Imported “Visual Reference Models” appear in the Reference Panel but are locked by default. We have to use a custom Ruby script to force an “Unlock.” to continue working on the Import File. | Forces users to use “Visual Reference” mode, which triggers the “Locked” issue mentioned above. |
| Which lead to Workflow | Locked Visual References Imported “Visual Reference Models” appear in the Reference Panel but are locked by default. | We would like to have the flexible ability, like Autocad attached vs overlay xref |
| Conflict | Extension Conflict (D5 Render) Having D5 Render installed sometimes causes Reference Links to disappear entirely upon publishing to Trimble Connect. | Users have to uninstall/disable other renderers to ensure TC links work. |
Attachments:
- Video: Tag Visibility Bug
2. Trimble Connect Native Integration (New Version)
Status: Missing critical features, not production-ready.
| Category | Missing Feature / Regression | Why this is Critical? |
|---|---|---|
| Missing Feature (Critical) | No “Reference Model” Management Panel The native version removed the “Linked Models” dashboard. There is no UI to list, view status (outdated/synced), or manage connected files. | In a project with 40+ reference models, it is impossible to know which file needs updating. We cannot manage complex projects without a centralized Reference Manager. |
| Missing Feature | No “Visual Reference Model” ModeThe ability to import a lightweight “Visual Reference” (ghosted/reference-only) seems to be missing or replaced by a standard import that does not maintain the same linking behavior as the legacy extension. | We need lightweight references for coordination that do not merge geometry into the active model but remain updateable. |
| Feature Request | Lack of “Overlay” vs. “Attach” Options Currently, references behave like “Attached” (nested references loaded within the file). We need an option similar to CAD/Revit to choose between “Overlay” or “Attach”. | Essential for proper collaboration between disciplines. |
Attachments:
- Video: The important of“ Reference Model” Management Panel
Conclusion & Request
We strongly urge the Trimble Product Team to:
-
Fix the Tag Visibility bug in the Trimble Connect 2.0 Extension immediately, as we are forced to continue using this version.
-
Prioritize the development of a “Reference Manager” panel in the Native Integration that matches or exceeds the functionality of the legacy extension.
-
Restore “Visual Reference” capabilities in the Native version.
We cannot migrate to the Native Integration until these features are implemented. The current Native version represents a significant step backward for professional project coordination.
Thank you for your attention to these critical matters.