Home / Guides / Trace
View panel

BIMIO Trace

Why can't I see this element here? A live checklist of every reason an element can be hidden.

Overview

It has happened to all of us: you know the wall, the light fitting or the tag is in the model, but it does not appear in this view. You start going through Visibility/Graphics, the view range, the filters, the phases... and half an hour later you still do not know what the reason was. Trace turns that blind hunt into an orderly diagnosis.

You point it at an element (by clicking on it, inside a link or by its ID) and at one or more views, click Analyze, and Trace works through a live list of checks: 28 possible reasons grouped into four themed cards, from the most basic to the most subtle. Each check turns green if it is ruled out, amber if it could be the cause and red if it is definitely the cause, with a one-line explanation.

As well as diagnosing, Trace helps you act: the most common causes have a one-click fix (Fix it) reversible with Ctrl+Z, you can jump to a view where the element does draw, copy the findings to paste into an email or an issue, and export a self-contained HTML report that works offline. The tool is read-only: it does not touch the model unless you expressly click Fix it.

Who it's for

Architects, modellers and BIM managers who lose time working out why an element does not appear in a particular view; also coordinators who need to document and communicate that diagnosis to the team. No advanced knowledge is required: the tool itself teaches you the correct order of checking.

Requirements

  • Revit 2022 to 2026 with the BIMIO suite installed (the BIMIO tab on the ribbon).
  • An open model with at least one active graphical view.
  • To diagnose elements from linked models, the link must be loaded; if it is unloaded, Trace can only evaluate the link layer and will ask you to reload it for the full diagnosis.
  • No internet connection is needed: the exported HTML report is self-contained and works without a network.

Where to find it

BIMIO tabView panelTrace button

The button opens the BIMIO · Trace — why can't I see this? window, which is modeless: you can keep working in Revit while it is open.

If the window is already open, clicking the button again brings it to the front instead of duplicating it.

If you open Trace with an element already selected in Revit, the header recognises it and you can analyse it straight away without picking it again.

Key concepts 8 terms

Check
Each of the 28 known reasons why an element may not be visible in a view: category switched off, hidden in the view, cropping, view range, phase, filters, workset, design option, and so on. Each check is evaluated independently and returns a verdict.
Verdict
The result of a check for that element in that view. Green with a tick: ruled out, not the reason. Amber: possible cause, it matches and could be the reason. Red: definite cause. Grey (N/A): the check does not apply to that combination of element and view, for example the view range in a 3D view.
Themed cards
The checks are grouped into four cards shown in a 2x2 grid for each analysed view: Existence & selection (the element exists and its link is loaded and visible), Visibility & graphics (V/G, hidden states, filters, detail level), View extent (crop, view range, section box, scope box, far clip) and View context (phase, worksets, discipline, design options, groups).
Complexity badge
Each card in the analysis carries a BASIC, INTERMEDIATE or ADVANCED label (that of its most subtle cause), and in the built-in manual and in the HTML report each rule shows its own. It indicates how subtle the cause is and helps you learn the natural order of review: basics first, advanced later.
Live sweep
When you click Analyze, Trace works through the checks one by one with a short pause between steps so you can watch the process. The view being checked expands and the finished ones collapse; when everything is done they all expand again with the causes ordered first. The Fast toggle removes the pause for bulk analyses.
Link layer
When the element lives in a linked model there are two levels of possible causes: those of the link itself in the host view (link unloaded, link hidden, link display settings) and those of the element inside the linked document. Trace evaluates both levels.
One-click fix (Fix it)
Five binary, reversible causes have a direct fix button: temporary hide/isolate, category switched off, element hidden in the view, subcategory switched off and workset not visible. The fix runs in a single transaction, so a single Ctrl+Z reverts it.
Built-in manual
The question-mark button in the header shows a manual generated from the rules themselves: every possible reason with an explanation of how to correct it in Revit and its complexity badge. Because it is generated from the rules' code, it never goes out of date.

The interface

