Revit 2020.2 Internal Origin Part Three

John Pierson and Parallax Team Apps recently shared a solution at the Autodesk App Store called Internal Origin Hide-ifier. I thought mine was cool but it doesn't install itself or come with a Doge.

It's only 1,000 bucks...nope its free!! Check it out.

Remember Linked Files Have Two Workset Parameters

I find this overlooked regularly. Each link has an Instance AND Type parameter called Workset. If we select a link (RVT) in the Project Browser we can see the Type parameter for workset, even if the link isn't loaded.

If we right-click and choose Select All Instances > In Entire Project we can see the Instance parameter value, unless there is more than one instance (copies of the link).

The best way to ensure that both parameter values are assigned to the same workset is to make sure the Active Workset is set correctly first, before we link the file. If not then we have to check both values.

Why are there two parameters?

The Type parameter governs the existence of the link in the database while the Instance parameter governs the actual instance you can see in the model views. The linked file can be copied, for example House Design A can be copied so we can show that it will be located on several lots within a development, each likely oriented differently.

The instance parameter allows us to assign each copy to a unique workset while the Type parameter affects all of the copies. That means closing the workset assigned to the Type parameter will close all of the copies of the link, none of them will be visible.

If we close the workset assigned to just one copy then only that linked file won't be visible.

If we experience erratic issues with linked file visibility it is the first thing I check. I'm also in the habit of looking at all the linked files every time I get introduced to project. This also applies to other linked files (CAD,Point Cloud).

Section Line Annotation Alignment

No, not the 2019.1 feature that allows us to use the Align tool on sections...

If you find yourself wondering why you don't the get the telltale dashed lines to help you line up section heads or tails check Visibility/Graphics for the view and make sure Lines are checked (visible). If the category is turned off, so too are they. These...

Check this...

Temporary View Templates

View Templates are quite useful and potentially powerful when they are allowed to be aggressive, placed in charge of Views. To make a View Template the Boss we just need to assign one to a view via its View Template parameter.

Using the Right Click option to Apply Template Properties does not a boss make. It just applies the template settings but then leaves the view open to abuse.

When we do take advantage of placing a View Template in charge of views we bump into this Boss and its rules whenever we want to change the way the view looks. Normally that's good because the View Template is preventing arbitrary changes. In the following image I've mocked up structural walls and separate Veneer walls because I want to accentuate the structural wall in plan views (a common request). It also allows for fussy exterior finish changes (though these are hardly fussy).

In the plan view I've reduced the intensity of the veneer walls. When we need to change the way a view looks and it has a Bossy View Template we can use the Temporary View Properties button on the View Control Shortcut Bar. Usually it is sufficient to click Enable Temporary View Properties. Notice the other choice; Temporarily Apply Template Properties.

If we often find ourselves needing to apply the same kind of override to certain views it makes sense to create a View Template for that and then use it to apply an override to the view, like this next image. I've changed the appearance of the veneer walls to make them stand out; so it is easier to adjust them.

I created a Filter that is looking for a specific value in Type Comments. I picked that because it was easy for this example but it could be any parameter you like, as long as it sets the element(s) apart from others.

I also made another Filter to change the wall the other walls look so they don't compete graphically with the veneer walls as much as they would normally.

When I'm done adjusting the veneer walls I just need to click Restore View Properties and the Boss is back in charge.

Next time you find yourself using Temporary View Properties and Visibility/Graphics to tweak a view again, for the same reason as the last couple times, consider creating a View Template for it.

Filter Linked Grids and Levels

As soon as we rely on or need to use linked files we are confronted with the presence of their grids and levels. Some people use Visibility/Graphics to interact with the linked files and override them so they can shut them off. I like using a Filter for each instead.

Since I have control over the naming of my grid and level types I can make them unique enough that it is unlikely to compete with the naming used for those that are in any of the linked files. Naturally, the last thing I want to attempt is to get the other trades to align their grid/level names. It's a lot easier to just deal with my own naming.

For example let say there are four linked files; Structure, HVAC, Plumbing and Electrical. They all have grids and levels that use different names. As long as mine are distinctly different from theirs I can filter them all off with one filter for grids and another for levels...since I may want to restore one or the other at times, separately.

Here's the Filter dialog configured to filter out all Grids but mine; I called it Not Local Grids. My Grids have a type name prefixed with AEC, but a firm's own acronym or something else that makes it unique works too. This can change from project to project easily too...if necessary.

