Revit Wants you to transmit 'detached copies' of Central files for linking into other models. If you ignore this and transmit your Local copy instead, Revit always remembers where that instance of the Local file was saved, and it causes havoc in a federated model situation. You can use the free CTC explorer extension to quickly check this:
Or you could use Dynamo with my Bakery package:
Hypothetically, let's say you have received a file from a consultant, and after reloading you realise it was a Local file, not a Central. Now, your federated model may already have changed the name of the file to match whatever the local was called. Let's say this problem has caused another problem: multiple instances of that same model have been loaded into this file.
If you are using View Templates, only one of these instances will be the point-of-truth for your View Template Revit Link Overrides. Time to get out your magnifying glass and investigate. Firstly, we will create multiple copies of the RVT file with different names, and then use Reload From (in Manage Links) to get these loaded into the current Revit session. This will create a Local alias:
Now, only one of these is the historical, correct link in the context of this federated model. How do we know which one to keep and which ones to remove?
We can use our View Template Revit Link Overrides to tell us... after all, they are the reason we are going through this process, right? We want Revit to 'remember' the overrides we have made in those templates. So let's have a look at the View Template and see what it tells us.
Basically, by reviewing the Custom overrides here, I was able to determine which version of the Link to keep. It just so happens that the correct historical link had:
a lower number as its instance name (shown above as 149), and
a lower number as its element ID (450048 compared to 1288492). I found this by using Project Browser, Select All Instances - In Entire Project and then Manage - IDs of Selection
The above two 'numerical' investigative methods are probably not 100% reliable, but they may give you a good idea of which link instance is older in terms of this project.
Now, simply Remove the wrong links using the Manage Links dialog, and be aware of not re-linking multiple new instances if you just so happen to get a Local copy from someone in the project team. And remember...
What does Revit Want? Central copies for linking purposes.
ArchVision has just released a new content subscription service, initially focused on Revit construction details, called Detail Warehouse. What is it and how does it work? Read on below...
The DETAIL WAREHOUSE provides access to over 27,500 native Revit Drafting Views designed to kick-start or supplement your in-house Revit standards library. The collection is comprised of foundation, door, window and roof details representing 50 sub-categories of construction details. In addition, you’ll also have access to nearly 1000 Revit Components.
The goal of DETAIL WAREHOUSE is to provide you with an efficient starting point and ongoing complement to your own internal library. For only $499 per year you can access the entire reference library drawing on what you need, when you need it. Learn more at DETAIL WAREHOUSE.
Besides offering the most extensive collection of Revit Drafting Views available anywhere, access to the DETAIL WAREHOUSE is provided via ArchVision’s innovative new content management platform called AVAIL. Through AVAIL, DETAIL WAREHOUSE subscribers can access foundation, door, window and roof “Channels” and search and download content closely matching their needs. A Properties Panel presents high-resolution previews of each Drafting View. AVAIL let’s users browse or search the content in a Channel but also offers an innovative new way to find content we call “Panoply”.
A couple of interesting new endeavors have appeared online recently that I wanted to share. The first is from Autodesk, and they are encouraging you to learn and use keyboard shortcuts. I have posted about keyboard shortcuts plenty of times in the past. I'm not sure this particular site will help me much, because over the years I have customized my Revit shortcuts and they don't match up with the default anymore :-)
I have also posted previously about warnings and error reports (including how to solve them). The Revit Warnings Project wants to take your Revit error reports and turn them into some useful, browse-able statistics data and graphs. It is an interesting read, if only to see how your errors compare to some others. I would like to see the Revit Warnings Project expanded to included recommended solutions to the warnings too.
There was an API addin available a while back, but in recent years I have used:
the Case Batch Export Family RFA's tool http://whatrevitwants.blogspot.com.au/2012/12/how-to-determine-if-family-is-in-place.html This way is pretty robust, as it also gives you a list of inplace families and masses that it couldn't save to rfas. Unfortunately, it is pretty hard to get now that Case have shut down their free app downloads :( Hopefully someone in your office already has it installed? Just copy all the files starting with Case between the relevant addin folders to get it going.
This is a pretty basic lesson, but just in case you aren't doing it already... Adding a default value to your input nodes can make your custom nodes much more useful (and possibly easier for others to use). Obviously, not every input always needs a default, but in some cases you probably know that "in 9 times out of 10 use cases, this value should be xyz". To add this default value in Dynamo:
Edit the custom node
In the input node label, after the label name type a space, followed by a colon, followed by a space
You are now in 'default value land'. Dynamo will prompt you for a datatype.
Choose or enter an appropriate datatype, then type a space, followed by an equals sign, followed by the default value
Obviously, the value must match the datatype.
An explanatory image and a 1 minute screencast are provided below.
I got a virtual tap on the shoulder from Brian Nickel over at The Revit Saver today. He said he had been "searching for an answer like this for a year or two, and the guy posted it two days ago overseas! Talk about a neat workflow!"
What are we talking about?
Basically, it is an inventive way to use the mesh tools in Memento, which can consume images, make meshes, and export them to Recap. From there, we can easily get that into Revit for quick site context investigations. The actual implications of this workflow are pretty big... hypothetically, it allows you to use any good series of images to automatically make some 3d geometry and bring it into the Revit environment for further modelling.
Funnily enough, this workflow is just a logical extension of the stated aims of Memento, namely images to meshes as a 'great companion to ReCap':
Here's how arnebjelland describes the workflow from Google Maps to Revit (via Photoshop, Memento and Revit), In short:
open google maps in full screen and find your building site
rotate the view around your site meanwhile you press «print screen» as often as you wish
with dropbox installed, the «print screens» should be perfectly downloaded automatically
you should crop your photos to get rid of unwanted text/labels. You can do this by making an «action» in Photoshop and then choose «File» – «Scripts» – «Image Processor» to crop every photos in a folder
then you make a mesh in Memento with your cropped photos and export it in RCP
Have you ever wondered if there are API commands for addressing or automating Type Catalog information in Revit? A recent post from Jeremy Tammik covered some of this. In it, he discusses the difference between
the embedded MEP lookup tables (which the API can address using FamilySizeTable and FamilySizeTableManager), and
the legacy text file lookup tables, which are basically a specially formatted TXT file with the same name as the RFA.
The post is well worth a read, as he also references some useful resources in the Revit help and an AU class...
What about units in Type Catalogues? Quoting directly from The Building Coder: " Question:
we're trying to create type catalogue in txt file for Radiator family.
We were trying to define a parameter in watt units, with no success. How
to define header for this parameter? Answer:
Look at page 15 of Martin Schmid's Autodesk University
class handout on Creating Revit MEP Content for Engineering Coordination.
Here is a sample Exhaust Fan RFA and TXT file for you to play with.
They don't use Watts, but should give the idea if you are not already familiar with type catalogues.
Also, the families guide provides a list of the parameter types,
namely, for electrical_power: watts, kilowatts,
calories_per_second, kilocalories_per_second, volt_amperes,
If you have done a clean install of Autodesk products, you may find that the older versions of Application Manager are a bit slow to get going. Just install version 5 straight up to get things updating nicely.
This Labs project was distributed a while back, but it timed out and the addin won't usually run anymore. Its purpose was basically to import a .RIF file from cadMEP back into Revit with some intelligent mapping.
I had someone ask me how to get this working now that the Labs period is up, and I made the suggestion to set the computer time back to before the addin expired... And it works :) So if you really want to play with the FAB to RME Labs addin from about 2 years ago, this might be an option for you.
Paweł Romaniuk has shared his workflow to take various parameters from a model, run the necessary algorithms and then write the area back to a parameter for use in a Revit schedule. Link to pdf download is below... Thanks Paweł.
There is no immediately easy way to override the colour of an entire Revit Link. Of course, you can set up a View Template and override all of the individual subcategories, but that can get time consuming when working with many links...
Worksharing Display Mode gives us a quick way of visualising Worksets. What if we put each Revit Link on its own Workset? Then if we set Worksharing Display Mode to Worksets, these Links are overridden with the Workset colours selected in the dialog:
Unfortunately, the Worksharing Display Mode setting is a temporary override (notice the border around the view?), and it will be switched off when we close and open the file. However, the colour choices will be retained. Is there a way we can quickly 'turn on' the Worksharing Display Mode for all views in the document? Perhaps this could be done just prior to printing, or at the start of an editing session?
Enter... you guessed it... Dynamo.
I made a node to Enumerate Worksharing Display Modes available, and another one to Set Worksharing Display Mode for View. Finally, I adapted the archi-lab Get All Views node into a List All Views node. Now, we can set them in one click:
And a Screencast:
Each time you print, you will be prompted to "Leave the mode on and print...", but the colour override will print fine :)
Colours will transfer using Transfer Project Standards, as per: Transfer Project Standards
If you populate a project with the desired worksets, usernames, and colors you can automatically transfer most of this data over to another project. Under Manage > Transfer Project Standards, there is a new option for Worksharing Display Settings.
Keep in mind this will not transfer over workset names from one project to another.
It will however transfer over workset colors, should the same name workset appear in both projects.
It is pretty difficult to change the Workset of Pipe Insulation. The Properties Palette allows you to change them one at a time (but not multiple), while the method I posted about previously can change multiple Pipe Insulations to a different Workset, but it didn't have a nice filtering mechanism.
Enter Dynamo... I made a custom node that takes a list of Pipe Insulations and gives you the Host Pipe element:
Then, I packaged this up in another node that collects all Pipe Insulations, checks their Workset, finds their Host Pipe, and then saves those Pipes to a SelectionSet:
So, if you have Pipe Insulations on the wrong workset: 1. Install Bakery package in Dynamo 2. Run definition as in image above
3. Close Dynamo 4. Load the Saved Selection 5. Group these Pipes (which groups the Insulations too) 6. Change workset (it will have already adopted the current workset) 7. Ungroup 8. Done
Thanks to Konrad and Andreas for archi-lab and Clockwork packages respectively. I get a few comments about my Bakery package having a lot of dependencies, but I like the fact that I just need to install Bakery and I get archi-lab, Clockwork, Lunchbox etc. Its like a rough and ready deployment solution...
Oh, one more thing. You may notice in recent versions (like 0.8.2 RC) that there is now some custom path management for Dynamo resources: