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.

Downloads Fixed - Some

I have been trying to carve out a little time here and there to fix the paths to downloads I've shared in the past. As of now the most requested stuff is fixed, the egress family and railing files. If you try to download something and hit a page not found warning, drop a comment in the post to bring it to my attention and I'll make it a priority.

Thanks for being patient - The mGmT...

Schedule Linked Files and Current File

I wrote an earlier post describing a way to create a schedule of linked files. I read a thread at RFO asking about including the current file in the schedule too. I can use the same approach to get that result too. This is a schedule of Levels (since all projects have at least one).

The schedule will naturally reference levels in the active file and I only need to check the Include elements in links option to get their levels too.

The query at RFO also dealt with custom file naming so I took advantage of the built-in Project Information parameter called Building Name. In each project file I've entered a custom File Name in Building Name. This example is using the format described at RFO. I also unchecked the option for Itemize every instance to avoid having many rows for each and every level in the files. I used Clear Cell to eliminate the Title (also turned off that option in Appearance) and used Hide Column for all the fields except Building Name. For this to work long term we need each trade to include this same piece of information in their model/file and update it when they post their next version.

Wish - Insert From File - Work with Templates

Insert from File allows us to import views from another project, views like schedules, drafting views or even sheets that contain either. It is biased toward RVT files though.

It would be handy if it we less biased, enough to include RTE (Revit templates) too. Since we probably have standard stuff set up there anyway. Doing so would allow me to acquire a view from a template file instead of having to first save one as a new project or find another project that is already available in a project folder elsewhere.

Project Version Wish

You may have experienced this too, maybe just once or forty times. I received a file to look over and it's not obvious which version of Revit it was created in. Naturally by the time I got a chance to look at it I couldn't just ask. The file name doesn't give me a clue. Some firms include a version designation in the project file name, for example "1234 Our Big Project-A-13.rvt". The "13" tells me that its a Revit 2013 file. There are plenty of annoying things in life, waiting for a Revit project to upgrade unnecessarily because I don't know what version it was created in is a drag.