Now I just add the filters to my View Templates and all the views that are going to get put on sheets and printed will behave with minimal input from me here on out. For coordination I'll use working views that don't have the filter applied or temporarily override the view template so I can toggle either of them on if necessary.

Here's a bonus Filtering tip that was shared at RTC (sorry I don't recall whose session it was). If you are filtering with a specific criteria but can't recall if the first letter is capitalized or not just leave that letter out. For example if you aren't sure if it is Concrete or concrete just enter oncrete as your critera. Pretty subtle and clever!

Linked File Revit MEP has Colors

Revit MEP can assign system colors to their pipe and duct systems. It is easier for them than using a lot of Filters like was required in the past. If you are one of the other trades (architect for example) and link an MEP model and you see color it's probably because they are using this feature. This is what it looks like in the MEP model. I focused on the Domestic Cold Water as an example.

Now the file has been linked to an architectural model. The colors assigned to the pipe system are still applied to the elements. You might be tempted to try to alter the settings of pipe and duct systems in the Project Browser, IF you've noticed that your architectural template has them. I'll save you the trouble, it won't do anything to them.

If you don't want to see those colors you CAN override them with Filters.

I've opened Visibility/Graphics and then created a Filter. In the Filters dialog, if you select only the Duct categories, Flex Ducts, Flex Pipes, Mechanical Equipment and all the Pipe categories, then the "Filter by:" will allow you to choose "System Classification", set it to "is greater than" and "" (empty field).

This should catch all the mechanical elements in linked file and look like this afterward.

Remember to take advantage of a View Template to control this more easily and consistently.

Roads Category and Spot Elevation

This is too weird not to write about it. I was asked to take a look at a file that would not let us apply a spot elevation. I did the usual things, check for the floor category visibility, no overrides to the linked floor(s), no filters, no underlay weirdness... no joy.

I compared it against a new view with no view template. The new view worked but the one with a view template assigned didn't. I tried turning back on all the model categories that were off in the view template. The Spot Elevation tool worked again. Hmmm...

I reset the View Template and then I turned back on each category that was off in the template, one at a time. When I turned on the Roads category the spot elevation started working again. WHAT??

That's more than a little bizarre since we've never been able to use the Roads category for anything. They don't even let us create an In-Place family using the Roads category. I imagine that it is something gone awry in this particular project file since this is the only one behaving this way but still...turning on the Roads category fixed it??

Filter Filtering Gotcha

When you create or edit a view Filter we can apply a Filter to the list of categories based on discipline.

Filtering the list of categories has a direct impact on the Filter Rules > Filter by: list too. If you tell Revit to only show you Architecture categories then you'll find the available parameters listed in the Filter by: criteria drop down will not include parameters that are related to other disciplines. For example, if you were hoping to use the filter to alter the way MEP elements look when they are linked into your model then you might be confused until you realize that earlier you told Revit to only show you Architectural stuff.

Remember the Filter's Filter. Same thing can happen in the View Templates, Visibility/Graphics dialog and Object Styles dialogs.

Visibility Graphics Issues and DWG Imports in Families

I worked through an issue this morning with a fellow RevitForum member. He was trying to determine why desks in the architect's model would not show up in one of his views, using Revit MEP. It turns out that one of the earlier replies in the thread offered part of the solution.

The desk family involved wasn't made of native Revit elements. It was only imported DWG elements. In the view that wouldn't show the desk the view's Visibility/Graphics settings were being controlled by a view template and it had the Imported Categories setting for Imports in Families un-checked. Just one or many things we need to track down when Thing's Go Missing.

Visibility Post Summary

This is a collection of posts regarding visibility in a general sense. They are either literally about visibility issues and features or somehow related to "seeing" things.

2015 Temporary View Templates
2013 Stacking Views on Sheets
2013 Elements are not Displayed or Missing (Troubleshooting guide)
2013 Text Editing and Zooming
2013 Workset Visibility and Linked Files
2013 Linked Files and Visibility Graphics
2013 Visibility Graphics Dialog and Using Current View Only
2013 Apply Versus Apply and View Templates
2013 Revit 2014 Schedules Pending Gotcha
2013 Fittings do not Look Right
2013 Why Use So Called Working Views
2013 View Discipline

2012 Applying Visibility Graphics Overrides
2012 Filter Pesky Levels
2012 Linked Files have Instance and Type Parameters
2012 Hide those Connectors
2012 View Range Redux
2012 Visibility Pecking Order
2012 Scope Boxes
2012 Color Fill Legends Mixing with Stairs

