Views accumulate tricks — an element painted red for a meeting, a category halftoned, a filter left over, thirty things hidden to tidy a screenshot. Reset View scans the active view, shows exactly how many of each it found, and clears only the kinds you tick — in one undoable transaction that keeps every annotation, dimension and tag, and keeps the view on its sheet. What it cannot reach, it tells you.
To un-trick a view by hand you spelunk the V/G dialog override by override and Reveal Hidden Elements one element at a time — or you duplicate the view and lose its identity.
The whole input half is a read-only preview — nothing writes until you pass one confirm dialog. The output is a single named transaction with a receipt you can believe.
Tap Input or Output to isolate a half — the other collapses.
The window opens scanning, and lands on the view's name, its template, and the four counts. Nothing has been touched yet.
The window opens on “Scanning the active view…” and lands on the view's name, kind and template line, with the four counts — Element, Category, Filter, Hidden. The probe checks 21 override channels, so an element whose only trick is a hidden fill pattern or a forced detail level is still caught. Sheets and schedules are declined in plain words: “Sheets have nothing to reset — open a view instead.”
“Element graphic overrides (colour, line, pattern, transparency, halftone)” is one line on screen and twenty-one questions underneath — six about lines, six about surface patterns, six about the cut, and three about the element as a whole. Five of those are the ones simpler tools skip: the four pattern-visibility tick boxes, which default to on, so an unticked one is itself an override, and a detail level forced away from the view's own. Every element in the view is asked all twenty-one.
Four kinds default on; resetting the dependent views is opt-in and only offered when dependents exist. And when the view template governs categories or filters, an amber band says so before you press anything — “reset can't clear those here; edit the template” — because clearing something the template will silently re-impose is worse than not clearing it.
Reset view is live only while three things hold together: the view carries overrides at all, the scan found something, and at least one kind is ticked. Untick all four and it greys out with the counts still on screen — 214, 3, 5 and 12, none of them at risk. The same guard covers views with nothing to reset: on a sheet the whole list greys and the line under the title reads “Sheets have nothing to reset — open a view instead.”
A permanent card lists the Revit API's blind spots — per-edge Linework, a linked model's display settings, and overrides or Hide-in-View on elements inside links — each with its manual route: the Linework tool set to By Category, Reveal Hidden Elements, Visibility/Graphics ▸ Revit Links. The one promise Reset View refuses to make is “100% pristine”, because the API cannot keep it.
“Every annotation, dimension and tag is kept. This can be undone with Ctrl+Z.” — the dialog's own words.
One dialog stands between the preview and the write. Then a single named transaction, a receipt in a full sentence, and an immediate rescan so the counts visibly drop.
Reset view is the only button that writes, and it asks first — naming how many views it will touch, and promising what it keeps: every annotation, dimension and tag, with Ctrl+Z as the exit. Cancel costs nothing; the preview stays on screen.
Every clear runs inside “BIMIO Reset View — reset overrides”: element, category and filter overrides reset to defaults, hidden elements revealed in a batch with a one-at-a-time fallback so one bad id never loses the rest. The view is reset in place, never duplicated — it keeps its sheet placement, its view references, its dependents. And if Revit rolls the commit back, every counter zeroes, so the summary cannot claim work that was undone.
Only category and filter graphics can belong to a view template. Per-element overrides and Hide-in-View never can — so under the strictest template in the office, the wall someone painted red still clears and the twelve things hidden for a screenshot still come back. The counts say it without arithmetic: Element 0, Hidden 0, Category still 3, Filter still 5, the amber band still up, and a receipt that names the template it refused to fight: “clear them in the template.”
The outcome is written in words, not a spinner: “Reset 214 element overrides, 3 category overrides and 5 filter overrides, and un-hid 12 elements across 1 view.” — with “Some items were skipped — see the log.” when that is true, and the template note when kinds were left untouched. The window rescans immediately, so the four counts drop toward zero in front of you: the receipt and the evidence, side by side.
Nothing is bound at open time — every scan reads whatever view is active now. So one window walks a whole set: change view in Revit, press Rescan, read the four counts, reset the ones that warrant it. A manual rescan clears the previous receipt rather than leaving a sentence hovering over numbers it no longer describes. And Log opens the folder each run is written to, which is where “Some items were skipped — see the log.” is sending you.
Reset View sits on the Views panel of the BIMIO tab. Scan, tick, confirm — and the view is honest again, still on its sheet. Revit 2024–2027, full trial, no card.