Day 3 — Views, graphics, and why things disappear

Half of the time a beginner loses to Revit is spent on "where did my element go?" It is almost never deleted. Today makes that class of problem a 30-second check instead of an afternoon.

Views are queries

A view is not a drawing. It's a live query into the model plus a set of graphics settings. Every plan, section, elevation, 3D view, and schedule is a different question asked of the same database. This is why you never draw the same thing twice, and why fixing graphics in one view doesn't fix it in another.

Duplicating a view offers three options, and the difference matters:

• Duplicate — same model content, no annotation. Use for a second view of the same area with different graphics.
• Duplicate with Detail — copies annotation and detail lines too.
• Duplicate as a Dependent — creates a child view that stays linked to the parent's properties, cropped to a region. This is how you split one big plan across multiple sheets. Change the parent's settings and the dependents follow.

View range: the number one culprit

Every plan view slices the model with four horizontal planes:

Consequences you will hit:

• A low wall (a 3' parapet or knee wall) sits entirely below the 4' cut plane, so it shows as projected, not cut — different line weight, sometimes surprising.
• A clerestory window at 8' is above the cut plane and won't appear at all. Fix with a plan region — a sub-area of the view with its own view range.
• A floor below shows only if it's within View Depth, and then it draws faint.
• Setting Bottom to "Level below" instead of the current level is the classic fix for "I can't see the stair going down".

Practice this deliberately: open your Level 1 plan, VP for View Properties, change the cut plane to 2', watch your windows vanish, put it back.

Visibility/Graphics and the precedence stack

VV or VG opens Visibility/Graphics for the current view: per-category checkboxes and per-category line/pattern overrides, plus tabs for annotation, imports, filters, and linked models.

Graphics come from a stack. Weakest to strongest:

1. Object Styles          (Manage → Object Styles — project-wide defaults)
2. View Template          (applied settings, may be locked)
3. Visibility/Graphics    (this view's category overrides)
4. View Filters           (rule-based, evaluated in filter list order)
5. Element override       (right-click → Override Graphics in View → Element)

Element overrides win over everything, which is exactly why one wall is mysteriously red and nothing you change fixes it. View → Reveal Hidden Elements (RH) shows hidden things in magenta; for stray overrides, check the element directly.

Full detail in view graphics.

Filters: rules, not selections

A view filter selects elements by rule — Category = Walls AND Fire Rating = 2 HR — and applies graphic overrides to whatever matches. Rules re-evaluate constantly, so a wall you change today picks up the override automatically.

Create one under VV → Filters → Edit/New, or View → Filters. Two gotchas:

• A filter can only test parameters that exist on the categories you selected. If your parameter is a project parameter on the wrong category, it won't appear in the list.
• Filters are applied in list order and the first match wins for a given override property. Reorder them with the arrows if two filters fight.

View templates: the actual skill

A view template is a saved bundle of view settings — scale, detail level, visibility/graphics, filters, phase, discipline — that you apply to many views at once.

The rule that separates professionals from beginners: set graphics through templates, not by hand. If you find yourself opening VV in the tenth view to make the same change, stop, put that change in the template, and apply the template.

Workflow:

1. Get one view looking exactly right.
2. View → View Templates → Create Template from Current View. Name it clearly: A-Floor Plan 1:100.
3. Select the other views in the Project Browser (Ctrl+click), right-click → Apply View Template.
4. In the view's Properties, the View Template field now shows the template. Settings controlled by it are greyed out in that view — that's the point.

You can mark individual properties as not included in a template, so a template can control graphics but leave each view's crop region alone. That Include column in the template dialog is the most useful thing on the page.

Scope boxes

A scope box is a 3D box that controls both cropping and datum visibility for a set of views. Create one (View → Scope Box), then in each view's Properties set Scope Box to it. The view crops to the box, and only the grids and levels that intersect the box appear.

This is how big projects manage per-area plans and matchlines without cropping twenty views by hand. Assign the scope box, and every view agrees.

Phases and design options, briefly

Two more reasons elements vanish, both of which will confuse you badly if you don't know they exist:

• Phase. Every element has a Phase Created and Phase Demolished. Every view has a Phase and a Phase Filter. If a view's phase is "Existing" and your wall was created in "New Construction", it isn't there. No error, no warning.
• Design options. Elements inside a design option only appear in views set to show that option. They also can't be edited from the main model, which produces a memorable "why can't I select this" moment.

Read phases and design options once so you recognize the symptoms.

The disappearance checklist

When something isn't visible, check in this order. It's ordered by real-world frequency:

1. View range / cut plane — is it above the top or below the bottom?
2. Visibility/Graphics — is the category unchecked? Is a filter hiding it?
3. Hidden element — press RH. If it's magenta, right-click → Unhide.
4. Crop region — is it outside the crop, or clipped by the annotation crop?
5. Phase / phase filter — does this view's phase include it?
6. Workset — is its workset closed or set to not-visible-by-default? (Day 7.)
7. Design option — is it in an option this view doesn't show?
8. Discipline / detail level — a coarse view hides fine geometry; the Discipline setting hides other trades' elements.

Only after all eight should you conclude something was deleted.

Today's exercise

1. In the Level 1 plan, set the cut plane to 2'-0" and note what changes. Set it back to 4'-0".
2. Add a low wall (3' high) somewhere inside. See how it draws differently from a full-height wall. Look at it in section to confirm why.
3. Add a clerestory window at 8' sill height. It won't show in plan. Fix it with a plan region around that wall.
4. Set a Fire Rating value of 2 HR on your interior wall type (it's a type parameter under Identity Data). Create a filter that catches Fire Rating = 2 HR and overrides those walls to a red cut pattern.
5. Get the Level 1 plan looking right: scale 1/8" = 1'-0" (1:100), detail level Medium, your filter applied, grids visible.
6. Create a view template from it. Apply it to the Level 2 plan. Confirm the Level 2 plan's VV settings are now greyed out.
7. Create a scope box around the building. Assign both floor plans to it.
8. Duplicate the Level 1 plan as a Dependent, crop it to half the building, and confirm changing the parent's view template changes the dependent.
9. Create a section through the stair (Section tool, drag a line across the plan) and a callout on the entry detail. Both are just views — find them in the Project Browser.

Save. Tomorrow you build the content that these views are showing.