2011 Printing with Temporary Hide Isolate
2011 Revit Links as Underlays
2011 Control Visibility of Image via Size Parameters

2010 Managing Visibility of Linked files
2010 Workset Visibility in Linked Files
2010 Guide Grids
2010 Smaller Grids in Large Scale Views

2009 Video Four View Range Top Offset
2009 How View Range Affects Various Views
2009 Where did my Mass Go

2008 OK and Apply
2008 Aaah the old Invisible Line Trick eh 99

2007 Sketch Lines and Visibility Graphics
2007 visibility of Grips
2007 Shaft Opening and View Range
2007 Future Phases

2006 Workplane Visibility Tips
2006 Workset Visibility in Linked Files
2006 View Range and Floors

Elements are not Displayed or Missing

Some time ago Dave Jones started a thread at RevitForum.org regarding finding elements that have gone missing, don't show up. Grant Doherty replied that most situations can be reduced to these major concepts: Visibility Graphics (Model, Links, FILTERS), View Range, Reveal Hidden Elements (The light bulb), Phases, Worksets and Design Options. Later Nancy McClure summarized things by asking if the problem is: Project Wide, By View, By Family (Project Wide) or By Object (per view).

I think troubleshooting also depends on circumstance, meaning did I just get an error message or am I unable to find something "now" based on the belief/experience that it used to "be there".

This is my version of the list, based on Dave's and taking into account some later posts in the thread. Naturally I've added my two cents.

This warning message occurs when we are actively creating something in a view. It confirms that we've just created something but it can't be shown in the view. The following list applies to conditions that cause this message to appear.

Modelling Actions

1. The wall we created is using Depth, not height (typical of Structural Walls)
2. The column we created is using Depth, not height

Visibility/Graphics

1. The element's Category is currently off
2. The view's Detail Level is not compatible with the missing element
3. A filter applied to the view excludes the element
4. The Active Workset is not visible (V/G override)
5. The Active Design Option for editing is not visible in the view
6. The governing View Template prevents changing the above
7. The Imported Categories > Imports in Families is not checked and DWG data is used in a family

View Properties

1. Depth clipping settings are not compatible
2. View Range settings are incompatible
3. A family's offset/elevation parameter places the element beyond the view range
4. Placing the element outside the view's crop region
5. The view's Discipline is not compatible
6. The view's Display Model setting is not compatible
7. The view's Phase and Phase Filter settings are incompatible

These apply to elements that were visible once but no longer are. When elements are missing remember to use Reveal Hidden Elements to see if anyone has done something in the view or to the elements to prevent them from being visible.

Element Overrides in View (often resolved with Reveal Hidden Elements)

1. Visibility/Graphics overrides applied to element's category
2. The Linework tool, Invisible lines applied to part of or all of the element
3. User applied Right click Hide in View > by Element
4. User applied Right click Hide in View > by Category
5. User applied Right click Hide in View > by Filter
6. User applied Right click Override Graphics in View > by Element
7. User applied Right click Override Graphics in View > by Category
8. User applied Right click Override Graphics in View > by Filter
9. The View's Parts Visibility setting is in conflict
10. User applied Temporary Hide/Isolate > Apply Hide/Isolate to View

Modelling or Documentation Actions

1. The missing Element was deleted by someone
2. The family's detail level
3. The element is being obscured by another element
4. The element resides within a group and it has been excluded from the group
5. The element is part of a design option that is not visible in the view
6. The family was created with nothing visible in this view's orientation
7. The family uses a yes/no parameter to control visibility, set to off
8. The family uses an offset parameter than can shift it out of view vertically
9. DWG data is used in a family and V/G settings don't show it
10. The element is constrained to a scope boxes that is not visible in the view (datum elements only)
11. The element  is a mass, and 'Show Mass' is turned off, or mass category is off
12. The element's host view has been deleted (area boundaries)
13. Wall is consumed by another wall, join/cut geometry
14. Random element located far from project affects zoom to fit
15. The view's scale, element is too large or much too small to see
16. The element is an annotation element and is not entirely within the annotation crop region

Using Worksets

1. The Active Workset is not visible (V/G override)
2. Workset that is not visible in the view (V/G override)
3. Workset is Closed using the Workset dialog
4. Workset of a linked file was not loaded during import
5. Workset that is not visible in a linked file (V/G override)
6. Workset is not Visible in All Views (Workset dialog setting)

