Showing posts with label View Templates. Show all posts
Showing posts with label View Templates. Show all posts

Tuesday, September 10, 2024

Managing RVT Link Visibility

 I stole this idea from Autodesk Revit Forum member de_smith, sharing it here now. 😀

Another member asked: We have multiple view templates set up for various types of plan views, so when a change needs to be made to the visibility of a linked model, that change must be carried over multiple times, for each view template. It easily becomes hard to track that the visibility is consistent everywhere. 

Is there a way that the linked model visibility settings can be applied independently of view templates, so that when modified, they can carry across the entire project?

de_smith replied with (some editing on my part): 

Control linked models with their own view template then layer the regular view's template back over it. 

Create a "REVIT LINK CLEAN UP VIEW"  view template (for each unique link)

  • in the view template dialog box untick the 'include' column for everything except V/G Overrides RVT Links
  • in this template do all your required visibility modifications to the revit link
  • in all your other view templates under the 'include' column untick V/G Override RVT Links

Apply the 'REVIT LINKS CLEAN UP VIEW' to all your views in your project browser at once

  • then go back and apply the other view templates to the views.
  • This holds the info from the Revit Links Clean up view

If there are any changes needed to the linked models, make the changes once, in the Revit Link's view template, apply it to all views at once and then reapply your other view templates. This is much quicker than changing the Revit links in every single view template.

I've done similar for Imported Categories (DWG links) and try hard not to override RVT links but this should work nicely when it's absolutely necessary.

Friday, April 02, 2021

Rogue RVT Links in your Project

If you've found rogue RVT links in your model it might be Transfer Project Standards (TPS) and View Templates to blame. When you need a View Template from that other project you're working on you run the risk of adding RVT links to the project's database. You'll find them listed in the Manage Links dialog but if you try to reload them Revit will tell you there aren't any instances placed.

This happens when a View Template manages overrides to those linked RVT files in "that other" project. Just remember to check Manage Links after using TPS (reports, haha); otherwise this Gotcha will Getcha

Hat tip to Alexis Kotzambasis for identifying this issue.

Friday, February 19, 2016

Keyboard Shortcut and View Template Conflict

It is obvious when you think about it but when you are trying to use a keyboard shortcut and it doesn't work you might be tempted to think, "That's strange it used to work?!". Off we go to check our keyboard shortcut settings...then..."OH, the view has a View Template assigned to it!"

When a View Template is Assigned to a view, via the view's properties (yes, that's different from applying a view template), the template blocks our access to those settings it is in charge of. When we open Visibility/Graphics we see the categories are disabled (gray). Any keyboard shortcut we attempt to use that involves one of those settings is likewise affected.

In my case tonight I was trying to use keyboard shortcut VH (Hide in View > Category) but nothing happened. Yes, it was just a View Template being bossy. Had me going for a second...

Wednesday, September 02, 2015

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.

Sunday, May 17, 2015

Revit 2016 - IFC Observations

Autodesk recommends that we visit Autodesk Exchange|Apps to download the latest IFC application before starting to work with IFC data.


While testing these features I exported some walls and doors to IFC 2x3 so I could import them as IFC geometry. When I used Link IFC there were Generic Model openings filling the door openings to provide room bounding geometry.


There is a bit more going on behind the scenes when we import IFC. In the past we had to open an IFC which created a Revit project file we could then link. Those extra steps are done for us now as a background operation. There are three files that Revit creates based on the source IFC we link.


If I get obnoxious and delete these files and then open my active project file I get a warning message that Revit couldn’t find a linked file. When I use Reload From and select the IFC file I linked in the first place Revit creates those three files all over again. In the background it’s really just referencing the IFC file named "Linking.ifc.RVT".

I then opened the .RVT file that Revit created during the Link IFC process and deleted the openings and replaced them with Room Separator lines. Rather than doing that we can just leave the Generic Model elements but we need to use a Filter to turn them off. Revit creates a shared parameter file based on the IFC data. We can create a Project Parameter using one of its parameters (ObjectTypeOverrides) so we can create a Filter focused on the Generic Model category.


Once we understand that we can use the same approach to override the appearance of the existing walls, doors and windows so they look more like existing elements.

Thursday, October 23, 2014

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.

Monday, June 17, 2013

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.

Wednesday, March 06, 2013

Manage View Templates Button Disabled

If your Manage View Templates button is disabled it means that you've got no view templates to manage. That troublemaker "someone" deleted them all. Time to find that someone? You can start rebuilding from scratch if you just right click on a view name in the Project Browser and choose Create View Template from View.

If you have some great View Templates elsewhere you can usually use Transfer Project Standards to get them. Keep in mind that View Templates can touch a lot of settings, for example linked RVT files. If the project you are bringing outside View Templates into doesn't have equivalent features in play then the templates may not be able to do everything they did in the other project. It might not be a problem for this project but it's probably worth double checking.

Monday, February 18, 2013

View Template Usage