Recently a tip was offered (but I can't remember who or where I read it, sorry) that you can use Show History on a project file instead of fully opening it. It helps you catch when you are attempting to open a project in a older version of Revit than the file was created with. It does not help with an older file being opened with a newer version though. Sadly I didn't remember this tip (even though it wouldn't have helped) until I got the dreaded "This is a one time upgrade process" message. Nuts!

I've got a couple wishes. First I'd love it if Revit would store a value in the file properties that indicates Revit version. Second I'd love for Revit to ask first, "Do You WANT to UPGRADE? and a "NO, NOOOO, please on all things holy NOOOO" button.

A Doors Life

As I mentioned in an earlier post I presented a session called "A Door's Life" at the recent Central States Revit Workshop. It tackles creating a host door family that nests 2 panels, 2 frames and 2 handles. It also features a nested clearance form for clash detection and a variable plan swing angle. The host door permits rotating the 3D panel and hardware to any angle as well, though 0-180 is probably the range that's most useful.

If you are interested in more information this is the handout that attendees received (embedded here).

As the handout will tell you it isn't meant to be the perfect door. It's a demonstration of concepts and how to put them all together. If you're lucky you'll end up with something you can use right away or at the very least have a good idea how to get where you want to go.

Click to Download the completed files for each exercise.

Dropping Files

My son is into "Dub Step" and he tells me "the drop" has special meaning but this post is about dragging and dropping files into Revit. You may be aware that, like other Windows applications and files, you can drag and drop a file from Windows Explorer into Revit and Revit will open the file.

As you have probably noticed I like subtle stuff. Brian Mackey mentioned in his adaptive point session at Central States Revit Workshop yesterday that where we drop the file affects how Revit will respond. If we drop a file on the ribbon Revit will open the file. If you drop the file into the canvas or drawing area, and a project or family is already open, it will likely load the family into the other open file instead. If you really want to open the file just be careful where you drop the file.

In Dub Step terms, "Where's the Drop dude?"

Revit Journal Folder and Saving Files on Network Drives

Revitform.org member "Cellophane" dropped this reminder/tip recently.

When you save project files that DO NOT use worksets and family files on a network folder Revit stores a copy of the files in your user Journal folder. Since release 2012 Revit has been using this location for the Journal folder and files:

C:\Users\\AppData\Local\Autodesk\Revit\Autodesk Revit "version"

While chatting with support they gave him this explanation:

"This happens when saving directly to a network location as a data security function, i.e. if the network save fails, the data can be recovered from the local journals folder. If you save locally you will not populate the folder. The reason behind it is saving non-worksharing files to a network introduces a greater possible of failure, so dropping a copy in the journal folder is a way of recovering them."

If you don't keep an eye on this you'll end up with quite a lot of files there. If other people use your computer and Revit then they've probably been "stealing" some disk space from your pc too. As tedious as it might seem to have to clean this out from time to time, the feature came in really handy recently when I managed to kill a few families that I thought I no longer needed. The next day a change came along and I needed them back. No, I didn't archive them for some reason...still not sure why. Regardless, the copies in the Journal folder sure came in handy though! I'm glad I didn't clean them out the day before.

Hide Workset Backup Folders

If you ever work on a project where there quite a few central files it can be bothersome that the _backup folders that Revit uses are presented first in the dialogs that provide access to files. I've found that I can use the "Hidden" file flag to get rid of them assuming I can live with my Folder View settings assigned to hide hidden files and folders.

In the properties of the Workset project's backup folder I check "Hidden".

Then in the settings that govern the display of files and folders in Windows Explorer I use the "Don't show hidden..." option.

Personally I find I need to be able to see hidden files or folders fairly often so it ends up being a bit annoying when I've made the change. I tend to flip back and forth and decide how long I'm going to be working a certain way before committing.

Something to consider...

Show History and a Rogue User Name

I wrote a post recently mentioning that we can use Show History on any file. I saw a post at AUGI that asked how users that claim they've never opened a file might show up in the Show History data. When you use Publish Coordinates to a project file you are altering that file when you save the changes and that change is recorded in the Show History data for it too.

Audit

I wish Audit had more to say. I wish I had a clue what it was actually trying to do, what it cares about, why I should care about it.

The WikiHelp says this about Audit:

Scans, detects, and fixes corrupt elements in the project. This option can greatly increase the time required to open files. Use this option only for periodic maintenance of large workshared files or when you are preparing to upgrade.

It doesn't tell us what it did, if there was anything to do or fix or that our file was too excellent to do anything at all. That's all I want for Christmas. Okay, that's not true but I'd still like it for Christmas.

Upgrading and Reloading Families

I overhead a conversation the other day at Autodesk University. One person suggested to the other that we should always upgrade families to the latest release and then reload them all into our project after it has been upgraded. They theorized that Revit was having to "upgrade" them each time we open a project, like the message we see when a linked file is still based on an earlier version. Assuming that is true they went on to say that upgrading the families and reloading them would avoid this repeated upgrading of content when you open a project.

My gut feeling is that is not true after the project is initially upgraded. I believe that the process of upgrading a project is taking into account the content that is part of the project as well. If I'm correct then the content inside the project is effectively upgraded as well. Saving a family out of the project results in a new family based on that version of Revit too, not the previous one.

Only a developer or product designer/manager could say for certain though.

Supplementary Files

Ryan Duell, with Autodesk and The Revit Clinic, created a list of ten supplementary files for Revit and where they are located by default, READ the POST. I've added a few more so the list is now 18 items. The first ten are the same as his but I've tweaked a few things or added a comment here and there so it isn't a literal copy/paste.

The example paths from the Revit Clinic post are Vista\Windows 7 location conventions, not-roaming profiles. My additions are based on XP, still using it, slack about upgrading, sorry!

1. UniformatClassifications.txt - C:\Program Files\Autodesk\\Program - This file houses the Uniformat Assembly Codes, and the location is fixed; it cannot be moved or specified in a library location. Sorry this means you can't move it to a server. If you wish to edit this file in one location, it is recommended to keep a copy on a server location, and create a batch file to copy and replace the specific file on the user workstation. This file is read once at the Revit application launch.
2. Revit.ini - C:\Program Files\Autodesk\\Program - This file contains the variables, paths, recent files, worksharing paths and more for each version of Revit. For some additional tips on editing this file see one of The Revit Clinic's previous posts HERE.
3. RevitKeynotes_Imperial_2004.txt - C:\ProgramData\Autodesk\\Imperial Library - This file contains the full set of keynotes, provided by Autodesk, which can be assigned to elements in their Type Properties. This file's location can be specified in the project or template, and modified under Annotate > Tag > Keynote Settings.
4. Journal files - C:\Program Files\Autodesk\Revit Architecture 2011\Journals - Revit creates these files as you work. Journal files capture all actions from the current Revit session. For additional information please see the four part series at The Revit Clinic: Part 1, Part 2, Part 3 and Part 4.
5. Worksharing Log File – Central file location "..._backup" folder - The file is named after the central file, with a .SLOG extension. For worksharing-enabled projects all of the central file and user interactions are recorded in this log file. For some additional information please see the previous post HERE.
6. Exportlayers-dwg-AIA.txt – C:\ProgramData\Autodesk\RAC 2011 - Export Layers and Properties settings are stored in this layer mapping file. This is used when exporting a project to DWG or DGN for example. For additional information reference the Help Documentation HERE.
7. UIState.dat - C:\Users\%username%\AppData\Local\Autodesk\Revit\ - Revit stores user specific customizations to the user interface such as the ribbon and quick access toolbar. For additional information see the Help documentation HERE or if you need to reset this file Click Here.
8. KeyboardShortcuts.xml - C:\Users\%username%\AppData\Local\Autodesk\Revit\ - After any change is made to the User Interface and Keyboard Shortcuts, this user-specific file is created to maintain the shortcut customizations. As a rule use the Revit interface to edit your keyboard shortcuts because it is easy than trying to edit this file directly. You can copy (via a Batch File process as mentioned earlier) the file to pass the office standard shortcuts to other workstations however. For additional information reference the technical solution HERE.
9. Shared Parameters Text file – User Defined - This text files stores the parameters added to families or project files. This file is not actively linked, and should never be manually edited. Additional information is available HERE. I've also posted several times about this concept, One, Two, Three, Four, Five, and Six. I've mentioned them in many others too.
10. Revit Server Log Files - C:\logfiles - If using Revit Server, these log files are very useful should you run into any troubleshooting issues.
11. Importlineweights-xxx.txt - C:\Program Files\Autodesk\Revit xxx 2011\Data (XP Location) - These files are used to define how imported cad file elements are interpreted to use different lineweights within Revit. If you import cad details and the don't properly show the graphical quality you expected then you need to change the settings for the file you are actively using. There are several sample files included with Revit. You can change the file you want to reference prior to importing information. This means you can have different "rules" for different kinds of external CAD data.
12. Revit.pat - C:\Program Files\Autodesk\Revit xxx 2011\Data (XP Location) - This is the resource file that your template's have for fill patterns and use to define the patterns for each filled region. A fill pattern can be acquired from other .pat files but they do need an extra declaration of either %TYPE=MODEL or %TYPE=DRAFTING. These help Revit understand which purpose they are intended for. You can read more about this by opening the file and reading the introductory paragraphs provided in the file. A metric version is included too.
13. shxfontmap.txt - C:\Program Files\Autodesk\Revit xxx 2011\Data (XP Location) - This file tells Revit which True Type Fonts you want it to use when it encounters a .shx font in a CAD file during the import process. It is a simple text file. Just add a line the defines the .shx font you want to catch and which TTF font to use instead. Setting this may help you keep some pesky external details from having their text information stretched or compacted because .shx fonts are not supported in Revit directly.
14. Add-ins - C:\Documents and Settings\All Users\Application Data\Autodesk\Revit\Addins\2011 (XP Location) - If you install external applications (3rd Party Software) they should be placing information that Revit needs to run their application in this folder location. If you need to disable their software for some reason or want to create your own you should be aware of this location. You can READ a post at The Revit Clinic for some additional information.
15. IFC Shared Parameters.txt - C:\Program Files\Autodesk\Revit Architecture 2011\Program - Similar purpose as other Shared Parameters but for IFC export instead. I don't know why this file isn't with the other Shared Parameters.
16. OmniClassTaxonomy.txt - C:\Program Files\Autodesk\Revit Architecture 2011\Program (XP Location) - Similar to the Uniformat structure used for Assembly Codes, this is the file that defines the available OmniClass selections when you are creating a component/loadable family.
17. Sitename.txt - C:\Program Files\Autodesk\Revit Architecture 2011\Program (XP Location) - This file is the preset locations provided if you choose to pick a city for your project location. Perhaps somewhat unnecessary with the new Internet based map tool for location but you can add cities via this file.
18. SiteAndWeatherStationName.txt - C:\Program Files\Autodesk\Revit Architecture 2011\Program (XP Location) - Similar to previous but for Weather Stations.

Dept. of Subtle - File Open Memory

While using Revit MEP I observed the following. As you know, when using the Recent Files window you have two options to open a file: Projects and Families.

If you use Projects > Open: Revit remembers which folder location you opened recently.
If you use Families > Open: Revit doesn't remember.

You can also use the Application Menu (Big R) > Open: Project, Family and Revit File.

If you use Project: Revit remembers.
If you use Family: Revit doesn't remember.
If you use Revit File: Revit remembers.

Seems a bit arbitrary and subtle to me. I'd prefer that it remembered the last folder I used regardless. When I tried the same thing in Revit Architecture I found that it remembered the folders correctly. There seems to be some inequity in how Revit keeps track of which folders we visit using the various Open File techniques available to us.

What do you see?

Thumbnail Explorer Released into the Wild

Raizlabs has released Thumbnail Explorer. This is an interesting product, a graphical search engine for your PC and network, with interesting possibilities for viewing/finding Revit content not to mention other file types.

From the website:

Thumbnail Explorer is the perfect tool for anyone who deals with graphics, office files or CAD and has more then a handful of files.

The software allows you to quickly and easily find any file across multiple folders without browsing or using Windows search. As you type a part of file name Thumbnail Explorer will show a list of thumbnails and will enable you to work with corresponding files without resorting to Windows Explorer.

Search and thumbnail extraction done as background process that guarantees interactive responsiveness even when searching through hundreds of thousands of files.

The software features tight integration with Windows Explorer. Double click or drag and drop search results into their native applications. Or right click to see the same context menu as in Windows Explorer.

Customize our tabbed interface to your work environment and files

Easy to use interface requires no training

Do you recognize the name Raiz? Leonid Raiz is one of the two founders of Revit, Irwin Jungreis being the other. Leonid's son Gregory founded Raizlabs 1997. Leonid has been working, in his spare time, on Thumbnail Explorer since retiring from Autodesk about two and half years after selling Revit to Autodesk. He recently released it to a small beta group and is now pleased to release it to the general public as a Raizlabs product.