Using Phases

1. The element's phase settings prevent the object from being shown
2.  The view's phase settings prevent the element from being shown

Using Design Options

1. The element has been placed in a design option that isn't visible
2. The element has been cut and pasted to a different design option that isn't visible
3. The design option is not visible in the view
4. Accept Primary has been applied to a design option
5. The view's design option has been changed, deleting annotation specific to the option
6. User applied Make Primary, altering the view's display of elements and annotation

Using Linked Files

1. The element is part of a linked file that is not visible in the view
2. The user has incorrectly identified the link instance to which the element belongs
3. The element is in a link that is not in its correct position
4. User applied Right Click Hide in View > by Element to element(s) in a linked file
5. The element is a linked instance with coordinates too great for Revit to handle, affects zooming

As with any list, I'm sure I've missed or overlooked something. The more complicated any given project gets, the more features of Revit that it engages, the more opportunity for elements to go missing. Happy hunting?

Linked Files and Visibility/Graphics

When you examine the Visibility/Graphics dialog you'll find each Revit file you've linked is shown in a list under the Revit Links tab. In this example I've linked Building A, B and C into a host model. The Project Browser shows three linked files and Visibility/Graphics shows the same three but also shows one child link beneath the top level row for each link.

The top level row for each link is the definition of the linked file while the child beneath it represents the actual instance that is placed in the model. The single child for each link provides a way to customize the appearance of the individual linked file apart from the parent definition. Ordinarily this would NOT be required. If overrides are necessary it is sufficient and appropriate to just alter the definition (top level) only.

However if for some reason you were to use two instances of Building A and Building C the Visibility/Graphics dialog would look more like this, while the Project Browser would remain unchanged.

The new child rows listed for Building A and C are the result of copying the originals for each to a new location. Each new row provides us with the ability to use Visibility/Graphic overrides for each child differently if necessary. For example, I could turn off the first instance of Building C without affecting the second instance.

As you can see, the upper Building C is off now. I could also use the button that appears in the Display Settings column to override individual instances of the linked files. If I want to alter both copies the same way I just need to change the top level definition. I start by checking the option "Override display settings for this instance", choosing Custom, activating the Model Categories tab and then changing the Model Categories drop down to Custom. Now I can override individual model categories in just one instance of the two copies of the linked file.

The link names you see are not default values, I changed them via the Name parameter in the Properties palette.

When worksets are involved the top level is assigned to the Type Parameter "Workset" and the child has its own instance parameter for "Workset" too. This means the definition can be assigned to a workset but each instance can be assigned to different worksets.

If you see more than one child instance of a linked file and there should only be one child that probably means someone has copied a link inadvertently. If you can't tell then it's likely they used Copy to Clipboard followed by Paste Aligned to Same Place and there are two instances on top of each other. Since it's been so easy to accidentally select a link I see this happen fairly often. It can create some confusion when people are trying to override graphics and their efforts don't seem to work. There may be another copy lurking underneath.

Visibility Graphics Dialog and Using Current View Only

Revit 2014 introduces an enhancement regarding importing CAD data (I believe undocumented). During an Import of CAD, in the past when we used the option "Current View Only" Revit showed a reference to that link in the Visibility Graphics dialog (V/G) regardless of the view we were working in.

With Revit 2014 it now filters out the link in views that it was not imported into. Naturally if you use Copy to Clipboard and Paste Aligned to put a copy in another view Revit will start to include the link in the V/G dialog again. This is what you should see if you use Current View Only for the import.

View Templates are Mean

If you do something that prompts Revit to pop up this kind of warning (this one is about Spaces)...

You'll be tempted to answer Yes with the expectation that Revit will show your spaces. Well you'd be wrong if your view is assigned to a view template. As in this example if you place a space (using Revit MEP features) you'll get this warning next.

Aggressive view templates will deny the override that the warning dialog implies. It's like asking your mother if you can do something and she says yes but then your father says no. It makes sense but the warning message can be confusing, at least initially. You still have to edit the View Template so it will show whatever category you really want to see.

Applying Visibilty Graphics Overrides

This might be obvious but you can apply changes to views much faster if you don't have any views open that show model elements. Now that it is possible to alter the properties of a view without actually opening it, because the Properties Palette will display a selected view's propeties when you select it in the Project Browser, this means we can edit its visibilty graphics settings even if it isn't open.