The other day I wrote about my transition between Revit versions and differences between what we can do with View Templates. Harry "Mr. Boost Your BIM" Mattison offered some code to relieve the tension. It's pretty cool how few lines of code and provide useful answers. Check out his post. Be sure to read his post tomorrow too, he's going to enhance it a bit and share that too!

Thursday, February 14, 2013

Scheduling View Template Usage

When I travel back and forth between Revit versions, say between 12 and 13, I find myself missing things. For example I wanted to see (in 2012) how many views were assigned to view templates and which ones were really being used. In 2013 we can add that parameter to a View List, 2012 not so much. In 2013 we can select a view template and see how many views are assigned to it, in 2012...you get the idea. I wish life and project conditions didn't make it hard to "just upgrade". Just do it, as soon as you can!

Wednesday, May 16, 2012

Apply View Template to all Views

I don't recall when this first showed up but I noticed it first in Revit 2012. Here's what it looks like with a right-click in Revit 2013.


My first reaction was cool! Then I wondered, "When or why would I use it?". Pondered it for a bit and decided that it might be cool if I have a sheet full of details that needed some cleanup. Create a view template and then apply it right quick. Then again I could just select multiple views in the project browser and apply them. With Revit 2013 my view templates will adjust all those details as soon as I change the template, or at least they can if I set it up that way. I suppose this feature might be handy if I forgot to do it and they were all on sheets at this point.

A subtle refinement to process that probably just goes unnoticed? I wonder how many of my readers use it, know about it, care?

Tuesday, May 15, 2012

Revit 2013 - View Types

It is now possible to create new view types for all views except for area plans and sheet. This means you can create your own versions of floor plans according to discipline or perhaps design phase. We've been able to do this with sections, elevations and detail views for some time. As Revit's features have been merged into the new Building Design Suite "Revit" it became apparent that putting all the tools in one box created some curious view, view template and discipline control issues that had to be sorted out, thus being able to create view types for more views was born.

Further, views can be tied to view templates and have changes to a view template take effect immediately in a view or many views. We can apply a view template like before, just to make a change or we can assign a view template to the view so that it will alter the view without the past extra step of applying the view template. This is the typical assumed behavior that most people where surprised to learn did not happen in the past.

One curious thing that is documented at the WikiHelp site regarding these new view types, changing a view from one type to another does not actually apply the view template change that is assigned (if any) to the view. It is an instance parameter so it's an extra step you've got to take to make sure the view has the correct template assigned.

If you use the Apply View template option on a view assigned to view template already you'll get this message.


It's confirming that you really want to apply a different template's settings to the view. It also says that the only properties that will be altered are those that aren't in conflict with the other template. Hopefully the swapping of view types won't occur much after creating them initially and getting this sorted out. If you do find yourself needing to swap them around, just remember to check the view template assignment.

Tip: They've added View Template to the available fields in View Lists (schedule) so it can be managed there too.

Friday, October 15, 2010

Managing Visibility of Linked Files

Aaron Maller of Malleristic Revitation and Beck Group shared a technique (in a comment to my previous post) that he and his current firm like to use to manage the visibility of specific categories in linked files. He/they rely on View Templates extensively to manage the user project experience.

The trouble, for most people, with View Templates when it comes to linked files is that they may not know when the linked files they'll need to use will become available. This means that they usually wait for them and then spend some time dealing with cleanup.

The technique that Aaron describes involves linking blank/empty placeholder files into their project templates. This way their View Templates can be configured to affect the placeholder in advance. Once a real project file is available they can use Reload From to replace the placeholder. Their View Templates and its views are already configured to hide certain categories so no real effort is required of the project team at large.

Different/special coordination views and View Templates can be used to show Levels and Grids for example so that it is easy to use Coordination Review or Copy/Monitor.

We can manage visibility of linked files with:

  • Visibility/Graphics - RVT Link overrides
  • Workset manipulation - as described in my previous post
  • View Templates - as described in this post
  • Some combination of the above

Which is easiest depends on your perspective. A small firm with a few users working on their own projects might choose one route while Aaron's firm will many users to support have chosen this one. Either way his/their approach might just be something you haven't considered?

Sunday, October 25, 2009

Dept. of Subtle - Can't Get Rid of Parameter Value - Project Browser Sorting

This one came up the other day when we were reviewing a view list schedule. They were sorting their views, in the Project Browser, using their own project parameter called View Class, assigned to Views. The intended syntax for the users to follow is: ## - VIEW CLASS VALUE. Initially a value of "02 - Plans" was used, among others, and then a new one showed up: 02-Plans. A subtle difference, just no spaces around the dash.

The team never really gave it much thought, opting to keep moving forward on the project. When I was asked about it my answer was, "A view is assigned/using it." The response was, "No we've fixed all the views already but it won't go away!". We checked again using a view list and sure enough the rogue value wasn't being used.

That's when it occurred to me that a view parameter is stored in View Templates. In fact a view template is the reason the value keeps popping up every now and then in a view's properties. We cleaned template after template, the project had quite a lot of them. Moral of the story? Remember View Templates! They capture view related data too!

A video might tell this better so check it out. I've also embedded it here to listen and watch.