The Trace window is organised from top to bottom: a header with the title, a status line that guides you along (for example Select an element (or enter an ID), then Analyze when it opens, or the diagnosis summary when it finishes) and the manual button; below it, two columns for choosing the element and the views to check; then the results area with one collapsible section per view; and at the foot, the action bar with the Fast toggle and the buttons for copying, exporting, finding a view and Analyze.

The interface texts are in English (Analyze, Pick element, Fix it...), but the structure is so visual that you learn it in a couple of uses: green ruled out, amber possible, red definite.

Main Trace window after an analysis: element and view selectors at the top, one expanded view section showing the four 2x2 cards with one cause in red (for example Element is not hidden in this view marked as the cause), several checks in green, and the bottom bar with the Copy findings, Export report, Find a view where it shows and Analyze buttons.
assets/shots/trace/fig-02.pngMain Trace window after an analysis: element and view selectors at the top, one expanded view section showing the four 2x2 cards with one cause in red (for example Element is not hidden in this view marked as the cause), several checks in green, and the bottom bar with the Copy findings, Export report, Find a view where it shows and Analyze buttons.
Main Trace window after an analysis: element and view selectors at the top, one expanded view section showing the four 2x2 cards with one cause in red (for example Element is not hidden in this view marked as the cause), several checks in green, and the bottom bar with the Copy findings, Export report, Find a view where it shows and Analyze buttons.
Header and status lineShows the Trace title and, below it, a status sentence that changes with the moment: which element is ready, how many views are being checked, the final diagnosis summary or the result of the last action (report saved, findings copied...). On the right, the question-mark button opens and closes the built-in manual.
ELEMENT selectorLeft column. A toggle with two modes: Pick element (point with the mouse) and By ID (type the element's numeric ID). In Pick element mode there are two buttons: Pick element… for elements in the host model and In link… for elements inside a linked model (with Tab to cycle through candidates). Next to them you see the label of what you have picked, for example the element's category and name.
VIEWS TO CHECK selectorRight column. Another toggle with two modes: Active view (check only the active view) and Pick views… (open a dialog to choose several views). In Pick views… mode, the current selection is summarised under the toggle, for example Active view + 3 views. Clicking Pick views… again reopens the dialog to change the selection.
Views to check dialogOpens from Pick views…. It contains an Active view checkbox (always uses whichever view is open at the moment of analysis), a search box that filters by name or by view type, a header checkbox to tick or untick all visible views at once, and the list of the project's graphical views with their name and type. You can click rows to highlight them (with Ctrl or Shift to extend the highlight), and ticking the checkbox of one of them propagates the change to the whole highlighted range. A summary at the bottom reflects the selection, for example Active view + 4 views. Confirm with Done or discard with Cancel.
Filter pillsThey appear when there are results. The global row Show: Causes (n), Ruled out (n) and N/A (n) filters which verdicts are shown across all views at once; each view section also has its own pills. By default causes and ruled-out checks are shown, and N/A ones are hidden to reduce noise.
Results sectionsOne collapsible section for each analysed view. The header shows the view's name and type plus a summary (Found the cause, 2 possible causes, Nothing found) and collapses or expands with a click. Inside, the four themed cards in a 2x2 grid; each row is a check with its status icon, its title, an explanatory detail and, where relevant, the Show where (navigate to the element in that view) and Fix it (one-click fix) links. When the analysis finishes, the rows are reordered with the causes first.
Action barAt the foot. On the left, the Fast toggle that turns off the step-by-step animation. On the right: Copy findings (copy the causes to the clipboard), Export report (save and open the HTML report), Find a view where it shows (jump to a view where the element does draw), Stop (halt a running analysis while keeping the partial results) and the main Analyze button. When the window opens only Fast and Analyze are visible: the three results buttons appear after the first analysis, and Stop only while an analysis is running.
Built-in manualReplaces the whole working area (selectors, results and action bar) when you click the question-mark button; only the header stays visible. It lists every possible reason grouped into the same four cards as the analysis, each with its complexity badge and a line on how to correct it in Revit. Close it by clicking the X on the same button.

Step-by-step workflows 8 workflows

1

Diagnose why an element is not visible in the active view

6 steps

Goal. Get, within seconds, the cause preventing an element from appearing in the view you are working in.

  1. Open the view where the element should be visible and click the Trace button on the BIMIO tab, View panel.The window is modeless: you can move it to a second monitor and keep working in Revit.
  2. With Pick element mode active, click the Pick element… button and click the element in any view where you can see it (for example a 3D view or a different plan).The Trace window minimises itself during the pick so it does not get in the way and comes back when you finish, even if you cancel with Esc. Next to the button you see the label of what you picked, for example Walls "Basic Wall".
    Trace window with the picked element's label next to the Pick element… button and the header reading Element ready. Pick views and Analyze.
    assets/shots/trace/fig-03.pngTrace window with the picked element's label next to the Pick element… button and the header reading Element ready. Pick views and Analyze.
  3. Leave the view selector on Active view.Whichever view is active in Revit at the moment you click Analyze will be checked.
  4. Click Analyze and watch the sweep: each check goes from pending to green (ruled out), amber (possible cause), red (definite cause) or grey (does not apply).The sweep order is instructive: first existence and selection, then visibility and graphics, view extent and view context.
    Section for the active view mid-sweep, with several rows in green, one in amber and the header summary reading Checking…
    assets/shots/trace/fig-04.pngSection for the active view mid-sweep, with several rows in green, one in amber and the header summary reading Checking…
  5. Read the summary in the section header (Found the cause, 1 possible cause…) and review the red and amber rows, which end up ordered at the top of each card.Every row with a cause includes a one-line detail that explains exactly what is going on, for example which view filter is hiding it.
  6. Use the Show: Causes / Ruled out / N/A pills if you want to hide the ruled-out checks and keep only the causes.N/A rows are hidden by default; turn them on if you also want to see what did not apply.
Result. You know for certain which view or element setting is preventing it from being seen, with a specific explanation for every cause found.
  • If you already had the element selected in Revit before clicking Analyze, Trace uses it directly without you having to pick it again.
  • You can click the section header to collapse or expand it at any time.
2

Analyse an element from a linked model

4 steps

Goal. Find out whether the problem lies in the link itself (unloaded, hidden, display settings) or in the element inside the linked model.

  1. In the ELEMENT selector, with Pick element mode active, click In link… instead of Pick element….This mode can reach into links; the normal mode only reaches elements in the host model.
  2. Click the element inside the link; use the Tab key to cycle through candidates if Revit highlights a different element.Trace automatically rejects reference planes and other references that are not model elements, so you do not capture the work plane by mistake.
  3. Check that the label reads Linked: with the element's category and the link's name, choose the views and click Analyze.
    Element label showing Linked: Doors "Door 90" · ARQ-Vinculo.rvt and the first card with the link checks.
    assets/shots/trace/fig-05.pngElement label showing Linked: Doors "Door 90" · ARQ-Vinculo.rvt and the first card with the link checks.
  4. Review the Existence & selection card first: that is where the link-layer checks live (The linked model is loaded, The link is visible in this view, The link's display settings show it).Under Visibility & graphics there is also an advanced check that verifies whether Revit actually draws that linked element in the host view.
Result. A two-level diagnosis: causes from the link in the host view and causes from the element inside the linked model, without having to open the link file.
  • If the link is unloaded, Trace flags it as the cause and leaves the element-level checks as N/A with a notice to reload the link for the full diagnosis.
  • The Show where links and the navigation actions act on the link instance in the host model.
3

Analyse an element by its ID

3 steps

Goal. Diagnose an element you cannot pick with the mouse, for example one quoted in an audit report or in a Revit warning.

  1. In the ELEMENT selector, switch the toggle to By ID.
  2. Type the element's numeric ID in the text field.It is the same ID shown by Manage → IDs of Selection, Revit warnings or the reports from other BIMIO tools.
  3. Choose the views to check and click Analyze.If the ID is not a valid number or does not exist in the model, the status line tells you so without running anything.
Result. The same full diagnosis without having to locate the element visually first.
  • By ID mode only accepts IDs from the host model; for elements in a link use In link….
4

Check the same element in several views at once

6 steps

Goal. Know in which views it is visible and in which it is not, and for what reason in each one — useful when a tag or a piece of equipment disappears only on certain drawings.

  1. In VIEWS TO CHECK, click the Pick views… toggle.The Views to check dialog opens immediately; if it was already selected, clicking it again reopens it.
  2. In the dialog, tick the views you want to check; use the search box to filter by name or type and the header checkbox to tick or untick all the visible ones.Only real graphical views are listed (no view templates). The Active view checkbox additionally adds whichever view is open at the moment of analysis.
    Views to check dialog with the search box, the Active view checkbox and several plan views ticked.
    assets/shots/trace/fig-06.pngViews to check dialog with the search box, the Active view checkbox and several plan views ticked.
  3. Click Done and check the summary under the toggle, for example Active view + 4 views.
  4. Turn on the Fast toggle if there are many views, and click Analyze.Fast removes the animation pause between checks; with several views the analysis finishes much sooner.
  5. During the sweep, the view in progress expands and the finished ones collapse with their summary; when it finishes, they all expand so you can review them at a glance.The global header summarises the whole set, for example Cause found in 2 of 5 views.
    Several view sections, some with a Found the cause summary and others with Nothing found, and the global filter pills visible.
    assets/shots/trace/fig-07.pngSeveral view sections, some with a Found the cause summary and others with Nothing found, and the global filter pills visible.
  6. If you need to interrupt, click Stop: the analysis halts and keeps the results obtained up to that point.
Result. One section per view with its own diagnosis, which lets you spot patterns: for example, that the element only fails in the views that share a template or a scope box.
  • The view selection is remembered while the window stays open, so you can repeat the analysis after applying fixes without choosing them again.
5

Apply a one-click fix (Fix it)

4 steps

Goal. Resolve the most common causes directly from Trace, without diving through Revit's dialogs.

  1. After an analysis, find a red or amber row showing the Fix it link.Five causes have a direct fix: temporary hide/isolate active, category switched off in V/G, element hidden in the view, subcategory switched off and workset not visible. The rest are corrected by hand following the manual's guidance.
    Row for the Element is not hidden in this view check in red with the Show where and Fix it links below the detail.
    assets/shots/trace/fig-08.pngRow for the Element is not hidden in this view check in red with the Show where and Fix it links below the detail.
  2. Click Fix it.The change is applied in a single Revit transaction (named BIMIO Trace — fix: followed by the rule's identifier), so a single Ctrl+Z reverts it completely.
  3. Watch the row re-evaluate itself: if the fix has worked, it turns green and the pill counters update.The status line confirms the action, for example Unhid the element in this view.
  4. If the cause is locked by a view template, Trace does not apply the change and tells you so: you must edit the template, not the view.For example: Model Categories are locked by view template … — turn the category on in the template, not this view. This avoids a change the template would silently revert.
Result. The cause is corrected and verified instantly, with the reassurance that you can undo it with Ctrl+Z.
  • Use Show where first to jump to the view and visually confirm the context before fixing.
6

Navigate to the element and find a view where it is visible

2 steps

Goal. See the element with your own eyes: in the problem view (to understand the context) or in any view in the project where Revit does draw it.

  1. In any resolved row of the diagnosis (except those marked N/A), click Show where.Trace activates that section's view, selects the element and zooms in on it. It is a navigation-only action: it changes nothing in the model.
  2. If the diagnosis finds no cause (Nothing found) or you simply want to confirm that the element exists and draws, click the Find a view where it shows button on the bottom bar.Trace goes through the project's graphical views looking for the first one in which the element generates real geometry, switches to that view and zooms in with the element selected. The status line tells you which view it was found in, for example Shown in "Ground Floor".
Result. Immediate visual confirmation: either you see the element in its context, or you discover it does not draw in any view (which points to a problem with the family itself or with the model).
  • If even Find a view where it shows cannot find a view, check the advanced causes in the manual: family geometry with no visibility in that orientation or detail level, invisible lines, and so on.
7

Share the diagnosis: copy the findings and export the HTML report

3 steps

Goal. Document the cause and hand it to whoever has to correct it, as plain text or as a browsable report.

  1. For a quick note, click Copy findings.A plain-text summary is copied to the clipboard: the element, the overall verdict and, for each view, the CAUSE and MAYBE lines with their explanation. Ideal for pasting into an email, a BCF issue or an RFI.
  2. For a full report, click Export report.Trace generates a self-contained HTML file and opens it in the browser. It is saved in Documents, inside the BIMIO Trace Reports folder, with the element's name and the date and time in the file name.
    HTML report open in the browser: header with the diagnosed element, statistics cards, search box, light/dark theme toggle and the results table by view and check.
    assets/shots/trace/fig-09.pngHTML report open in the browser: header with the diagnosed element, statistics cards, search box, light/dark theme toggle and the results table by view and check.
  3. Share the HTML file directly: it needs no connection or servers, everything is embedded in the file itself.The report also includes the full reference manual with how to correct each cause, so the recipient can resolve it without having Trace installed.
Result. A record of the diagnosis ready to attach to an issue or send to the modeller responsible, with the correction instructions included.
  • The status line shows the exact path of the saved file in case the browser does not open automatically.
8

Consult the built-in manual of causes

2 steps

Goal. Learn (or revise) all the reasons why an element can be hidden in Revit and how each one is corrected, without running any analysis.

  1. Click the question-mark button in the top-right corner of the window.The selectors, the results and the action bar are replaced by the manual; the same button, now showing an X, closes it and brings the analysis back.
    Trace manual mode: Existence & selection, Visibility & graphics, View extent and View context cards with each rule, its BASIC/INTERMEDIATE/ADVANCED badge and its solution line.
    assets/shots/trace/fig-10.pngTrace manual mode: Existence & selection, Visibility & graphics, View extent and View context cards with each rule, its BASIC/INTERMEDIATE/ADVANCED badge and its solution line.
  2. Work through the four cards in the same order Trace checks them and read, for each rule, the solution line.For example, for a switched-off category: open Visibility/Graphics (VG) and tick the element's category on the Model Categories tab. The badges indicate how difficult each cause is.
Result. An always up-to-date crib sheet of the 28 causes of invisibility and their remedy, generated from the very rules the analysis runs, so it never falls out of sync.
  • The manual is also included at the end of every exported HTML report, useful for training the team.

Options reference 8 options

OptionWhat it does
Pick element / By ID (element selector)How you indicate the element to diagnose: by pointing at it with the mouse (with the Pick element… button for the host model and In link… for linked models) or by typing its numeric ID.
Active view / Pick views… (view scope)Which views are checked: only the view active at the moment of analysis, or a set chosen in the Views to check dialog.
Active view checkbox (in the views dialog)Always adds whichever view is open at the moment you click Analyze, in addition to the views ticked in the list.
Search and select-all (in the views dialog)A Search views… field to filter the list by name, and a header checkbox to tick or untick all the visible views at once.
Fast toggleTurns off the animation pause between checks (about 160 ms per step). Recommended when analysing many views at once; switched off, the step-by-step sweep helps you understand the checking order.
Global Show: Causes / Ruled out / N/A pillsFilter which verdicts are shown across all views at once, with the count for each type. Causes and ruled-out checks are shown by default; N/A ones are hidden.
Per-view pillsEach view section has its own Causes / Ruled out / N/A pills to adjust the filter for that view only.
? button (manual)Toggles between the analysis view and the built-in manual with every cause and its solution.

What you get out

  • On-screen diagnosis: one section per view with the verdict of each of the 28 checks, its explanation and its summary (Found the cause, possible causes, Nothing found).
  • Text on the clipboard (Copy findings): a plain-text summary with the element, the overall verdict and the CAUSE/MAYBE lines per view, ready to paste into emails, issues or RFIs.
  • Self-contained HTML report (Export report): saved in Documents\BIMIO Trace Reports with the element's name and a date-and-time stamp, opens automatically in the browser, works offline and includes a search box, light/dark theme, statistics, all the results by view and the full reference manual.
  • Optional changes to the model only via Fix it: each fix runs in a single transaction reversible with Ctrl+Z.

Pro tips 6 tips

Pick the element from a view where you can see it (a 3D view is usually the most convenient) and then analyse the problem view.
Leave the slow mode on (Fast off) the first few times: watching the sweep order teaches you the correct order to review visibility in Revit.
When a cause is locked by a view template, correct the template: the first Visibility & graphics check tells you which parameters the template controls.
Analyse several views at once when the element disappears only on some drawings: comparing the sections reveals the pattern (same template, same scope box, same phase).
After applying a Fix it, the check re-evaluates itself; if it stays red, the cause was twofold: review the remaining amber and red rows.
A Nothing found result is not a dead end: use Find a view where it shows to confirm that the element draws geometry in some view.

Good to know

A single element is analysed per run; if several elements are selected, Trace asks you to choose just one (or to use By ID).
By ID mode only resolves elements in the host model; for elements in links you must use In link….
The Pick views… dialog only lists printable graphical views, excluding view templates; schedules and view templates cannot be analysed.
With an unloaded link only the link layer is evaluated; the element-level checks stay as N/A until you reload it.
Only five causes have a one-click fix (temporary hide/isolate, category, hidden element, subcategory and workset); the rest are corrected manually following the guide.
Fix it refuses to modify a setting locked by a view template (the change would be reverted); you must edit the template.
Some rare cases are not detected yet: an element covered by another one in front of it (Revit exposes no API for this), grossly oversized model extents or view scale thresholds.
The interface and the HTML report are in English.
Trace does not save settings between sessions: closing the window loses the element, view and filter selection.

FAQ 8 questions

Can Trace break anything in my model?
No. All the checks are read-only and open no transactions. The only thing that modifies the model is the Fix it link, which you click expressly, and each fix goes in a single transaction: one Ctrl+Z reverts it completely.
What is the difference between a red cause and an amber one?
Red (definite cause) is a condition that with certainty prevents the element from being seen, for example that it is individually hidden in that view. Amber (possible cause) is a condition that matches and could be the reason, but Trace cannot guarantee it one hundred per cent; it is worth reviewing if there is no red one.
Why do so many rows appear as N/A?
Each check only makes sense for certain combinations of element and view: the view range does not apply to a 3D view, the section box does not apply to a plan, the link checks do not apply to a local element, and so on. That is why N/A rows are hidden by default; you can show them with the N/A pill.
Does it work with elements from linked models?
Yes, with full support: use the In link… button to pick them (with Tab to cycle through candidates). Trace evaluates both the link layer in the host view (link loaded, visible, display settings) and the element inside the linked document, including an advanced check of whether Revit actually draws it. If the link is unloaded, it will ask you to reload it for the full diagnosis.
The summary says Nothing found. What now?
It means that none of the 28 checks detected a cause in that view: the element may simply fall outside the crop, it may draw but very small, or the cause may be one of the advanced ones not covered (for example, another element in front of it). Click Find a view where it shows to confirm that the element draws geometry in some view and compare that view with the problem one.
I click Fix it and it tells me the view template blocks the change. Why?
When a view has a template assigned, certain settings (such as model categories) are locked and any local change would be silently reverted. Trace detects this and refuses to apply a pointless fix: it tells you the template's name so you make the change there, affecting every view that uses it.
Where is the exported report saved?
In your Documents folder, inside BIMIO Trace Reports, with a name made up of the element's label (with spaces and invalid characters replaced by hyphens) plus the date and time, for example Walls--Basic-Wall-_20260703_1245.html. The window's status line shows the full path after exporting, and the file opens automatically in the browser.
Can I analyse several elements at once?
No; Trace is designed to diagnose one element in depth (in one or many views). If you need to audit hidden elements in bulk across the model, that task belongs to the suite's inspection tools; Trace answers the specific question of why this element is not visible here.