It is particulary evident when a project has many linked files. You can alter a view for the first floor but if another floor's view is open Revit seems to spend time thinking about that one too, even mention the linked files.

If you are in the habit of using a synchronize with central view or bulletin board drafting or legend view then open that view and close all others before you dive into overriding view graphics or applying view templates.

Family Editor Please Respect Visibility Settings

[rant mode on]

I really really really really really wish the family editor would honor the Detail Level settings, as well as Yes/No parameter assignment relationship to elements. It is magical enough working in the family editor environment. When you have complicated geometry meshing with lots of visibility controls and options it would be so helpful if we didn't have to drop it into a project to see if they are working correctly.

Yes the elements turn light gray when Yes/No parameters govern or Detail Level settings, but often it would be so much more helpful if it actually turned OFF!

[rant mode off...maybe...]

Where Did it Go?

I've caught myself doing this a couple times before and a question at AUGI reminded me of it. We can temporarily hide things using the Temporary Hide/Isolate feature. When not in use the icon just looks like glasses, more like sunglasses when it is in use, plus the turquoise blue frame around the drawing area and the slight shading behind the glasses too. One of the options available to us is listed at the top, Apply Hide/Isolate to View.

I've clicked on that when I really intended to click the Reset Temporary Hide/Isolate option instead. Later on I end up wondering where "that thing" went. Reveal Hidden Elements (little light bulb) helped me out.

If whatever you were missing shows up with this mode active then you did the same thing. The Apply Hide/Isolate to View option either applies your temporary condition to the element selected or the category depending on how you temporarily hid it to begin with. The end result is the same as if you used the right-click option Hide in View and either chose Elements or Category.

Next time "that thing" goes missing the little light bulb might need to go on.

Visibility Pecking Order

Worth an echo. Ryan at The Revit Clinic wrote a post this morning that lists the order of power, the pecking order, the order in which visibility settings and override tools stack up...who wins when multiple things are applied. Good info, check it out! Here's the list...you need to read his post to get the graphics.

(10 is the lowest and 1 is the highest, using walls as an example)

1. Line Work Tool
2. Override Graphics in View > By Element > Halftone
3. Graphic Display Options – Silhouette Edges
4. Override Graphics in View > By Element
5. View Filters
6. View Depth – “Beyond” Line Style
7. Phasing Graphic Overrides
8. Visibility / Graphic Overrides > Override Host Layers > Cut Line Styles
9. Visibility / Graphic Overrides > Projection \ Cut Lines
10. Project Object Styles

Dept. of Subtle - V/Gs or V/G?

Maybe this is something that only freaks out someone trying to write about something. Is it Visibility/Graphics or Visibility/Graphic?

I'm used to seeing and writing Visibility/Graphics but the dialog actually says Visibility/Graphic, no "s". The Properties palette uses the "s" however.

The review of one of my chapters for the 2012 version of Introducing Autodesk Revit Architecture 2012 flagged it as a question about consistency. I opted to go with the dialog "s-less" version. I hope it doesn't make anyone mad! :)

Stay tuned, we'll let you know when the book is finished and ready to ship! Here's the new cover, recently shared by Pat Davis on the Tampa Bay Revit User's Group blog.

Workset Visibility in Linked Files

Warning: Worksets are not for visibility control purists need to walk away, put some ear plugs in and repeat after me, "Nah nah nah, I can't hear you Steve, I can't hear you".

When you work with linked project files a common issue people deal with is controlling the display of the linked levels and grids. The first person I recall discovering the technique I'm about to describe is Daniel Stine, the author of several Revit books.

If your project and the other project files use specific worksets for certain elements, like Levels and/or grids you can control their visibility quite easily. Here's the steps:

• For each linked project file - define a workset(s) name for the linked elements
• Have the source of each file make sure the elements are assigned to this workset(s)
• Create the same workset(s) using the same name in your own project
• Un-Check Visible by default in all views

When you import the other project file Revit will recognize the workset that uses the same name and respect the fact that your workset by the same name isn't supposed to be visible, rendering their workset "invisible" too. I've created a brief video that explains this too.

For the purist that prefers to use Filters for visibility control, Revit doesn't provide access to project file parameters like file name or project name. If Revit did then we could filter for the grids in the other file instead. If the grid family name chosen by the other project file creators was carefully assigned/selected we could control it with Filters.