Karo.WhyHidden is a Revit visibility-diagnostics add-in from Karo Modum. It investigates why a known element does not appear in a particular view, bringing together checks that would otherwise require opening several Revit settings dialogs. The vendor describes 16 visibility checks covering direct hiding, graphics settings, spatial clipping, worksets, phasing, design options, linked-model display, and view-template control. Findings appear as diagnostic cards identifying relevant settings, filters, or worksets. Selected issues have one-click fixes; others receive guidance. The product is primarily a troubleshooting aid rather than a model-wide QA engine or an automatic redesign of view standards. [1-3]
Typical Workflow
- Identify the element: Select it in a view where it is visible, or use its element ID. This is a targeted investigation of a known object, not a search for an unidentified missing object.
- Activate the problem view: Switch to the plan, section, elevation, or 3D view where the element should appear.
- Run Why Hidden: Launch the command from the Karo ribbon tab.
- Review diagnostics: Read the cards identifying visibility blockers and the settings responsible. Multiple conditions may apply at the same time.
- Resolve appropriate conditions: Use an available quick fix or follow the guidance, retaining control over office templates and shared standards.
- Verify and communicate: Confirm the intended display and copy the formatted diagnostic report into a team chat or task tracker. [2]
The 16-Point Diagnostic Scope
The vendor’s technical checklist identifies the following mechanisms. These are diagnostic categories, not a promise that every possible family, geometry, or linked-model edge case can be conclusively resolved. Applicability depends on the selected element and view type. [3]
- Manually hidden element: The object was hidden individually in the view.
- Category visibility: Its model or annotation category is disabled in Visibility/Graphics.
- View filters: A matching filter suppresses visibility or applies an invisible-line treatment.
- View range: The object falls outside the plan’s applicable vertical display range.
- 3D section box: An active section box clips the geometry.
- Workset visibility: The element’s workset is not visible in the view.
- Phase and phase filter: Temporal display settings exclude the element.
- Design options: The element belongs to an option not displayed by the view.
- Crop region or model extents: The object lies beyond the view’s spatial boundary.
- Annotation crop: Annotation falls outside the annotation crop boundary.
- Family detail-level settings: Family geometry has display restrictions at Coarse, Medium, or Fine detail.
- Temporary Hide/Isolate: A temporary visibility session suppresses the object.
- Element graphic overrides: An individual override applies an invisible-line treatment.
- View-specific ownership: A 2D element belongs to another view rather than the target view.
- Revit link overrides: Linked-model display is governed by host-view or linked-view settings.
- View-template control: A governing template controls settings that cannot be changed independently in the view. [3]
Key Features and Practical Value
- Consolidated investigation: Reduces repeated checks across Visibility/Graphics, filters, view ranges, worksets, and templates.
- Specific findings: Diagnostic cards identify the implicated setting, filter name, or workset, making results more actionable than a generic visibility warning.
- Multi-cause review: Helps expose overlapping blockers, so resolving one condition does not necessarily end the investigation.
- Selective quick fixes: The demonstration lists Unhide, Reset Invisible Lines, and Restore Temporary Hide as examples. Not all diagnostic categories have automated fixes.
- Template-aware diagnosis: The vendor states that diagnosis does not require unlocking or detaching view templates. This should not be interpreted as permission to make broad template changes without review.
- Clipboard reporting: A formatted report can be copied for support requests, coordination messages, and issue tracking. Public evidence reviewed confirms clipboard output, not dedicated Excel or PDF export.
- Local execution: The vendor describes a standalone add-in running locally inside Revit without cloud processing. [2]
Applications in BIM Production and QA/QC
WhyHidden is most relevant to frequent, element-specific visibility support: a component missing from a plan, a tag clipped by annotation boundaries, geometry excluded by a workset or filter, or linked content displayed differently between views. For BIM support teams, a consistent diagnostic report can reduce back-and-forth questions and provide a clearer record of the setting involved. For production teams, explicit findings may reduce trial-and-error changes that inadvertently disrupt documentation standards. These are potential workflow benefits, not independently measured productivity results.
Limitations and Evaluation Considerations
- Not an exhaustive guarantee: Sixteen checks do not establish coverage of every Revit visibility interaction. Family internals, masking or occlusion, specialized categories, and complex nested links warrant pilot testing rather than assumed support.
- Known-element prerequisite: The published workflow requires selecting the element or knowing its ID. It does not establish a capability to reconstruct a deleted object or discover an unknown missing element.
- Intent still requires judgment: An element may correctly be hidden by design. A detected blocker is not automatically an error that should be removed.
- Broader effects of changes: Editing a shared template, workset display rule, phase filter, or link setting can affect more than the selected element.
- Linked-element behavior needs confirmation: The checklist includes link overrides, but the material reviewed does not fully establish selection procedures and coverage for nested links or every host/linked-view combination.
- No independent benchmark: Claims of instant diagnosis and time savings come from the vendor. No independent performance or accuracy testing was established in this review.
- Documentation visibility: A technical manual is referenced in the demonstration, but its contents were not recovered in the search results. Exact installer version, language options, detailed system requirements, activation connectivity, and complete unsupported-case lists remain unverified.
Compatibility, Pricing, and Licensing
- Revit support: The vendor demonstration lists Revit 2023, 2024, 2025, 2026, and 2027.
- Supported graphical contexts: Plans, sections, elevations, and 3D views are advertised; individual checks apply only where relevant.
- Trial: A 14-day free trial is advertised.
- Subscription: US$9 per month or US$69 per year, as advertised in the vendor demonstration available during this review.
- Activation: Transferable machine activation is advertised. Seat counts, concurrent-use rights, and transfer procedures should be confirmed before purchase.
- Commercial terms: Karo Modum’s terms describe recurring billing and restrictions, and state that digital purchases are generally non-refundable after delivery, activation, or use, subject to applicable law. The developer disclaims Autodesk affiliation or certification.
- Verification: Confirm live checkout pricing, taxes, subscription conditions, compatible builds, and organizational deployment requirements before purchase. [2, 4]
Recommended Pilot
- Build a controlled test set with known hiding causes across plans, sections, elevations, and 3D views.
- Include overlapping conditions, such as an individually hidden object whose category is also disabled.
- Test template-controlled settings, worksets, phase filters, design options, annotation crops, and host/linked-view combinations.
- Compare findings against the known cause and record false positives, omissions, and situations requiring manual interpretation.
- Apply quick fixes only in a test model and verify their scope, reversibility, and effect on shared standards.
- Review copied report content for usefulness and project confidentiality before sharing outside the project team.
- Validate installation, activation, compatibility, and local-processing claims with IT, then document approved support procedures.
Overall Assessment
Karo.WhyHidden is a focused troubleshooting tool whose strongest advertised combination is consolidated visibility checks, specific diagnostic findings, selective quick fixes, and shareable reports. Its potential value lies in reducing repetitive investigation while preserving deliberate control over view standards. It is best positioned as an assistant to Revit troubleshooting, not a guarantee that every visibility problem can be automatically diagnosed or repaired. Teams with frequent missing-element support requests should evaluate it through the trial using representative project conditions, especially overlapping blockers, templates, and linked content.
Sources
- Karo Modum — official product catalogue. Developer context and product discovery. The indexed excerpt did not expose the full WhyHidden product section.
- Karo — How to Find Missing & Hidden Elements in Revit | Karo WhyHidden. Vendor demonstration and description; principal evidence for workflow, cards, quick fixes, clipboard reporting, local execution, Revit versions, trial, pricing, and transferable activation.
- Karo Modum — Why Is an Element Hidden in Revit? The 16-Point Visibility Troubleshooting Checklist. Vendor technical reference, updated September 2026; source for the 16 diagnostic categories. This is vendor-authored reference material, not independent validation.
- Karo Modum — Terms of Service & EULA. Commercial and licensing context; effective August 19, 2026.
Advertisement
No comments:
Post a Comment